MIME-Version: 1.0
In-Reply-To: <CAMz4kuJigdhbV5+J1CcqP6zb7pqi9HaW=dxe_rsNi-=RsQ70vA@mail.gmail.com>
References: <359d62c1f2f7ef61c6160df9b60c1af4bfcea89a.1496664241.git.baolin.wang@spreadtrum.com>
 <CACRpkdbtuPKr=tWGoJC-sg2Oj47rYMpo6fs_Us=Nynew1Wkz=w@mail.gmail.com>
 <20170612060718.GA8566@spreadtrum.com> <20170613031547.GA29679@spreadtrum.com>
 <CACRpkdbaP1U3pefTbPj-wOa1AibcJHBBALfKWO8dBR=YW8f7zA@mail.gmail.com>
 <CAMz4ku+jZ-S6sBL=ib++j+ooqweU9UC+MTgFca7ScrQiJDeZVQ@mail.gmail.com>
 <CACRpkdYETvpsr1X1dfiGfg9i=Tq2qHJBZHv7Us4aZ_1HQcOdoA@mail.gmail.com> <CAMz4kuJigdhbV5+J1CcqP6zb7pqi9HaW=dxe_rsNi-=RsQ70vA@mail.gmail.com>
From: Linus Walleij <linus.walleij@linaro.org>
Date: Wed, 12 Jul 2017 14:04:15 +0200
Message-ID: <CACRpkdZg018Q7EE-LvsLqWDm3=P2_L58MxR3fcgcUtGaAXk45A@mail.gmail.com>
Subject: Re: [PATCH v2 1/2] DT: pinctrl: Add binding documentation for
 Spreadtrum pin controller
To: Baolin Wang <baolin.wang@linaro.org>
Cc: Mark Rutland <mark.rutland@arm.com>, Rob Herring <robh+dt@kernel.org>,
        "linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
        "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
        "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
        Mark Brown <broonie@kernel.org>
Content-Type: text/plain; charset="UTF-8"
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1060
Lines: 24

On Tue, Jun 27, 2017 at 9:59 AM, Baolin Wang <baolin.wang@linaro.org> wrote:
> On 26 June 2017 at 06:19, Linus Walleij <linus.walleij@linaro.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