[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAMz4kuJqbL3Mao9UCGCvhbZeAnubLNrddz699ywVfZm2scbr3w@mail.gmail.com>
Date: Thu, 31 Aug 2017 16:07:01 +0800
From: Baolin Wang <baolin.wang@...aro.org>
To: Linus Walleij <linus.walleij@...aro.org>
Cc: Baolin Wang <baolin.wang@...eadtrum.com>,
Mark Rutland <mark.rutland@....com>,
Rob Herring <robh+dt@...nel.org>,
"linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Mark Brown <broonie@...nel.org>
Subject: Re: [RESEND PATCH v5 1/3] pinctrl: Add sleep related state to
indicate sleep related configs
Hi,
On 31 August 2017 at 15:16, Linus Walleij <linus.walleij@...aro.org> wrote:
> On Thu, Aug 17, 2017 at 8:50 AM, Baolin Wang <baolin.wang@...eadtrum.com> wrote:
>
>> In some scenarios, we should set some pins as input/output/pullup/pulldown
>> when the specified system goes into deep sleep mode, then when the system
>> goes into deep sleep mode, these pins will be set automatically by hardware.
>>
>> That means some pins are not controlled by any specific driver in the OS, but
>> need to be controlled when entering sleep mode. Thus we introduce one sleep
>> state config into pinconf-generic for users to configure.
>>
>> Signed-off-by: Baolin Wang <baolin.wang@...eadtrum.com>
>> ---
>> Changes since v4:
>> - Add sleep-hardware-state config to indicate sleep related configs.
>
> No reactions and I can certainly not think of anything better (I even
> suggested this) so patch applied.
>
> Sorry for taking so long to look at this, I've been choked :/
I can understand you are so busy :), thanks for your help.
--
Baolin.wang
Best Regards
Powered by blists - more mailing lists