From: jbrunet@baylibre.com (Jerome Brunet)
To: linus-amlogic@lists.infradead.org
Subject: [PATCH 1/2] hwrng: meson: expose RNG0 clock via DT
Date: Mon, 20 Feb 2017 11:07:23 +0100 [thread overview]
Message-ID: <1487585243.3734.3.camel@baylibre.com> (raw)
In-Reply-To: <a02b078d-9171-cf66-d5d8-84259f9f9a88@gmail.com>
On Sun, 2017-02-19 at 21:33 +0100, Heiner Kallweit wrote:
> Expose the RNG0 clock via DT.
>
> Signed-off-by: Heiner Kallweit <hkallweit1@gmail.com>
> ---
> ?arch/arm64/boot/dts/amlogic/meson-gx.dtsi???| 2 +-
> ?arch/arm64/boot/dts/amlogic/meson-gxbb.dtsi | 5 +++++
> ?include/dt-bindings/clock/gxbb-clkc.h???????| 1 +
> ?3 files changed, 7 insertions(+), 1 deletion(-)
>
> diff --git a/arch/arm64/boot/dts/amlogic/meson-gx.dtsi
> b/arch/arm64/boot/dts/amlogic/meson-gx.dtsi
> index 5d995f77..620495a4 100644
> --- a/arch/arm64/boot/dts/amlogic/meson-gx.dtsi
> +++ b/arch/arm64/boot/dts/amlogic/meson-gx.dtsi
> @@ -380,7 +380,7 @@
> ? #size-cells = <2>;
> ? ranges = <0x0 0x0 0x0 0xc8834000 0x0
> 0x2000>;
> ?
> - rng {
> + hwrng: rng {
> ? compatible = "amlogic,meson-rng";
> ? reg = <0x0 0x0 0x0 0x4>;
> ? };
> diff --git a/arch/arm64/boot/dts/amlogic/meson-gxbb.dtsi
> b/arch/arm64/boot/dts/amlogic/meson-gxbb.dtsi
> index 04b3324b..a375cb21 100644
> --- a/arch/arm64/boot/dts/amlogic/meson-gxbb.dtsi
> +++ b/arch/arm64/boot/dts/amlogic/meson-gxbb.dtsi
> @@ -524,3 +524,8 @@
> ?&vpu {
> ? compatible = "amlogic,meson-gxbb-vpu", "amlogic,meson-gx-
> vpu";
> ?};
> +
> +&hwrng {
> + clocks = <&clkc CLKID_RNG0>;
> + clock-names = "core";
> +};
> diff --git a/include/dt-bindings/clock/gxbb-clkc.h b/include/dt-
> bindings/clock/gxbb-clkc.h
> index 692846c7..473676b1 100644
> --- a/include/dt-bindings/clock/gxbb-clkc.h
> +++ b/include/dt-bindings/clock/gxbb-clkc.h
> @@ -15,6 +15,7 @@
> ?#define CLKID_SPI 34
> ?#define CLKID_I2C 22
> ?#define CLKID_SAR_ADC 23
> +#define CLKID_RNG0 25
Shouldn't you comment out the corresponding "define" in
drivers/clk/meson/gxbb.h ?
I don't know if it is rule, but we usually "expose" the clock (moving
the define from drivers/clk/meson/gxbb.h to include/dt-
bindings/clock/gxbb-clkc.h) in a dedicated patch, with the subject
starting with "clk: gxbb: expose foobar clock". It helps the
maintainers of the subsystem to give their ack.
For this to happen, please remember the patch should be sent to them as
well. Here you are missing the clock and dt guys:
* Stephen Boyd <sboyd@codeaurora.org>
* Michael Turquette <mturquette@baylibre.com>
* linux-clk at vger.kernel.org
* devicetree at vger.kernel.org
scripts/get_maintainer.pl can help you finding all people your patch
should be sent to.
The remaining part of this patch involves DT, so the subject should
start with "ARM64: dts: meson-gx:"
You also need to add devicetree at vger.kernel.org in CC.
Apart from these minor remarks, the patchset looks good to me.
Thx !
> ?#define CLKID_ETH 36
> ?#define CLKID_USB0 50
> ?#define CLKID_USB1 51
next prev parent reply other threads:[~2017-02-20 10:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-19 20:30 [PATCH 0/2] hwrng: meson: add clock handling Heiner Kallweit
2017-02-19 20:33 ` [PATCH 1/2] hwrng: meson: expose RNG0 clock via DT Heiner Kallweit
2017-02-20 10:07 ` Jerome Brunet [this message]
2017-02-19 20:35 ` [PATCH 2/2] hwrng: meson: add clock handling to driver Heiner Kallweit
2017-02-20 11:37 ` PrasannaKumar Muralidharan
2017-02-21 1:58 ` [PATCH 0/2] hwrng: meson: add clock handling Neil Armstrong
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=1487585243.3734.3.camel@baylibre.com \
--to=jbrunet@baylibre.com \
--cc=linus-amlogic@lists.infradead.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).