From: Dirk Behme <dirk.behme@de.bosch.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>,
Wolfram Sang <wsa@the-dreams.de>
Cc: Dirk Behme <dirk.behme@gmail.com>,
Linux-sh list <linux-sh@vger.kernel.org>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Simon Horman <horms+renesas@verge.net.au>,
Michael Turquette <mturquette@baylibre.com>,
linux-clk <linux-clk@vger.kernel.org>
Subject: Re: [PATCH v2] clk: shmobile: r8a7795: Add SDHI clocks
Date: Fri, 22 Jan 2016 13:30:37 +0100 [thread overview]
Message-ID: <56A220ED.9090208@de.bosch.com> (raw)
In-Reply-To: <CAMuHMdU+8QCje=C98neja31yjMR4H6Bz-_hN0ihk3WC=JXdVuQ@mail.gmail.com>
On 20.01.2016 09:16, Geert Uytterhoeven wrote:
> Hi Dirk,
>
> On Sun, Jan 17, 2016 at 10:47 AM, Dirk Behme <dirk.behme@gmail.com> wrote:
>> On 15.01.2016 11:20, Geert Uytterhoeven wrote:
>>> On Fri, Jan 15, 2016 at 11:11 AM, Dirk Behme <dirk.behme@de.bosch.com>
>>> wrote:
>>>> On 14.01.2016 19:24, Geert Uytterhoeven wrote:
>>>>> 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.
>>>>>>> Signed-off-by: Dirk Behme <dirk.behme@gmail.com>
>>>>>>> ---
>>>>>>> Changes in v2: Add the missing *H clocks and correct the dividers.
>
>>>>> 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.
>>>>
>>>> Anything like
>>>>
>>>> https://git.kernel.org/cgit/linux/kernel/git/horms/renesas-bsp.git/commit/drivers/clk/shmobile/clk-rcar-gen3.c?h=v4.2/rcar-3.0.x&id=cd10385afc15cef6bfbaea4aa5da41193b24fe82
>>
>> I've had a look to that.
>>
>> I think we can pick all the functions
>>
>> +static const struct clk_ops cpg_sd_clock_ops = {
>> + .enable = cpg_sd_clock_enable,
>> + .disable = cpg_sd_clock_disable,
>> + .is_enabled = cpg_sd_clock_is_enabled,
>> + .recalc_rate = cpg_sd_clock_recalc_rate,
>> + .round_rate = cpg_sd_clock_round_rate,
>> + .set_rate = cpg_sd_clock_set_rate,
>> +};
>>
>> unchanged from that patch.
>>
>> However, I'm not sure how to interface this to cpg_mssr_probe()? It's
>> similar to cpg_mssr_register_mod_clk(), but not identical so that this could
>> be reused.
>>
>> We could extend r8a7795_cpg_mssr_info by anything like an additional
>>
>> /* Dynamic clocks */
>> .dyn_clks = /* Add an array allowing to pass various clk_ops structs */
>> ...
>>
>> ?
>>
>> Or we could hard code it like
>>
>> https://git.kernel.org/cgit/linux/kernel/git/horms/renesas-bsp.git/commit/drivers/clk/shmobile/clk-rcar-gen3.c?h=v4.2/rcar-3.0.x&id=cd10385afc15cef6bfbaea4aa5da41193b24fe82
>>
>> is doing it with
>>
>> + } else if (!strcmp(name, "sd0")) {
>> + return cpg_sd_clk_register(name, cpg->reg + CPG_SD0CKCR,
>> np);
>> + } else if (!strcmp(name, "sd1")) {
>> + return cpg_sd_clk_register(name, cpg->reg + CPG_SD1CKCR,
>> np);
>> + } else if (!strcmp(name, "sd2")) {
>> + return cpg_sd_clk_register(name, cpg->reg + CPG_SD2CKCR,
>> np);
>> + } else if (!strcmp(name, "sd3")) {
>> + return cpg_sd_clk_register(name, cpg->reg + CPG_SD3CKCR,
>> np);
>>
>> and add this to e.g. r8a7795_cpg_clk_register(). But, hmm.
>>
>>
>> What do you think? Opinions? Examples?
>
> Please extend enum r8a7795_clk_types, and handle them in
> r8a7795_cpg_clk_register() based on the enum values.
>
> You can find an (old) example in the prototype I did for r8a7791:
> https://git.kernel.org/cgit/linux/kernel/git/geert/renesas-drivers.git/tree/drivers/clk/shmobile/clk-r8a7791-cpg-mssr.c?h=topic/cpg-mssr-v4
Whats about anything like
http://marc.info/?l=linux-sh&m=145346559429931
?
Best regards
Dirk
WARNING: multiple messages have this Message-ID (diff)
From: Dirk Behme <dirk.behme@de.bosch.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>,
Wolfram Sang <wsa@the-dreams.de>
Cc: Dirk Behme <dirk.behme@gmail.com>,
Linux-sh list <linux-sh@vger.kernel.org>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Simon Horman <horms+renesas@verge.net.au>,
Michael Turquette <mturquette@baylibre.com>,
linux-clk <linux-clk@vger.kernel.org>
Subject: Re: [PATCH v2] clk: shmobile: r8a7795: Add SDHI clocks
Date: Fri, 22 Jan 2016 12:30:37 +0000 [thread overview]
Message-ID: <56A220ED.9090208@de.bosch.com> (raw)
In-Reply-To: <CAMuHMdU+8QCje=C98neja31yjMR4H6Bz-_hN0ihk3WC=JXdVuQ@mail.gmail.com>
On 20.01.2016 09:16, Geert Uytterhoeven wrote:
> Hi Dirk,
>
> On Sun, Jan 17, 2016 at 10:47 AM, Dirk Behme <dirk.behme@gmail.com> wrote:
>> On 15.01.2016 11:20, Geert Uytterhoeven wrote:
>>> On Fri, Jan 15, 2016 at 11:11 AM, Dirk Behme <dirk.behme@de.bosch.com>
>>> wrote:
>>>> On 14.01.2016 19:24, Geert Uytterhoeven wrote:
>>>>> 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.
>>>>>>> Signed-off-by: Dirk Behme <dirk.behme@gmail.com>
>>>>>>> ---
>>>>>>> Changes in v2: Add the missing *H clocks and correct the dividers.
>
>>>>> 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.
>>>>
>>>> Anything like
>>>>
>>>> https://git.kernel.org/cgit/linux/kernel/git/horms/renesas-bsp.git/commit/drivers/clk/shmobile/clk-rcar-gen3.c?h=v4.2/rcar-3.0.x&idÍ10385afc15cef6bfbaea4aa5da41193b24fe82
>>
>> I've had a look to that.
>>
>> I think we can pick all the functions
>>
>> +static const struct clk_ops cpg_sd_clock_ops = {
>> + .enable = cpg_sd_clock_enable,
>> + .disable = cpg_sd_clock_disable,
>> + .is_enabled = cpg_sd_clock_is_enabled,
>> + .recalc_rate = cpg_sd_clock_recalc_rate,
>> + .round_rate = cpg_sd_clock_round_rate,
>> + .set_rate = cpg_sd_clock_set_rate,
>> +};
>>
>> unchanged from that patch.
>>
>> However, I'm not sure how to interface this to cpg_mssr_probe()? It's
>> similar to cpg_mssr_register_mod_clk(), but not identical so that this could
>> be reused.
>>
>> We could extend r8a7795_cpg_mssr_info by anything like an additional
>>
>> /* Dynamic clocks */
>> .dyn_clks = /* Add an array allowing to pass various clk_ops structs */
>> ...
>>
>> ?
>>
>> Or we could hard code it like
>>
>> https://git.kernel.org/cgit/linux/kernel/git/horms/renesas-bsp.git/commit/drivers/clk/shmobile/clk-rcar-gen3.c?h=v4.2/rcar-3.0.x&idÍ10385afc15cef6bfbaea4aa5da41193b24fe82
>>
>> is doing it with
>>
>> + } else if (!strcmp(name, "sd0")) {
>> + return cpg_sd_clk_register(name, cpg->reg + CPG_SD0CKCR,
>> np);
>> + } else if (!strcmp(name, "sd1")) {
>> + return cpg_sd_clk_register(name, cpg->reg + CPG_SD1CKCR,
>> np);
>> + } else if (!strcmp(name, "sd2")) {
>> + return cpg_sd_clk_register(name, cpg->reg + CPG_SD2CKCR,
>> np);
>> + } else if (!strcmp(name, "sd3")) {
>> + return cpg_sd_clk_register(name, cpg->reg + CPG_SD3CKCR,
>> np);
>>
>> and add this to e.g. r8a7795_cpg_clk_register(). But, hmm.
>>
>>
>> What do you think? Opinions? Examples?
>
> Please extend enum r8a7795_clk_types, and handle them in
> r8a7795_cpg_clk_register() based on the enum values.
>
> You can find an (old) example in the prototype I did for r8a7791:
> https://git.kernel.org/cgit/linux/kernel/git/geert/renesas-drivers.git/tree/drivers/clk/shmobile/clk-r8a7791-cpg-mssr.c?h=topic/cpg-mssr-v4
Whats about anything like
http://marc.info/?l=linux-sh&m\x145346559429931
?
Best regards
Dirk
next prev parent reply other threads:[~2016-01-22 12:30 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 [this message]
2016-01-22 12:30 ` Dirk Behme
2016-01-14 18:45 ` Michael Turquette
2016-01-14 19:02 ` Dirk Behme
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=56A220ED.9090208@de.bosch.com \
--to=dirk.behme@de.bosch.com \
--cc=dirk.behme@gmail.com \
--cc=geert+renesas@glider.be \
--cc=geert@linux-m68k.org \
--cc=horms+renesas@verge.net.au \
--cc=linux-clk@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=wsa@the-dreams.de \
/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.