From: geert@linux-m68k.org (Geert Uytterhoeven)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 03/13] ARM: dts: sh73a0: Remove unnecessary clock-output-names properties
Date: Tue, 22 Mar 2016 11:17:48 +0100 [thread overview]
Message-ID: <CAMuHMdWPocvJj8_YfGNUyPnEajEK0uMLv_rj-NVUsWRdAZgWcQ@mail.gmail.com> (raw)
In-Reply-To: <1458610840-15194-4-git-send-email-horms+renesas@verge.net.au>
On Tue, Mar 22, 2016 at 2:40 AM, Simon Horman
<horms+renesas@verge.net.au> wrote:
> * Fixed rate and fixed factor clocks do not require an
> clock-output-names property.
> * Since 07705583e920fef6 ("clk: shmobile: div6: Make clock-output-names
> optional") Renesas div6 clocks do not require a clock-output-names
> property.
>
> In the above cases there is only one clock output and its name is taken
> from that of the clock node.
>
> Accordingly, remove the unnecessary clock-output-names properties and as
> necessary update the node names. The zb_clk is excluded from this rename
> as the MSTP clock driver (clk-mstp.c) explicitly looks for a clock
> named zb_clk for the r8a73a4 and sh73a0 SoCs.
>
> Signed-off-by: Simon Horman <horms+renesas@verge.net.au>
> ---
> arch/arm/boot/dts/sh73a0.dtsi | 88 ++++++++++++++-----------------------------
> 1 file changed, 29 insertions(+), 59 deletions(-)
>
> diff --git a/arch/arm/boot/dts/sh73a0.dtsi b/arch/arm/boot/dts/sh73a0.dtsi
> index bf825ca4f6f7..e697250886ef 100644
> --- a/arch/arm/boot/dts/sh73a0.dtsi
> +++ b/arch/arm/boot/dts/sh73a0.dtsi
> @@ -686,170 +677,149 @@
> clocks = <&pll1_div2_clk>, <0>,
> <&cpg_clocks SH73A0_CLK_PLL2>, <0>;
> #clock-cells = <0>;
> - clock-output-names = "zb";
> };
Same comment here as for r8a73a4:
I'm wondering whether we should keep this one for now?
Dropping it changes the clock name from "zb_clk" to "zb".
--
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert at linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2016-03-22 10:17 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-22 1:40 [PATCH 00/13] ARM, arm64: dts: Remove unnecessary clock-output-names properties Simon Horman
2016-03-22 1:40 ` [PATCH 01/13] ARM: dts: r7s72100: " Simon Horman
2016-03-22 1:40 ` [PATCH 02/13] ARM: dts: r8a73a4: " Simon Horman
2016-03-22 10:17 ` Geert Uytterhoeven
2016-03-23 0:52 ` Simon Horman
2016-03-22 1:40 ` [PATCH 03/13] ARM: dts: sh73a0: " Simon Horman
2016-03-22 10:17 ` Geert Uytterhoeven [this message]
2016-03-22 1:40 ` [PATCH 04/13] ARM: dts: r8a7740: " Simon Horman
2016-03-22 1:40 ` [PATCH 05/13] ARM: dts: r8a7778: " Simon Horman
2016-03-22 1:40 ` [PATCH 06/13] ARM: dts: r8a7779: " Simon Horman
2016-03-22 1:40 ` [PATCH 07/13] ARM: dts: r8a7791: " Simon Horman
2016-03-22 1:40 ` [PATCH 08/13] ARM: dts: r8a7793: " Simon Horman
2016-03-22 1:40 ` [PATCH 09/13] ARM: dts: r8a7794: " Simon Horman
2016-03-22 1:40 ` [PATCH 10/13] ARM: dts: gose: " Simon Horman
2016-03-22 1:40 ` [PATCH 11/13] ARM: dts: koelsch: " Simon Horman
2016-03-22 1:40 ` [PATCH 12/13] ARM: dts: porter: " Simon Horman
2016-03-22 1:40 ` [PATCH 13/13] ARM: dts: lager: " Simon Horman
2016-03-22 10:18 ` [PATCH 00/13] ARM, arm64: dts: " Geert Uytterhoeven
2016-03-23 1:07 ` Simon Horman
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=CAMuHMdWPocvJj8_YfGNUyPnEajEK0uMLv_rj-NVUsWRdAZgWcQ@mail.gmail.com \
--to=geert@linux-m68k.org \
--cc=linux-arm-kernel@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).