From: Linus Walleij <linus.walleij@linaro.org>
To: Haojian Zhuang <haojian.zhuang@gmail.com>
Cc: Linus Walleij <linus.walleij@stericsson.com>,
linux-kernel@vger.kernel.org, Stephen Warren <swarren@nvidia.com>,
Grant Likely <grant.likely@secretlab.ca>,
Barry Song <21cnbao@gmail.com>,
Shawn Guo <shawn.guo@freescale.com>,
Thomas Abraham <thomas.abraham@linaro.org>,
Dong Aisheng <dong.aisheng@linaro.org>,
Rajendra Nayak <rajendra.nayak@linaro.org>,
Haojian Zhuang <haojian.zhuang@marvell.com>
Subject: Re: [PATCH v6] pinctrl: add a pin config interface
Date: Tue, 13 Dec 2011 13:23:16 +0100 [thread overview]
Message-ID: <CACRpkdYN9e3L3GD0T6FEYVbHd4nCTfnDSF-M6LexfHUNJ2n+Ww@mail.gmail.com> (raw)
In-Reply-To: <CAN1soZw=51caZjEoxBx8ch0KiE-kgHQFA1amRcTOyDDKe5Ymzw@mail.gmail.com>
On Tue, Dec 13, 2011 at 8:21 AM, Haojian Zhuang
<haojian.zhuang@gmail.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
next prev parent reply other threads:[~2011-12-13 12:23 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-09 11:57 [PATCH v6] pinctrl: add a pin config interface Linus Walleij
2011-12-12 6:19 ` Haojian Zhuang
2011-12-13 0:22 ` Linus Walleij
2011-12-13 7:21 ` Haojian Zhuang
2011-12-13 12:23 ` Linus Walleij [this message]
2011-12-13 21:49 ` Stephen Warren
2011-12-13 22:56 ` Linus Walleij
2011-12-12 10:56 ` Domenico Andreoli
2011-12-13 12:19 ` Linus Walleij
2011-12-14 7:04 ` Chanho Park
2011-12-14 9:05 ` Linus Walleij
2011-12-14 15:44 ` Stephen Warren
2011-12-14 19:37 ` Linus Walleij
2012-01-18 7:16 ` Thomas Abraham
2012-01-19 16:58 ` Linus Walleij
2012-01-19 18:14 ` Thomas Abraham
[not found] ` <CAJuYYwTP8a4KYDrJ2o9Wmt4jo_DvLviy75T90JnV7Hw10Y+ZXw@mail.gmail.com>
[not found] ` <CACRpkdYwx3O42aC8F+DMV1GL0ce62ZhChOQYdbd7-syunsgBOg@mail.gmail.com>
2012-01-20 15:59 ` Thomas Abraham
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=CACRpkdYN9e3L3GD0T6FEYVbHd4nCTfnDSF-M6LexfHUNJ2n+Ww@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=21cnbao@gmail.com \
--cc=dong.aisheng@linaro.org \
--cc=grant.likely@secretlab.ca \
--cc=haojian.zhuang@gmail.com \
--cc=haojian.zhuang@marvell.com \
--cc=linus.walleij@stericsson.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rajendra.nayak@linaro.org \
--cc=shawn.guo@freescale.com \
--cc=swarren@nvidia.com \
--cc=thomas.abraham@linaro.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).