From: Mitch Bradley <wmb@firmworks.com>
To: Stephen Warren <swarren@nvidia.com>
Cc: "devicetree-discuss@lists.ozlabs.org"
<devicetree-discuss@lists.ozlabs.org>,
"cjb@laptop.org" <cjb@laptop.org>,
Dong Aisheng <dongas86@gmail.com>,
"ext Tony Lindgren (tony@atomide.com)" <tony@atomide.com>,
"Linus Walleij (linus.walleij@linaro.org)"
<linus.walleij@linaro.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"rob.herring@calxeda.com" <rob.herring@calxeda.com>,
"Grant Likely (grant.likely@secretlab.ca)"
<grant.likely@secretlab.ca>,
Thomas Abraham <thomas.abraham@linaro.org>,
"kernel@pengutronix.de" <kernel@pengutronix.de>,
"Simon Glass (sjg@chromium.org)" <sjg@chromium.org>,
Shawn Guo <shawn.guo@linaro.org>,
Dong Aisheng-B29396 <B29396@freescale.com>,
"Sascha Hauer (s.hauer@pengutronix.de)" <s.hauer@pengutronix.de>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: An extremely simplified pinctrl bindings proposal
Date: Mon, 06 Feb 2012 09:05:24 -1000 [thread overview]
Message-ID: <4F302474.1020701@firmworks.com> (raw)
In-Reply-To: <74CDBE0F657A3D45AFBB94109FB122FF178E5D3160@HQMAIL01.nvidia.com>
I like the general approach of simplifying the pinctrl thing, as the
previous approach did not appear to be converging.
One possible name would be "gpconfig" - for general purpose configuration.
The register access model in the strawman proposal is probably too
simple. 32-bit memory mapped registers are certainly the most common
subcase on ARM, but there are many other cases that occur in practice:
* Registers that must be accessed with 8, 16, or 64-bit cycles.
* Registers that have side effects on read, so read-mask-write must be
avoided
* Registers accessed via an index/data cycle pair, thus having locking
requirements
* Registers that must be read after being written, or otherwise
requiring some sort of memory-ordering enforcement.
* Time delays between pairs of writes
* PCI configuration registers, which often have some combination of the
above
* Registers behind serial buses like I2C
Both Open Firmware and ACPI have addressed this general problem. In
addition to a numeric identifier for the register, you need to specify
the access semantics. It's difficult to finitely enumerate all possible
cases, but you can get to 99.9% with a modest number of access models,
and then add new models as needed.
next prev parent reply other threads:[~2012-02-06 19:05 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
[not found] ` <CACRpkdahin4srDh7dphgvq306gjz7CGP=h4dVkUY+w0z0wpXRQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-02-06 5:53 ` Stephen Warren
2012-02-06 17:29 ` Linus Walleij
[not found] ` <CACRpkdbtTPSoX1x4aBtNVGZ2Qex9t77D09V9JgON_jfShQdx6w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-02-06 19:03 ` Tony Lindgren
[not found] ` <20120206190315.GU1426-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
2012-02-06 19:56 ` Linus Walleij
[not found] ` <CACRpkdZthbejmTqRJAWHb8jU-p8LPT_+zj_CY1q0voMb4FKz2Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-02-06 21:04 ` Tony Lindgren
2012-02-06 23:15 ` Linus Walleij
[not found] ` <CACRpkdYrbD3PpJ3wb69yb3Ya8SeZJnPpgJdtttjWTkS5xsD-4g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-02-06 23:57 ` Tony Lindgren
[not found] ` <20120206235733.GY1426-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
2012-02-07 1:07 ` Linus Walleij
2012-02-07 5:28 ` Stephen Warren
[not found] ` <4F2F6AE2.1040504-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2012-02-06 19:41 ` Mark Brown
[not found] ` <74CDBE0F657A3D45AFBB94109FB122FF178E5D3160-C7FfzLzN0UxDw2glCA4ptUEOCMrvLtNR@public.gmane.org>
2012-02-06 18:57 ` Tony Lindgren
2012-02-06 19:05 ` Mitch Bradley [this message]
2012-02-06 19:26 ` Linus Walleij
[not found] ` <CACRpkdYt-L+an5DTdYkS5Hi+18-rszAt7hXwZNUNVK-d0UaCWA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-02-06 21:24 ` Mitch Bradley
[not found] ` <4F302474.1020701-D5eQfiDGL7eakBO8gow8eQ@public.gmane.org>
2012-02-07 5:33 ` Stephen Warren
[not found] ` <4F30B79C.4030404-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
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=4F302474.1020701@firmworks.com \
--to=wmb@firmworks.com \
--cc=B29396@freescale.com \
--cc=cjb@laptop.org \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=dongas86@gmail.com \
--cc=grant.likely@secretlab.ca \
--cc=kernel@pengutronix.de \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rob.herring@calxeda.com \
--cc=s.hauer@pengutronix.de \
--cc=shawn.guo@linaro.org \
--cc=sjg@chromium.org \
--cc=swarren@nvidia.com \
--cc=thomas.abraham@linaro.org \
--cc=tony@atomide.com \
/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).