[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACRpkdYN9e3L3GD0T6FEYVbHd4nCTfnDSF-M6LexfHUNJ2n+Ww@mail.gmail.com>
Date: Tue, 13 Dec 2011 13:23:16 +0100
From: Linus Walleij <linus.walleij@...aro.org>
To: Haojian Zhuang <haojian.zhuang@...il.com>
Cc: Linus Walleij <linus.walleij@...ricsson.com>,
linux-kernel@...r.kernel.org, Stephen Warren <swarren@...dia.com>,
Grant Likely <grant.likely@...retlab.ca>,
Barry Song <21cnbao@...il.com>,
Shawn Guo <shawn.guo@...escale.com>,
Thomas Abraham <thomas.abraham@...aro.org>,
Dong Aisheng <dong.aisheng@...aro.org>,
Rajendra Nayak <rajendra.nayak@...aro.org>,
Haojian Zhuang <haojian.zhuang@...vell.com>
Subject: Re: [PATCH v6] pinctrl: add a pin config interface
On Tue, Dec 13, 2011 at 8:21 AM, Haojian Zhuang
<haojian.zhuang@...il.com> wrote:
> Excuse me that I didn't find that patch. Did you merge it into your
> git tree?
Yes. It's pushed out and will also be included in linux-next.
> The latest patch on pinconf.c is updating pdev->dev to
> &pdev->dev.
It *should* be the other way around. So pdev->dev points to the
original platform device, and thus you have a handle on that in e.g.
board files where the pin controller is defined and thus you can
apply pin configurations from there.
> By the way, will you merge generic-pinconf into your for-next branch?
Nobody has ACK:ed it and Stephen and Mark both have
unresolved issue with how this should look.
If the current v5 patch suits your needs, please ACK it on the
mailing list so we know that there are people who like this
solution apart from me.
Yours,
Linus Walleij
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists