Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S934755AbdDFNjM (ORCPT ); Thu, 6 Apr 2017 09:39:12 -0400 Received: from hqemgate14.nvidia.com ([216.228.121.143]:10103 "EHLO hqemgate14.nvidia.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753213AbdDFNjJ (ORCPT ); Thu, 6 Apr 2017 09:39:09 -0400 X-PGP-Universal: processed; by hqpgpgate101.nvidia.com on Thu, 06 Apr 2017 06:39:08 -0700 Message-ID: <58E6405E.5020402@nvidia.com> Date: Thu, 6 Apr 2017 18:49:26 +0530 From: Laxman Dewangan User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: Thierry Reding , Jon Hunter CC: , , , , , , Linus Walleij Subject: Re: [PATCH 3/4] pwm: tegra: Add DT binding details to configure pin in suspends/resume References: <1491401626-31303-1-git-send-email-ldewangan@nvidia.com> <1491401626-31303-4-git-send-email-ldewangan@nvidia.com> <33445b27-ae0b-b28e-afca-e7b776b4b7c0@nvidia.com> <20170406130315.GB7784@ulmo.ba.sec> In-Reply-To: <20170406130315.GB7784@ulmo.ba.sec> X-Originating-IP: [10.19.65.30] X-ClientProxiedBy: DRBGMAIL101.nvidia.com (10.18.16.20) To bgmail102.nvidia.com (10.25.59.11) Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1845 Lines: 41 On Thursday 06 April 2017 06:33 PM, Thierry Reding wrote: > * PGP Signed by an unknown key > > On Thu, Apr 06, 2017 at 09:57:09AM +0100, Jon Hunter wrote: >> On 05/04/17 15:13, Laxman Dewangan wrote: >>> +state of the system. The configuration of pin is provided via the pinctrl >>> +DT node as detailed in the pinctrl DT binding document >>> + Documentation/devicetree/bindings/pinctrl/pinctrl-bindings.txt >>> + >>> +The PWM node will have following optional properties. >>> +pinctrl-names: Pin state names. Must be "suspend" and "resume". >> Why not just use the pre-defined names here? There is a pre-defined name >> for "default", "idle" and "sleep" and then you can use the following >> APIs and avoid the lookup of the state ... >> >> pinctrl_pm_select_default_state() >> pinctrl_pm_select_idle_state() >> pinctrl_pm_select_sleep_state() >> >> Note for i2c [0][1], I used "default" as the active/on state (which I >> know is not that descriptive) and then used 'idle' as the suspended >> state. This way we don't need any custom names. > Agreed, I think that's how these states are meant to be used. I did quick grep for the pinctrl_pm_select_* functions in the code tree and found usage of these APIs in some of the places. I am taking the reference of i2c-st, i2c-nomadic and extcon/extcon-usb-gpio.c drivers and from this the interpretation is default state: When interface active and transfer need to be done in IO interface. idle state: Active state of the system but interface is not active, put in non-active state of the interface. sleep state: When system entering into suspend and IO interface is going to be inactive. So in PWM case, we will need the "default" and "sleep" state. In suspend(), set the "sleep" state and in resume, set the "default" state. + Linus W as I refereed his st/nomadik driver for reference.