Re: [PATCH 1/1] clk: renesas: cpg-mssr: r8a7796: add IMR clocks

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 02/21/2017 10:39 PM, Geert Uytterhoeven wrote:

On 02/20/2017 11:38 AM, Geert Uytterhoeven wrote:
Add the IMR[0-1] clocks to the R8A7796 CPG/MSSR driver.

Signed-off-by: Sergei Shtylyov <sergei.shtylyov@xxxxxxxxxxxxxxxxxx>

Reviewed-by: Geert Uytterhoeven <geert+renesas@xxxxxxxxx>

--- linux.orig/drivers/clk/renesas/r8a7796-cpg-mssr.c
+++ linux/drivers/clk/renesas/r8a7796-cpg-mssr.c
@@ -179,6 +179,8 @@ static const struct mssr_mod_clk r8a7796
        DEF_MOD("vin1",                  810,   R8A7796_CLK_S0D2),
        DEF_MOD("vin0",                  811,   R8A7796_CLK_S0D2),
        DEF_MOD("etheravb",              812,   R8A7796_CLK_S0D6),
+       DEF_MOD("imr1",                  822,   R8A7796_CLK_S2D1),
+       DEF_MOD("imr0",                  823,   R8A7796_CLK_S2D1),


According to R-Car Gen3 Hardware Users Manual Rev.0.53E, the parent
clock is S0D2, like on H3 ES2.0.

   Not S0D4? I'd expect that what they call "register access" to be
controlled by the MSSR bits...

Good question...

Will queue in clk-renesas-for-v4.12 with corrected parent clock.

   So, what have you used for 7795 and 7796?

S2D1 for r8a7795 (H3 ES1.0)
S0D2 for r8a7796 (M3-W)

And I planned to use S0D2 for H3 ES2.0, too.

Looks to me we should be using S0D4 for both. And perhaps the 2nd specifier for S0D2.

Gr{oetje,eeting}s,

                        Geert

MBR, Sergei




[Index of Archives]     [Linux Samsung SOC]     [Linux Wireless]     [Linux Kernel]     [ATH6KL]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Samba]     [Device Mapper]

  Powered by Linux