public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: laurent.pinchart@ideasonboard.com (Laurent Pinchart)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/7] Renesas R8A7790 Common Clock Framework support
Date: Thu, 14 Nov 2013 16:23:05 +0100	[thread overview]
Message-ID: <9051092.bb2GyTMq0G@avalon> (raw)
In-Reply-To: <CANqRtoRfBb_mZ3erk_iSmmjuFJAWetN3THjGQcBhEjVE__2wWg@mail.gmail.com>

Hi Magnus,

On Thursday 14 November 2013 19:16:05 Magnus Damm wrote:
> Hi Laurent,
> 
> Thanks for V2, it is looking better and better. Great that r8a7791 and
> r8a7790 can share the CPG code. I have now finally got my r8a7791 board
> replaced so I intend to try your code out on Lager and then see if I can
> cook something up on Koelsch.

I was actually planning to test the code on the Koelsch board. I don't want to 
step on anyone's toes, so please let me know if someone is already working on 
CCF patches for M2, otherwise I'll send them.

> I have one question related to the CPG. What is your plan regarding CPU
> Frequency scaling? I'd like to see "z_clk" and "z2_clk" implemented together
> with some way to let CPUFreq scale "z_clk". Can you please spend some time
> on that?

Z2 is a fixed factor clock, I'll just add it to DT.

Z is a bit more tricky. It's the output of a pure multiplier (PLL0) followed 
by a pure divisor (SYS-CPU divider 1). I can easily model the two as separate 
clock devices, but I'm unsure about what should be done at runtime when 
setting the Z clock frequency. Would it be enough to have a fixed PLL0 
frequency and configure the SYS-CPU divider 1 only (from 1/1 to 1/32), or 
would we need to configure the PLL0 multiplier as well for a more fine-grained 
Z frequency configuration ?

-- 
Regards,

Laurent Pinchart

      reply	other threads:[~2013-11-14 15:23 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-10  3:09 [PATCH v2 0/7] Renesas R8A7790 Common Clock Framework support Laurent Pinchart
2013-11-10  3:09 ` [PATCH v2 1/7] clk: shmobile: Add R-Car Gen2 clocks support Laurent Pinchart
2013-11-10  3:09 ` [PATCH v2 2/7] clk: shmobile: Add DIV6 clock support Laurent Pinchart
2013-11-10  3:09 ` [PATCH v2 3/7] clk: shmobile: Add MSTP " Laurent Pinchart
2013-11-10  3:09 ` [PATCH v2 4/7] ARM: shmobile: r8a7790: Add clock index macros for DT sources Laurent Pinchart
2013-11-10  3:09 ` [PATCH v2 5/7] ARM: shmobile: r8a7791: " Laurent Pinchart
2013-11-10  3:09 ` [PATCH v2 6/7] ARM: shmobile: r8a7790: Add clocks Laurent Pinchart
2013-11-10  3:09 ` [PATCH v2 7/7] ARM: shmobile: r8a7790: Reference clocks Laurent Pinchart
2013-11-14 10:16 ` [PATCH v2 0/7] Renesas R8A7790 Common Clock Framework support Magnus Damm
2013-11-14 15:23   ` 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=9051092.bb2GyTMq0G@avalon \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=linux-arm-kernel@lists.infradead.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