From: Fabrice Gasnier <fabrice.gasnier@st.com>
To: <lee.jones@linaro.org>, <robh+dt@kernel.org>, <alexandre.torgue@st.com>
Cc: <mcoquelin.stm32@gmail.com>, <arnd@arndb.de>,
<mark.rutland@arm.com>, <gabriel.fernandez@st.com>,
<fabrice.gasnier@st.com>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
<linux-stm32@st-md-mailman.stormreply.com>,
<linux-arm-kernel@lists.infradead.org>
Subject: [PATCH 1/3] dt-bindings: mfd: syscon: Add optional clock support
Date: Tue, 27 Nov 2018 17:48:15 +0100 [thread overview]
Message-ID: <1543337297-21873-2-git-send-email-fabrice.gasnier@st.com> (raw)
In-Reply-To: <1543337297-21873-1-git-send-email-fabrice.gasnier@st.com>
Some system control registers need to be clocked, so the registers can
be accessed. Add an optional clock.
Signed-off-by: Fabrice Gasnier <fabrice.gasnier@st.com>
---
Documentation/devicetree/bindings/mfd/syscon.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/mfd/syscon.txt b/Documentation/devicetree/bindings/mfd/syscon.txt
index 25d9e9c..a9aaa51 100644
--- a/Documentation/devicetree/bindings/mfd/syscon.txt
+++ b/Documentation/devicetree/bindings/mfd/syscon.txt
@@ -17,6 +17,7 @@ Optional property:
- reg-io-width: the size (in bytes) of the IO accesses that should be
performed on the device.
- hwlocks: reference to a phandle of a hardware spinlock provider node.
+- clocks: phandle to the syscon clock
Examples:
gpr: iomuxc-gpr@20e0000 {
--
1.9.1
next prev parent reply other threads:[~2018-11-27 16:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-27 16:48 [PATCH 0/3] mfd: syscon: Add optional clock support needed on stm32 Fabrice Gasnier
2018-11-27 16:48 ` Fabrice Gasnier [this message]
2018-12-11 22:16 ` [PATCH 1/3] dt-bindings: mfd: syscon: Add optional clock support Rob Herring
2018-12-12 8:18 ` Fabrice Gasnier
2018-11-27 16:48 ` [PATCH 2/3] " Fabrice Gasnier
2018-11-27 16:48 ` [PATCH 3/3] ARM: dts: stm32: Add clock on stm32mp157c syscfg Fabrice Gasnier
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=1543337297-21873-2-git-send-email-fabrice.gasnier@st.com \
--to=fabrice.gasnier@st.com \
--cc=alexandre.torgue@st.com \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=gabriel.fernandez@st.com \
--cc=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mark.rutland@arm.com \
--cc=mcoquelin.stm32@gmail.com \
--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 NNTP newsgroup(s).