linux-kernel - Re: [PATCH v2 1/2] DT: pinctrl: Add binding documentation for Spreadtrum pin controller

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CACRpkdZg018Q7EE-LvsLqWDm3=P2_L58MxR3fcgcUtGaAXk45A@mail.gmail.com>
Date:   Wed, 12 Jul 2017 14:04:15 +0200
From:   Linus Walleij <linus.walleij@...aro.org>
To:     Baolin Wang <baolin.wang@...aro.org>
Cc:     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: [PATCH v2 1/2] DT: pinctrl: Add binding documentation for
 Spreadtrum pin controller

On Tue, Jun 27, 2017 at 9:59 AM, Baolin Wang <baolin.wang@...aro.org> wrote:
> On 26 June 2017 at 06:19, Linus Walleij <linus.walleij@...aro.org> wrote:

>> I meant, as part of setting the "default" state or even the "init"
>> state, we would inspect the "sleep" state, use those settings, and
>> program them into the registers at this early point.
>
> I understood your points. But we can not program all into the
> registers at one early point, sometimes these sleep-related configs
> need depend on some conditions in users' drivers, like on condition 1:
> driver need to set one pin as input-enable when specified system goes
> into deep sleep, on condition 2: driver need set this pin as
> output-enable when specified system goes into deep sleep. So I still
> think it is better if we introduce some standard sleep related
> configs.

So you mean you need special runtime states to set up sleep states?

Do you have an example of how this would look in the device tree?

I am sorry but I have a hard time following the use case :(

Yours,
Linus Walleij