From: laurent.pinchart@ideasonboard.com (Laurent Pinchart)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] drivers/pinctrl: grab default handles from device core
Date: Fri, 11 Jan 2013 21:36:10 +0100 [thread overview]
Message-ID: <9702060.jEbHySsCv0@avalon> (raw)
In-Reply-To: <CACRpkdZ0b=ZohgaBH3qPH_O5TiWmXJXs6872D+YPVA9g4BssYg@mail.gmail.com>
Hi Simon,
On Friday 11 January 2013 21:12:43 Linus Walleij wrote:
> On Thu, Jan 10, 2013 at 9:42 PM, Stephen Warren wrote:
> > On 12/12/2012 01:25 PM, 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.
> >
> > There are quite a few problems with this patch, and they end up
> > completely breaking at least Tegra in next-20130110.
>
> But I have not put this patch into linux-next.
>
> I was still waiting for Greg to ACK it...
>
> Apparently it was included in a pull request to the SH tree or something,
> Simon can you remove these patches for now, this patch needs to
> be elaborated on in the pinctrl tree first.
I've sent several patch series for the SH PFC (Pin Function Controller) to the
linux-sh mailing list. One of the series included pinctrl core patches for
easier testing, but I made it clear that they should *not* be pushed to
mainline through the SH tree.
Actually the whole PFC series have been found out today by Guennadi
Liakhovetski to be buggy. I will fix the problems and send a new version. In
the meantime the pinmux-pinctrl and pinmux-dt series should not be pushed to
mainline.
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2013-01-11 20:36 UTC|newest]
Thread overview: 19+ 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 21:54 ` Greg Kroah-Hartman
2013-01-02 13:42 ` Linus Walleij
2013-01-09 8:16 ` Linus Walleij
2013-01-02 13:37 ` Mark Brown
2013-01-10 20:42 ` Stephen Warren
2013-01-10 22:07 ` Stephen Warren
2013-01-11 20:22 ` Linus Walleij
2013-01-11 20:12 ` Linus Walleij
2013-01-11 20:36 ` Laurent Pinchart [this message]
2013-01-11 20:45 ` Linus Walleij
2013-01-16 17:49 ` Stephen Warren
2013-01-17 0:59 ` Linus Walleij
2013-01-17 2:33 ` Greg KH
2013-01-17 16:30 ` Stephen Warren
2013-01-17 6:02 ` Simon Horman
2013-01-17 16:31 ` Stephen Warren
2013-01-17 23:55 ` Simon Horman
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=9702060.jEbHySsCv0@avalon \
--to=laurent.pinchart@ideasonboard.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).