From: Greg KH <gregkh@linuxfoundation.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Doug Anderson <dianders@chromium.org>,
Thierry Reding <thierry.reding@gmail.com>,
Mark Brown <broonie@kernel.org>, Lee Jones <lee.jones@linaro.org>,
Chris Zhong <zyw@rock-chips.com>,
Heiko Stuebner <heiko@sntech.de>,
Sonny Rao <sonnyrao@chromium.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH] drivers/pinctrl: Add the concept of an "init" state
Date: Wed, 8 Oct 2014 06:46:15 -0700 [thread overview]
Message-ID: <20141008134615.GA6586@kroah.com> (raw)
In-Reply-To: <CACRpkda2O+LWQovekrxNDa27O7OK4GRRz6ugA=Yzh4qZ3JSc7Q@mail.gmail.com>
On Wed, Oct 08, 2014 at 11:00:11AM +0200, Linus Walleij wrote:
> On Tue, Oct 7, 2014 at 10:28 PM, Doug Anderson <dianders@chromium.org> wrote:
>
> > For pinctrl the "default" state is applied to pins before the driver's
> > probe function is called. This is normally a sensible thing to do,
> > but in some cases can cause problems. That's because the pins will
> > change state before the driver is given a chance to program how those
> > pins should behave.
> >
> > As an example you might have a regulator that is controlled by a PWM
> > (output high = high voltage, output low = low voltage). The firmware
> > might leave this pin as driven high. If we allow the driver core to
> > reconfigure this pin as a PWM pin before the PWM's probe function runs
> > then you might end up running at too low of a voltage while we probe.
> >
> > Let's introudce a new "init" state. If this is defined we'll set
> > pinctrl to this state before probe and then "default" after probe
> > (unless the driver explicitly changed states already).
> >
> > An alternative idea that was thought of was to use the pre-existing
> > "sleep" or "idle" states and add a boolean property that we should
> > start in that mode. This was not done because the "init" state is
> > needed for correctness and those other states are only present (and
> > only transitioned in to and out of) when (optional) power management
> > is enabled.
> >
> > Signed-off-by: Doug Anderson <dianders@chromium.org>
>
> I *like* this approach. A lot.
>
> It will come with DT bindings for free as it's just strings.
>
> > +++ b/drivers/base/dd.c
> > @@ -308,6 +308,8 @@ static int really_probe(struct device *dev, struct device_driver *drv)
> > goto probe_failed;
> > }
> >
> > + pinctrl_init_done(dev);
>
> We will need Greg's ACK for this oneliner.
As much as I hate subsystem-specific code in the driver core, I guess I
let this happen before, so I can't object here :)
Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
prev parent reply other threads:[~2014-10-08 13:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-07 20:28 Doug Anderson
2014-10-08 9:00 ` Linus Walleij
2014-10-08 13:46 ` Greg KH [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20141008134615.GA6586@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=broonie@kernel.org \
--cc=dianders@chromium.org \
--cc=heiko@sntech.de \
--cc=lee.jones@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sonnyrao@chromium.org \
--cc=thierry.reding@gmail.com \
--cc=zyw@rock-chips.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome