From: Orson Zhai <orson.zhai@unisoc.com>
To: Lee Jones <lee.jones@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Arnd Bergmann <arnd@arndb.de>
Cc: <devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<steven.tang@unisoc.com>, Orson Zhai <orson.zhai@unisoc.com>
Subject: [PATCH 0/2] Add syscon name and #cells support
Date: Thu, 14 Nov 2019 19:45:23 +0800 [thread overview]
Message-ID: <20191114114525.12675-1-orson.zhai@unisoc.com> (raw)
Our SoCs have a lot of glabal registers which is hard to be managed in
current syscon structure.
Same register's offset is different in different SoCs. We used chip
config macro to manage them which prevents driver to be compiled in
all-in-one image.
After talking with Arnd and Rob at Linaro Connect 2017, I got the
idea to extend syscon with #cells support. And furthe, I added syscon
names support to help access multiple syscon nodes more easier.
These patches has been tested in our internal tree about 2 years.
They have no side effect to current syscon consumer.
Thanks,
Orson
--------------------
Orson Zhai (2):
dt-bindings: Add syscon-names support
mfd: syscon: Add syscon-names and phandle args support
.../devicetree/bindings/mfd/syscon.txt | 36 ++++++++++
drivers/mfd/syscon.c | 65 +++++++++++++++++++
include/linux/mfd/syscon.h | 22 +++++++
3 files changed, 123 insertions(+)
--
2.18.0
next reply other threads:[~2019-11-14 12:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-14 11:45 Orson Zhai [this message]
2019-11-14 11:45 ` [PATCH 1/2] dt-bindings: Add syscon-names support Orson Zhai
2019-11-15 9:33 ` Arnd Bergmann
2019-11-18 8:39 ` Orson Zhai
2019-11-19 14:20 ` Arnd Bergmann
2019-11-19 14:46 ` Arnd Bergmann
2019-11-20 15:49 ` Orson Zhai
2019-11-14 11:45 ` [PATCH 2/2] mfd: syscon: Add syscon-names and phandle args support Orson Zhai
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=20191114114525.12675-1-orson.zhai@unisoc.com \
--to=orson.zhai@unisoc.com \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=steven.tang@unisoc.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).