All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dirk Behme <dirk.behme@gmail.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH v2] clk: shmobile: r8a7795: Add SDHI clocks
Date: Thu, 14 Jan 2016 19:02:02 +0000	[thread overview]
Message-ID: <5697F0AA.90800@gmail.com> (raw)
In-Reply-To: <1450951761-3160-1-git-send-email-dirk.behme@gmail.com>

On 14.01.2016 19:24, Geert Uytterhoeven wrote:
> Hi Dirk,
>
> On Sat, Jan 9, 2016 at 7:42 AM, Dirk Behme <dirk.behme@gmail.com> wrote:
>> On 24.12.2015 11:09, Dirk Behme wrote:
>>> Add R8A7795 SDHI clocks.
>
> Thanks for your patch!
>
>>> Signed-off-by: Dirk Behme <dirk.behme@gmail.com>
>>> ---
>>> Changes in v2: Add the missing *H clocks and correct the dividers.
>>>
>>> This replaces v1
>>>
>>> http://www.spinics.net/lists/linux-sh/msg47464.html
>>>
>>>    drivers/clk/shmobile/r8a7795-cpg-mssr.c | 13 ++++++++++++-
>>>    1 file changed, 12 insertions(+), 1 deletion(-)
>>>
>>> diff --git a/drivers/clk/shmobile/r8a7795-cpg-mssr.c
>>> b/drivers/clk/shmobile/r8a7795-cpg-mssr.c
>>> index 05479e6..f30ed32 100644
>>> --- a/drivers/clk/shmobile/r8a7795-cpg-mssr.c
>>> +++ b/drivers/clk/shmobile/r8a7795-cpg-mssr.c
>>> @@ -100,8 +100,15 @@ static const struct cpg_core_clk r8a7795_core_clks[]
>>> __initconst = {
>>>          DEF_FIXED("s3d2",       R8A7795_CLK_S3D2,  CLK_S3,         2, 1),
>>>          DEF_FIXED("s3d4",       R8A7795_CLK_S3D4,  CLK_S3,         4, 1),
>>>          DEF_FIXED("cl",         R8A7795_CLK_CL,    CLK_PLL1_DIV2, 48, 1),
>>> +       DEF_FIXED("sd0h",       R8A7795_CLK_SD0H,  CLK_PLL1_DIV2,  2, 1),
>>> +       DEF_FIXED("sd0",        R8A7795_CLK_SD0,   CLK_PLL1_DIV2,  8, 1),
>>> +       DEF_FIXED("sd1h",       R8A7795_CLK_SD1H,  CLK_PLL1_DIV2,  2, 1),
>>> +       DEF_FIXED("sd1",        R8A7795_CLK_SD1,   CLK_PLL1_DIV2,  8, 1),
>>> +       DEF_FIXED("sd2h",       R8A7795_CLK_SD2H,  CLK_PLL1_DIV2,  2, 1),
>>> +       DEF_FIXED("sd2",        R8A7795_CLK_SD2,   CLK_PLL1_DIV2,  8, 1),
>>> +       DEF_FIXED("sd3h",       R8A7795_CLK_SD3H,  CLK_PLL1_DIV2,  2, 1),
>>> +       DEF_FIXED("sd3",        R8A7795_CLK_SD3,   CLK_PLL1_DIV2,  8, 1),
>
> The dividers for these clocks are not fixed, they are controlled by the
> SDnCKCR registers.
>
> Unfortunately the register layout is more complicated than on R-Car Gen2, so
> you can no longer use clk_register_divider_table(), but have to write a custom
> clock driver.
>
> For an initial version, a simple "read-only" version that just calls
> clk_register_fixed_factor() with divider values read from the hardware
> registers may be good enough. But for full support, you need a driver that
> can program the registers, too.
>
> Just using fixed dividers like you did won't work, as the boot loader/reset
> state may be different.
> E.g. on my board, which has a 16.66666 MHz crystal, the initial state according
> to the register values is:
>    - sd[0-2]h are stopped,
>    - sd[0-2] run at 25 MHz,
>    - sd3h runs at 400 MHz,
>    - sd3 runs at 100 MHz.


Hmm, why do I get

sh_mobile_sdhi ee140000.mmc: mmc0 base at 0xee140000 clock rate 99 MHz

(or 199MHz considering the clock workaround) and for the other SDx 
with this patch, then?

Best regards

Dirk


>>> @@ -120,6 +127,10 @@ static const struct mssr_mod_clk r8a7795_mod_clks[]
>>> __initconst = {
>>>          DEF_MOD("sys-dmac1",             218,   R8A7795_CLK_S3D1),
>>>          DEF_MOD("sys-dmac0",             219,   R8A7795_CLK_S3D1),
>>>          DEF_MOD("scif2",                 310,   R8A7795_CLK_S3D4),
>>> +       DEF_MOD("sdif3",                 311,   R8A7795_CLK_SD3),
>>> +       DEF_MOD("sdif2",                 312,   R8A7795_CLK_SD2),
>>> +       DEF_MOD("sdif1",                 313,   R8A7795_CLK_SD1),
>>> +       DEF_MOD("sdif0",                 314,   R8A7795_CLK_SD0),
>
> This part is OK.
>
> Gr{oetje,eeting}s,
>
>                          Geert
>
> --
> Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@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
>


  parent reply	other threads:[~2016-01-14 19:02 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-24 10:09 [PATCH v2] clk: shmobile: r8a7795: Add SDHI clocks Dirk Behme
2016-01-09  6:42 ` Dirk Behme
2016-01-14 18:24 ` Geert Uytterhoeven
2016-01-15 10:11   ` Dirk Behme
2016-01-15 10:11     ` Dirk Behme
2016-01-15 10:20     ` Geert Uytterhoeven
2016-01-15 10:20       ` Geert Uytterhoeven
2016-01-17  9:47       ` Dirk Behme
2016-01-17  9:47         ` Dirk Behme
2016-01-20  8:16         ` Geert Uytterhoeven
2016-01-20  8:16           ` Geert Uytterhoeven
2016-01-22 12:30           ` Dirk Behme
2016-01-22 12:30             ` Dirk Behme
2016-01-14 18:45 ` Michael Turquette
2016-01-14 19:02 ` Dirk Behme [this message]
2016-01-14 19:06 ` Geert Uytterhoeven
  -- strict thread matches above, loose matches on Subject: below --
2016-01-30  6:33 [PATCH v2] clk: shmobile: r8a7795: Add SD divider support Dirk Behme
2016-01-30  6:33 ` Dirk Behme
2016-01-30  6:33 ` Dirk Behme
2016-02-04 19:30 ` Wolfram Sang
2016-02-04 19:30   ` Wolfram Sang
2016-02-04 19:30   ` Wolfram Sang
2016-02-08 15:32   ` Geert Uytterhoeven
2016-02-08 15:32     ` Geert Uytterhoeven

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=5697F0AA.90800@gmail.com \
    --to=dirk.behme@gmail.com \
    --cc=linux-sh@vger.kernel.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 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.