devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Michael Turquette <mturquette@baylibre.com>,
	Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
	Simon <horms@verge.net.au>, Magnus <magnus.damm@gmail.com>,
	Linux-sh list <linux-sh@vger.kernel.org>,
	linux-clk@vger.kernel.org,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [PATCH 3/4 v3][RFC] arm64: renesas: Add initial r8a7795 SoC support
Date: Thu, 20 Aug 2015 09:43:34 +0200	[thread overview]
Message-ID: <CAMuHMdWMNLf-fDsiLNFwO05i0cqBHkdM2mwC3GinwWFN4pWFZg@mail.gmail.com> (raw)
In-Reply-To: <12310001.Bt8qbPIiMv@avalon>

Hi Laurent,

On Wed, Aug 19, 2015 at 11:29 PM, Laurent Pinchart
<laurent.pinchart@ideasonboard.com> wrote:
>> > Also, while you're thinking about the perfect clock binding, please do
>> > consider dropping clock-output-names if you can. Specifying clock-names
>> > alongside the clocks property inside of the consumer node is a bit more
>> > elegant in my opinion. This is also a bit easier if you think about
>> > expressing your clock data with C inside of your provider driver.
>>
>> Makes sense. I don't think anything relies on the "clock-output-names"
>> ... currently.
>>
>> I was going to use it for identifying the GIC clock, though:
>>
>> --- a/drivers/clk/shmobile/clk-mstp.c
>> +++ b/drivers/clk/shmobile/clk-mstp.c
>> @@ -144,6 +144,9 @@ cpg_mstp_clock_register(const char *name, const char
>> *paren init.name = name;
>>         init.ops = &cpg_mstp_clock_ops;
>>         init.flags = CLK_IS_BASIC | CLK_SET_RATE_PARENT;
>> +       /* INTC-SYS is the module clock of the GIC, and must not be disabled
>> */
>> +       if (!strcmp(name, "intc-sys"))
>> +               init.flags |= CLK_ENABLE_HAND_OFF;
>>         init.parent_names = &parent_name;
>>         init.num_parents = 1;
>>
>> (FTR, on R-Car Gen3 the clock is called "intc-ap", not "intc-sys", doh...).
>>
>> This does put some reliance on (undocumented) naming in DT, though, so not
>> having the "clock-output-names" would solve that.
>
> Using the clock name is indeed very messy, let's avoid that.
>
>> However, while "intc-sys"/"intc-ap" (if existent) is always MSTP408, MSTP408
>> is used for other modules on R-Car Gen1 and most older SoCs. so it would
>> complicate the driver code.
>
> How about setting the flag based on information provided in DT ?

Like scanning DT for the GIC, and looking for its clock?

I don't want to add an explicit flag in DT, as it's not a hardware property,
but a deficiency of the current GIC driver/subsystem.

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

  reply	other threads:[~2015-08-20  7:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <877fpdw3av.wl%kuninori.morimoto.gx@renesas.com>
     [not found] ` <873801w377.wl%kuninori.morimoto.gx@renesas.com>
     [not found]   ` <1559394.i3FG4v33fI@avalon>
2015-08-04 12:34     ` [PATCH 3/4 v3][RFC] arm64: renesas: Add initial r8a7795 SoC support Geert Uytterhoeven
2015-08-18  0:20       ` Michael Turquette
2015-08-19  7:49         ` Geert Uytterhoeven
2015-08-19 21:29           ` Laurent Pinchart
2015-08-20  7:43             ` Geert Uytterhoeven [this message]
2015-08-20 19:48               ` Laurent Pinchart
2015-08-24  7:51                 ` Geert Uytterhoeven
2015-08-28  8:44           ` 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=CAMuHMdWMNLf-fDsiLNFwO05i0cqBHkdM2mwC3GinwWFN4pWFZg@mail.gmail.com \
    --to=geert@linux-m68k.org \
    --cc=devicetree@vger.kernel.org \
    --cc=horms@verge.net.au \
    --cc=kuninori.morimoto.gx@renesas.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    --cc=mturquette@baylibre.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 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).