SUPERH platform development
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH v8 04/07] arm64: renesas: r8a7795 dtsi: Add all SCIF nodes
Date: Mon, 07 Sep 2015 19:43:11 +0000	[thread overview]
Message-ID: <7329282.OeGUVITr0v@avalon> (raw)
In-Reply-To: <20150831062952.24004.17072.sendpatchset@little-apple>

Hi Geert,

On Thursday 03 September 2015 21:03:10 Geert Uytterhoeven wrote:
> On Thu, Sep 3, 2015 at 1:48 PM, Laurent Pinchart wrote:
> > On Thursday 03 September 2015 09:54:17 Geert Uytterhoeven wrote:
> >> On Thu, Sep 3, 2015 at 9:41 AM, Magnus Damm wrote:
> >>> On Mon, Aug 31, 2015 at 10:08 PM, Geert Uytterhoeven wrote:
> >>>> On Mon, Aug 31, 2015 at 2:59 PM, Magnus Damm wrote:
> >
> > [snip]
> > 
> >>>>> But if we're going down that route then may I ask why we have
> >>>>> "-clocks" suffix for the MSTP/CPG compat strings? I'd rather make
> >>>>> them shorter and more similar to the rest of the compat strings on
> >>>>> the SoC.
> >>>> 
> >>>> It uses plural because CPG and MSTP nodes provide more than one clock.
> >>>> 
> >>>> Cfr. DIV6, which provides a single clock, and uses e.g.
> >>>> "renesas,r8a7791-div6-clock", "renesas,cpg-div6-clock" (singular).
> >>> 
> >>> Ok, thanks but my concern was not about singular vs plural.
> >>> Why do we need the "-clocks" suffix?
> >>> 
> >>> It's a detail, but for me the shorter "renesas,r8a7795-mstp" makes
> >>> more sense than "renesas,r8a7795-mstp-clocks"
> >> 
> >> The MSTP blocks are subsets of the CPG block, and their registers are
> >> heavily entangled with other registers inside the CPG and other MSTP
> >> blocks. So currently the MSTP nodes don't represent the MSTP blocks, but
> >> their clocks only (and not e.g. reset control).
> >> 
> >> I'm afraid the only sane way to express their full functionality is to
> >> have a single cpg_mstp node...
> > 
> > That might be a good idea. We could just use two clock cells and hide all
> > the dirty details in C code. Anyone wants to give it a try ? :-)
> 
> I think we have to keep at least the references to the parent clocks of the
> MSTP clocks in DT, as many of them are instantiated from DT (fixed-factor,
> div6, ...) instead of the renesas,<soc>-cpg-clocks C code.

We could use clock-indices for that, although it might quickly become ugly. 
And it would require removing the hardcoded assumption in the CCF core that 
the number of clock cells is 1 at most.

-- 
Regards,

Laurent Pinchart


      parent reply	other threads:[~2015-09-07 19:43 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-31  6:29 [PATCH v8 04/07] arm64: renesas: r8a7795 dtsi: Add all SCIF nodes Magnus Damm
2015-08-31 10:40 ` Laurent Pinchart
2015-08-31 12:47 ` Geert Uytterhoeven
2015-08-31 12:59 ` Magnus Damm
2015-08-31 13:08 ` Geert Uytterhoeven
2015-09-03  7:41 ` Magnus Damm
2015-09-03  7:54 ` Geert Uytterhoeven
2015-09-03  8:06 ` Magnus Damm
2015-09-03  8:23 ` Geert Uytterhoeven
2015-09-03  8:28 ` Magnus Damm
2015-09-03 11:48 ` Laurent Pinchart
2015-09-03 19:03 ` Geert Uytterhoeven
2015-09-07 19:43 ` Laurent Pinchart [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=7329282.OeGUVITr0v@avalon \
    --to=laurent.pinchart@ideasonboard.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox