From: Stephen Boyd <stephen.boyd@linaro.org>
To: Rob Herring <robh+dt@kernel.org>, Frank Rowand <frowand.list@gmail.com>
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
Russell King - ARM Linux <linux@armlinux.org.uk>,
devicetree-spec@vger.kernel.org
Subject: [PATCH v5 0/4] OF phandle nexus support + GPIO nexus
Date: Tue, 30 Jan 2018 18:36:14 -0800 [thread overview]
Message-ID: <20180131023618.14292-1-stephen.boyd@linaro.org> (raw)
This is a continutation of my phandle remapping/nexus node series
from a while ago. I finally got around to writing the documentation
in the spec for this, but it's really rough around the edges and
could use some review/suggestions to get it into shape. Please
review!
This is one small chunk of work related to DT overlays for expansion
boards. It would be good to have a way to expose #<list>-cells types of
providers through a connector in a standard way. So we introduce a way
to make "nexus" nodes for these types of properties to remap the consumer
number space to the other side of the connector's number space. It's
basically a copy of the interrupt nexus implementation, but without
the address space matching design and interrupt-parent walking.
Changes since v4:
* Rebased to v4.15
* Reworded spec patch a bit
* Dropped overlay stuff from unittest patch because that's done by dtc now
Changes since v3:
* Added devicetree spec patch
* Rebased to v4.13-rc1
Changes since v2:
* Picked up Linus' ack on the gpio core patch
* Made const stack arrays static (Rob Herring)
* Used of_property_read_u32() instead of open coding (Rob Herring)
Changes since v1:
* Addition of optional pass-thru parameter
* Reduction of strings passed to 1 instead of 3 (or 4 now)
* Updated gpio patch for the new function signature
* Updated test-case for new funciton signature and pass-thru parameter
* Updated kernel-doc to be correct and highlighted difference between this
API and of_parse_phandle_with_args()
Stephen Boyd (3):
Document nexus nodes/specifier remapping
of: Support parsing phandle argument lists through a nexus node
of: unittest: Add phandle remapping test
gpio: Support gpio nexus dt bindings
Kernel:
drivers/gpio/gpiolib-of.c | 4 +-
drivers/of/base.c | 184 ++++++++++++++++++++++++++++
drivers/of/unittest-data/tests-phandle.dtsi | 25 ++++
drivers/of/unittest.c | 120 ++++++++++++++++++
include/linux/of.h | 12 ++
5 files changed, 343 insertions(+), 2 deletions(-)
Spec:
source/devicetree-basics.rst | 206 +++++++++++++++++++++++++++++++++++++++++++
1 file changed, 206 insertions(+)
--
2.7.4
next reply other threads:[~2018-01-31 2:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-31 2:36 Stephen Boyd [this message]
[not found] ` <20180131023618.14292-1-stephen.boyd-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2018-01-31 2:36 ` [PATCH v5 1/4] Document nexus nodes/specifier remapping Stephen Boyd
[not found] ` <20180131023618.14292-2-stephen.boyd-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2018-02-02 20:10 ` Rob Herring
2018-01-31 2:36 ` [PATCH v5 2/4] of: Support parsing phandle argument lists through a nexus node Stephen Boyd
2018-01-31 2:36 ` [PATCH v5 3/4] of: unittest: Add phandle remapping test Stephen Boyd
2018-01-31 2:36 ` [PATCH v5 4/4] gpio: Support gpio nexus dt bindings Stephen Boyd
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=20180131023618.14292-1-stephen.boyd@linaro.org \
--to=stephen.boyd@linaro.org \
--cc=devicetree-spec@vger.kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=robh+dt@kernel.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 read-only IMAP folder(s) and NNTP newsgroup(s).