From: Simon Horman <horms@verge.net.au>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: Magnus Damm <magnus.damm@gmail.com>,
Shinobu Uehara <shinobu.uehara.xc@renesas.com>,
Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>,
linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH] ARM: dts: r8a7794: Correct hsusb parent clock
Date: Tue, 15 Nov 2016 18:56:03 +0100 [thread overview]
Message-ID: <20161115175602.GF3979@verge.net.au> (raw)
In-Reply-To: <1478545627-32280-1-git-send-email-geert+renesas@glider.be>
On Mon, Nov 07, 2016 at 08:07:07PM +0100, Geert Uytterhoeven wrote:
> The parent clock of the HSUSB clock is the HP clock, not the MP clock.
>
> Fixes: c7bab9f929e51761 ("ARM: shmobile: r8a7794: Add USB clocks to device tree")
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
Thanks, I have queued this up.
I also checked that the correct parent is used on the r8a7790, 1 and 3.
HSUSB is not present on the r8a7792.
> ---
> arch/arm/boot/dts/r8a7794.dtsi | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/arm/boot/dts/r8a7794.dtsi b/arch/arm/boot/dts/r8a7794.dtsi
> index 01816ac775a8d177..7d9f0601d3ca8def 100644
> --- a/arch/arm/boot/dts/r8a7794.dtsi
> +++ b/arch/arm/boot/dts/r8a7794.dtsi
> @@ -1262,7 +1262,7 @@
> mstp7_clks: mstp7_clks@e615014c {
> compatible = "renesas,r8a7794-mstp-clocks", "renesas,cpg-mstp-clocks";
> reg = <0 0xe615014c 0 4>, <0 0xe61501c4 0 4>;
> - clocks = <&mp_clk>, <&mp_clk>,
> + clocks = <&mp_clk>, <&hp_clk>,
> <&zs_clk>, <&p_clk>, <&p_clk>, <&zs_clk>,
> <&zs_clk>, <&p_clk>, <&p_clk>, <&p_clk>, <&p_clk>,
> <&zx_clk>;
> --
> 1.9.1
>
prev parent reply other threads:[~2016-11-15 17:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-07 19:07 [PATCH] ARM: dts: r8a7794: Correct hsusb parent clock Geert Uytterhoeven
2016-11-08 12:16 ` Yoshihiro Shimoda
2016-11-09 7:34 ` Simon Horman
2016-11-15 17:56 ` Simon Horman [this message]
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=20161115175602.GF3979@verge.net.au \
--to=horms@verge.net.au \
--cc=geert+renesas@glider.be \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=shinobu.uehara.xc@renesas.com \
--cc=yoshihiro.shimoda.uh@renesas.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.