From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: An extremely simplified pinctrl bindings proposal
Date: Mon, 6 Feb 2012 11:03:15 -0800 [thread overview]
Message-ID: <20120206190315.GU1426@atomide.com> (raw)
In-Reply-To: <CACRpkdbtTPSoX1x4aBtNVGZ2Qex9t77D09V9JgON_jfShQdx6w@mail.gmail.com>
* Linus Walleij <linus.walleij@linaro.org> [120206 08:58]:
> On Mon, Feb 6, 2012 at 6:53 AM, Stephen Warren <swarren@nvidia.com> wrote:
>
> I will certainly finalize the pinctrl subsystem as-is, adding the
> pin configurations states as the last major piece. If for nothing
> else it provides some understanding of the problem space.
>
> I think we should keep both for the time being and consider the
> alternative approach when patches appear. So if/when someone
> creates a new subsystem like this, drivers can move over to it on a
> per-driver basis. If there are zero drivers left in pinctrl it can be
> deleted.
Yes it seems that we can easily do both. So far the only
change needed for pinctrl drivers containing no data is that
we should make the string names optional and structure debugfs
around the physical register addresses instead. I'm basically
just setting the mux register physcal address as the pin name
for now to work around this.
Regards,
Tony
next prev parent reply other threads:[~2012-02-06 19:03 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-05 5:31 An extremely simplified pinctrl bindings proposal Stephen Warren
2012-02-05 6:07 ` Richard Zhao
2012-02-06 3:07 ` Thomas Abraham
2012-02-06 5:44 ` Stephen Warren
2012-02-06 4:20 ` Linus Walleij
2012-02-06 5:53 ` Stephen Warren
2012-02-06 17:29 ` Linus Walleij
2012-02-06 19:03 ` Tony Lindgren [this message]
2012-02-06 19:56 ` Linus Walleij
2012-02-06 21:04 ` Tony Lindgren
2012-02-06 23:15 ` Linus Walleij
2012-02-06 23:57 ` Tony Lindgren
2012-02-07 1:07 ` Linus Walleij
2012-02-07 5:28 ` Stephen Warren
2012-02-06 19:41 ` Mark Brown
2012-02-06 18:57 ` Tony Lindgren
2012-02-06 19:05 ` Mitch Bradley
2012-02-06 19:26 ` Linus Walleij
2012-02-06 21:24 ` Mitch Bradley
2012-02-07 5:33 ` Stephen Warren
2012-02-07 7:07 ` Mitch Bradley
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=20120206190315.GU1426@atomide.com \
--to=tony@atomide.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).