From: linus.walleij@linaro.org (Linus Walleij)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3] pinctrl: add support for group and pinmux states
Date: Mon, 16 Jan 2012 10:46:00 +0100 [thread overview]
Message-ID: <CACRpkdaLEasbm-_Vg9VzD+EwwJst1yLQ1sruPaHtFASxcRXXUA@mail.gmail.com> (raw)
In-Reply-To: <7FE21149F4667147B645348EC60578850910C3@039-SN2MPN1-013.039d.mgd.msft.net>
On Mon, Jan 16, 2012 at 9:26 AM, Dong Aisheng-B29396
<B29396@freescale.com> wrote:
> The question is that we allow customer to define pingroup state and this is
> independent on pinctrl core.
You are right, this patch might not be helpful :-(
I had bad dreams after writing it, and I think I also missed Stephens point,
that the pinctrl core should iteratively call the config interface of the
controller while walking a config.
I am authoring a different proposal which is much closer to the pinmux
maps, and thus closer to what you're currently doing with the device
tree bindings and all.
Hold on, hope to post this later today.
Linus Walleij
prev parent reply other threads:[~2012-01-16 9:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-16 0:16 [PATCH v3] pinctrl: add support for group and pinmux states Linus Walleij
2012-01-16 8:26 ` Dong Aisheng-B29396
2012-01-16 9:46 ` Linus Walleij [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=CACRpkdaLEasbm-_Vg9VzD+EwwJst1yLQ1sruPaHtFASxcRXXUA@mail.gmail.com \
--to=linus.walleij@linaro.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 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).