Received: by 10.192.165.156 with SMTP id m28csp2026612imm; Thu, 12 Apr 2018 07:28:18 -0700 (PDT) X-Google-Smtp-Source: AIpwx497YIFJ28SVzc9ntGtqgOl/T9PliMUgO6e6l8dVVopE5l/NLiR/c5EGTSAnnxGBrQJia3z+ X-Received: by 2002:a17:902:6a81:: with SMTP id n1-v6mr1291739plk.342.1523543298551; Thu, 12 Apr 2018 07:28:18 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1523543298; cv=none; d=google.com; s=arc-20160816; b=WBczsXhsCJEF294338L+7lQosBInL96zKTvuSzNmXedmRF0Y2Jv9MUgOT7dnDgizV5 pTj1onpvdoqqf62yRpqdQuZxrILAT/a0YgzpKZfFWPMbXC6FspQlrpNg6XCeMbK4lWdf aQxdpKPAL3ZoBwCxYUv9A5sIfKF1Oq+dIxG2MgfzKkDbJdWttOJUsBYfURtUXkZNGL9l vWbljO8yzBxe1MB0m+H0NaOkCDciQfLdjFayYLVNkqhidSnukObPR7tmq3flF9cGoJEo arZnRmN5H9uk3dN9ANxrHjUGf0YEsIzc9f+3LeXvYCslRM4Hn60uCpART0Ygi1l0SKpJ 7zmA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:arc-authentication-results; bh=gqkdA9sJ2peD7tqQLYosIMzbcGU5/HfKm+QOOZ8jllY=; b=dTddUFqoqq+wLCv1ZgArA+ntICzw3D6l1LlfpwLggfPcA/hTc/kl3xMbKb+6FGWIjn tCar8W2RVkS1CHBibtCZYE9caw2T5zBKBnqH12VLKavoDwU/paRvPxXdKAXHVjE/8HET qv6Ic1PKO1HWElelJK0fJik5YV9jsnvAXY+Vhb2RVCQ3CMp4ghOBnLpT/+C7IsMPneGt vmPS7PyDFbG8KrRGVRM8U+9d2F/0HdhZ7vjL8EolLQp2It7n811fDCUMrA65fS6UyBwR skGh6a2MUNeWr5WEVHbxQgxh4FpXMLeNj8dNJDOeC4HdGBRxx1LwdfUgSQhtQUWO9BmQ ZDdg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id e28si2384639pgn.621.2018.04.12.07.27.41; Thu, 12 Apr 2018 07:28:18 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753549AbeDLOXD (ORCPT + 99 others); Thu, 12 Apr 2018 10:23:03 -0400 Received: from muru.com ([72.249.23.125]:36414 "EHLO muru.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752598AbeDLOXB (ORCPT ); Thu, 12 Apr 2018 10:23:01 -0400 Received: from atomide.com (localhost [127.0.0.1]) by muru.com (Postfix) with ESMTPS id F278D8081; Thu, 12 Apr 2018 14:24:33 +0000 (UTC) Date: Thu, 12 Apr 2018 07:22:57 -0700 From: Tony Lindgren To: Keerthy Cc: linus.walleij@linaro.org, grygorii.strashko@ti.com, t-kristo@ti.com, Russ.Dill@ti.com, linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org, ssantosh@kernel.org, haojian.zhuang@linaro.org, linux-arm-kernel@lists.infradead.org, d-gerlach@ti.com Subject: Re: [PATCH 10/14] gpio: omap: Drop the concept of gpio banks not being able to lose context. Message-ID: <20180412142257.GW5700@atomide.com> References: <1523505239-16229-1-git-send-email-j-keerthy@ti.com> <1523505239-16229-11-git-send-email-j-keerthy@ti.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1523505239-16229-11-git-send-email-j-keerthy@ti.com> User-Agent: Mutt/1.9.4 (2018-02-28) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Keerthy [180412 03:56]: > From: Russ Dill > --- a/drivers/gpio/gpio-omap.c > +++ b/drivers/gpio/gpio-omap.c > @@ -68,7 +68,7 @@ struct gpio_bank { > bool dbck_enabled; > bool is_mpuio; > bool dbck_flag; > - bool loses_context; > + > bool context_valid; > int stride; > u32 width; For some SoCs GPIO bank1 won't lose the context ever. So I'd like to keep loses_context flag around to avoid pointless save and restore. But maybe this still happens with get_context_loss_count and I'm misreading this patch? However.. > @@ -1198,15 +1198,9 @@ static int omap_gpio_probe(struct platform_device *pdev) > #ifdef CONFIG_OF_GPIO > bank->chip.of_node = of_node_get(node); > #endif > - if (node) { > - if (!of_property_read_bool(node, "ti,gpio-always-on")) > - bank->loses_context = true; > - } else { > - bank->loses_context = pdata->loses_context; > - > - if (bank->loses_context) > - bank->get_context_loss_count = > - pdata->get_context_loss_count; > + if (!node) { > + bank->get_context_loss_count = > + pdata->get_context_loss_count; > } > > if (bank->regs->set_dataout && bank->regs->clr_dataout) .. I do have a patch ready here that I'll post after -rc1 to remove CONFIG_OMAP_PM_NOOP related stuff, turns out that's noop anyways :) So yeah the pdata->get_context_loss_count parts are noop and can be just removed. Regards, Tony