From: Seraphin Bonnaffe <seraphin.bonnaffe@st.com>
To: <b29396@freescale.com>, <linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<lee.jones@linaro.org>, <maxime.coquelin@st.com>
Cc: <sameo@linux.intel.com>, <grant.likely@linaro.org>,
<robh+dt@kernel.org>, <pawel.moll@arm.com>,
<mark.rutland@arm.com>, <ijc+devicetree@hellion.org.uk>,
<galak@codeaurora.org>, <arnd@arndb.de>,
<seraphin.bonnaffe@st.com>
Subject: [RFC PATCH 0/2] mfd: syscon: declare holes in syscon register maps
Date: Tue, 7 Oct 2014 15:22:26 +0200 [thread overview]
Message-ID: <1412688148-20835-1-git-send-email-seraphin.bonnaffe@st.com> (raw)
In-Reply-To: <54244655.1090801@st.com>
In reply to mail: Holes management in syscon driver.
Hi Dong, Maxime, Lee, all,
Regmap also offers .rd_table and .wr_table structures that can be used to
specify valid ranges within agiven regmap configuration.
This patch uses these structures to declare holes in a syscon instance.
It takes the description from DT, and fills in the structures accordingly.
Can I have your opinion on this implementation ?
Thanks and Regards,
Seraphin
Seraphin Bonnaffe (2):
mfd: syscon: Document new DT binding "holes"
mfd: syscon: specify rd_table and wr_table from DT
Documentation/devicetree/bindings/mfd/syscon.txt | 5 ++++
drivers/mfd/syscon.c | 35 ++++++++++++++++++++++++
2 files changed, 40 insertions(+)
--
1.9.1
next parent reply other threads:[~2014-10-07 13:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <54244655.1090801@st.com>
2014-10-07 13:22 ` Seraphin Bonnaffe [this message]
2014-10-07 13:22 ` [RFC PATCH 1/2] mfd: syscon: Document new DT binding "holes" Seraphin Bonnaffe
2014-10-07 13:22 ` [RFC PATCH 2/2] mfd: syscon: specify rd_table and wr_table from DT Seraphin Bonnaffe
2014-10-08 11:12 ` [RFC PATCH 0/2] mfd: syscon: declare holes in syscon register maps Maxime Coquelin
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=1412688148-20835-1-git-send-email-seraphin.bonnaffe@st.com \
--to=seraphin.bonnaffe@st.com \
--cc=arnd@arndb.de \
--cc=b29396@freescale.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=grant.likely@linaro.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=maxime.coquelin@st.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=sameo@linux.intel.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
all inboxes | Powered by JetHome®