From: Heiner Kallweit <hkallweit1@gmail.com>
To: Jerome Brunet <jbrunet@baylibre.com>,
Kevin Hilman <khilman@baylibre.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
Neil Armstrong <narmstrong@baylibre.com>,
linux-amlogic@lists.infradead.org, linux-crypto@vger.kernel.org,
Stephen Boyd <sboyd@codeaurora.org>,
Michael Turquette <mturquette@baylibre.com>
Cc: linux-clk@vger.kernel.org, devicetree@vger.kernel.org
Subject: [PATCH v3 2/4] ARM64: dts: meson-gx: add clock to DT binding documentation for hwrng
Date: Wed, 22 Feb 2017 07:59:08 +0100 [thread overview]
Message-ID: <86db7397-8355-0d07-5180-c78d6cd06c84@gmail.com> (raw)
In-Reply-To: <4e2d12e5-f75b-3ac6-a3f7-18e8a8b7283b@gmail.com>
Add clock to DT binding documentation.
Signed-off-by: Heiner Kallweit <hkallweit1@gmail.com>
---
v2:
- splitted first version of patch into two
- add DT binding documentation
- mention that clock is optional
- replace spaces with tabs in DT binding example
v3:
- splitted DT extension and binding documentation update into two patches
---
Documentation/devicetree/bindings/rng/amlogic,meson-rng.txt | 11 +++++++++--
1 file changed, 9 insertions(+), 2 deletions(-)
diff --git a/Documentation/devicetree/bindings/rng/amlogic,meson-rng.txt b/Documentation/devicetree/bindings/rng/amlogic,meson-rng.txt
index 202f2d09..4d403645 100644
--- a/Documentation/devicetree/bindings/rng/amlogic,meson-rng.txt
+++ b/Documentation/devicetree/bindings/rng/amlogic,meson-rng.txt
@@ -6,9 +6,16 @@ Required properties:
- compatible : should be "amlogic,meson-rng"
- reg : Specifies base physical address and size of the registers.
+Optional properties:
+
+- clocks : phandle to the following named clocks
+- clock-names: Name of core clock, must be "core"
+
Example:
rng {
- compatible = "amlogic,meson-rng";
- reg = <0x0 0xc8834000 0x0 0x4>;
+ compatible = "amlogic,meson-rng";
+ reg = <0x0 0xc8834000 0x0 0x4>;
+ clocks = <&clkc CLKID_RNG0>;
+ clock-names = "core";
};
--
2.11.1
next prev parent reply other threads:[~2017-02-22 6:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-22 6:55 [PATCH v3 1/3] clk: meson-gxbb: expose clock CLKID_RNG0 Heiner Kallweit
2017-02-22 6:59 ` Heiner Kallweit [this message]
2017-02-27 22:34 ` [PATCH v3 2/4] ARM64: dts: meson-gx: add clock to DT binding documentation for hwrng Rob Herring
[not found] ` <4e2d12e5-f75b-3ac6-a3f7-18e8a8b7283b-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2017-02-22 7:00 ` [PATCH v3 3/4] ARM64: dts: meson-gx: add clock CLKID_RNG0 to hwrng node Heiner Kallweit
2017-02-22 7:02 ` [PATCH v3 4/4] hwrng: meson: add clock handling to driver Heiner Kallweit
2017-02-27 13:28 ` [PATCH v3 1/3] clk: meson-gxbb: expose clock CLKID_RNG0 Neil Armstrong
2017-03-16 10:07 ` Herbert Xu
2017-03-16 18:24 ` Kevin Hilman
2017-03-17 8:30 ` Herbert Xu
[not found] ` <20170317083032.GA18512-lOAM2aK0SrRLBo1qDEOMRrpzq4S04n8Q@public.gmane.org>
2017-03-17 23:05 ` Kevin Hilman
2017-03-22 15:24 ` Kevin Hilman
2017-03-23 1:43 ` Michael Turquette
2017-03-23 7:56 ` Herbert Xu
2017-03-28 22:07 ` Michael Turquette
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=86db7397-8355-0d07-5180-c78d6cd06c84@gmail.com \
--to=hkallweit1@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=jbrunet@baylibre.com \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=narmstrong@baylibre.com \
--cc=sboyd@codeaurora.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).