From: gregkh@linuxfoundation.org (Greg Kroah-Hartman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] drivers/pinctrl: grab default handles from device core
Date: Wed, 12 Dec 2012 13:54:04 -0800 [thread overview]
Message-ID: <20121212215404.GA18555@kroah.com> (raw)
In-Reply-To: <1355343907-11535-1-git-send-email-linus.walleij@stericsson.com>
On Wed, Dec 12, 2012 at 09:25:07PM +0100, Linus Walleij wrote:
> From: Linus Walleij <linus.walleij@linaro.org>
>
> This makes the device core auto-grab the pinctrl handle and set
> the "default" (PINCTRL_STATE_DEFAULT) state for every device
> that is present in the device model right before probe. This will
> account for the lion's share of embedded silicon devcies.
>
> A modification of the semantics for pinctrl_get() is also done:
> previously if the pinctrl handle for a certain device was already
> taken, the pinctrl core would return an error. Now, since the
> core may have already default-grabbed the handle and set its
> state to "default", if the handle was already taken, this will
> be disregarded and the located, previously instanitated handle
> will be returned to the caller.
>
> This way all code in drivers explicitly requesting their pinctrl
> handlers will still be functional, and drivers that want to
> explicitly retrieve and switch their handles can still do that.
> But if the desired functionality is just boilerplate of this
> type in the probe() function:
>
> struct pinctrl *p;
>
> p = devm_pinctrl_get_select_default(&dev);
> if (IS_ERR(p)) {
> if (PTR_ERR(p) == -EPROBE_DEFER)
> return -EPROBE_DEFER;
> dev_warn(&dev, "no pinctrl handle\n");
> }
>
> The discussion began with the addition of such boilerplate
> to the omap4 keypad driver:
> http://marc.info/?l=linux-input&m=135091157719300&w=2
>
> A previous approach using notifiers was discussed:
> http://marc.info/?l=linux-kernel&m=135263661110528&w=2
> This failed because it could not handle deferred probes.
>
> This patch alone does not solve the entire dilemma faced:
> whether code should be distributed into the drivers or
> if it should be centralized to e.g. a PM domain. But it
> solves the immediate issue of the addition of boilerplate
> to a lot of drivers that just want to grab the default
> state. As mentioned, they can later explicitly retrieve
> the handle and set different states, and this could as
> well be done by e.g. PM domains as it is only related
> to a certain struct device * pointer.
>
> Cc: Felipe Balbi <balbi@ti.com>
> Cc: Benoit Cousson <b-cousson@ti.com>
> Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>
> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> Cc: Mitch Bradley <wmb@firmworks.com>
> Cc: Mark Brown <broonie@opensource.wolfsonmicro.com>
> Cc: Ulf Hansson <ulf.hansson@linaro.org>
> Cc: Rafael J. Wysocki <rjw@sisk.pl>
> Cc: Kevin Hilman <khilman@ti.com>
> Cc: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
> Cc: Rickard Andersson <rickard.andersson@stericsson.com>
> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Cc: Russell King <linux@arm.linux.org.uk>
> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
> ---
> ChangeLog v1->v2:
> - Only store a pointer in the device struct, and only allocate
> this if it's really used by the device.
> - Seeking ACK on this from Greg (and others who like it) so I
> can merge it through the pinctrl subsystem.
It looks ok, but this can't go in for 3.8, sorry, please wait for 3.9.
greg k-h
WARNING: multiple messages have this Message-ID (diff)
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Linus Walleij <linus.walleij@stericsson.com>
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Linus Walleij <linus.walleij@linaro.org>,
Felipe Balbi <balbi@ti.com>, Benoit Cousson <b-cousson@ti.com>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
Mitch Bradley <wmb@firmworks.com>,
Mark Brown <broonie@opensource.wolfsonmicro.com>,
Ulf Hansson <ulf.hansson@linaro.org>,
"Rafael J. Wysocki" <rjw@sisk.pl>, Kevin Hilman <khilman@ti.com>,
Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>,
Rickard Andersson <rickard.andersson@stericsson.com>,
Russell King <linux@arm.linux.org.uk>
Subject: Re: [PATCH v2] drivers/pinctrl: grab default handles from device core
Date: Wed, 12 Dec 2012 13:54:04 -0800 [thread overview]
Message-ID: <20121212215404.GA18555@kroah.com> (raw)
In-Reply-To: <1355343907-11535-1-git-send-email-linus.walleij@stericsson.com>
On Wed, Dec 12, 2012 at 09:25:07PM +0100, Linus Walleij wrote:
> From: Linus Walleij <linus.walleij@linaro.org>
>
> This makes the device core auto-grab the pinctrl handle and set
> the "default" (PINCTRL_STATE_DEFAULT) state for every device
> that is present in the device model right before probe. This will
> account for the lion's share of embedded silicon devcies.
>
> A modification of the semantics for pinctrl_get() is also done:
> previously if the pinctrl handle for a certain device was already
> taken, the pinctrl core would return an error. Now, since the
> core may have already default-grabbed the handle and set its
> state to "default", if the handle was already taken, this will
> be disregarded and the located, previously instanitated handle
> will be returned to the caller.
>
> This way all code in drivers explicitly requesting their pinctrl
> handlers will still be functional, and drivers that want to
> explicitly retrieve and switch their handles can still do that.
> But if the desired functionality is just boilerplate of this
> type in the probe() function:
>
> struct pinctrl *p;
>
> p = devm_pinctrl_get_select_default(&dev);
> if (IS_ERR(p)) {
> if (PTR_ERR(p) == -EPROBE_DEFER)
> return -EPROBE_DEFER;
> dev_warn(&dev, "no pinctrl handle\n");
> }
>
> The discussion began with the addition of such boilerplate
> to the omap4 keypad driver:
> http://marc.info/?l=linux-input&m=135091157719300&w=2
>
> A previous approach using notifiers was discussed:
> http://marc.info/?l=linux-kernel&m=135263661110528&w=2
> This failed because it could not handle deferred probes.
>
> This patch alone does not solve the entire dilemma faced:
> whether code should be distributed into the drivers or
> if it should be centralized to e.g. a PM domain. But it
> solves the immediate issue of the addition of boilerplate
> to a lot of drivers that just want to grab the default
> state. As mentioned, they can later explicitly retrieve
> the handle and set different states, and this could as
> well be done by e.g. PM domains as it is only related
> to a certain struct device * pointer.
>
> Cc: Felipe Balbi <balbi@ti.com>
> Cc: Benoit Cousson <b-cousson@ti.com>
> Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>
> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> Cc: Mitch Bradley <wmb@firmworks.com>
> Cc: Mark Brown <broonie@opensource.wolfsonmicro.com>
> Cc: Ulf Hansson <ulf.hansson@linaro.org>
> Cc: Rafael J. Wysocki <rjw@sisk.pl>
> Cc: Kevin Hilman <khilman@ti.com>
> Cc: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
> Cc: Rickard Andersson <rickard.andersson@stericsson.com>
> Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> Cc: Russell King <linux@arm.linux.org.uk>
> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
> ---
> ChangeLog v1->v2:
> - Only store a pointer in the device struct, and only allocate
> this if it's really used by the device.
> - Seeking ACK on this from Greg (and others who like it) so I
> can merge it through the pinctrl subsystem.
It looks ok, but this can't go in for 3.8, sorry, please wait for 3.9.
greg k-h
next prev parent reply other threads:[~2012-12-12 21:54 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-12 20:25 [PATCH v2] drivers/pinctrl: grab default handles from device core Linus Walleij
2012-12-12 20:25 ` Linus Walleij
2012-12-12 21:54 ` Greg Kroah-Hartman [this message]
2012-12-12 21:54 ` Greg Kroah-Hartman
2013-01-02 13:42 ` Linus Walleij
2013-01-02 13:42 ` Linus Walleij
2013-01-09 8:16 ` Linus Walleij
2013-01-09 8:16 ` Linus Walleij
2013-01-02 13:37 ` Mark Brown
2013-01-02 13:37 ` Mark Brown
2013-01-10 20:42 ` Stephen Warren
2013-01-10 20:42 ` Stephen Warren
2013-01-10 22:07 ` Stephen Warren
2013-01-10 22:07 ` Stephen Warren
2013-01-11 20:22 ` Linus Walleij
2013-01-11 20:22 ` Linus Walleij
2013-01-11 20:12 ` Linus Walleij
2013-01-11 20:12 ` Linus Walleij
2013-01-11 20:36 ` Laurent Pinchart
2013-01-11 20:36 ` Laurent Pinchart
2013-01-11 20:45 ` Linus Walleij
2013-01-11 20:45 ` Linus Walleij
2013-01-16 17:49 ` Stephen Warren
2013-01-16 17:49 ` Stephen Warren
2013-01-17 0:59 ` Linus Walleij
2013-01-17 0:59 ` Linus Walleij
2013-01-17 2:33 ` Greg KH
2013-01-17 2:33 ` Greg KH
2013-01-17 16:30 ` Stephen Warren
2013-01-17 16:30 ` Stephen Warren
2013-01-17 6:02 ` Simon Horman
2013-01-17 6:02 ` Simon Horman
2013-01-17 6:02 ` Simon Horman
2013-01-17 16:31 ` Stephen Warren
2013-01-17 16:31 ` Stephen Warren
2013-01-17 16:31 ` Stephen Warren
2013-01-17 23:55 ` Simon Horman
2013-01-17 23:55 ` Simon Horman
2013-01-17 23:55 ` Simon Horman
2013-01-18 15:05 ` Linus Walleij
2013-01-18 15:05 ` Linus Walleij
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=20121212215404.GA18555@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.