All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Cousson, Benoit" <b-cousson@ti.com>
To: Paul Walmsley <paul@pwsan.com>
Cc: "Gopinath, Thara" <thara@ti.com>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	"khilman@deeprootsystems.com" <khilman@deeprootsystems.com>
Subject: Re: [PATCH] OMAP4: Extend clock data.
Date: Thu, 30 Sep 2010 11:21:11 +0200	[thread overview]
Message-ID: <4CA45687.1010205@ti.com> (raw)
In-Reply-To: <4CA4555D.2040106@ti.com>

On 9/30/2010 11:16 AM, Cousson, Benoit wrote:
> Hi Thara,
>
> On 9/30/2010 10:57 AM, Paul Walmsley wrote:
>> Hello Thara,
>>
>> On Thu, 30 Sep 2010, Thara Gopinath wrote:
>>
>>> This patch extends the OMAP4 clock data to include
>>> various x2 clock nodes as the clock framework
>>> skips a *2 whie calculating the dpll locked frequency.
>>>
>>> Signed-off-by: Thara Gopinath<thara@ti.com>
>>> Acked-by: Kevin Hilman<khilman@deeprootsystems.com>
>>> ---
>>> Currently the framework is extended to include x2 nodes
>>> only for a few clocks critical for OMAP4 DVFS. This
>>> exercise needs to be done for most of the other post divider
>>> clocks as and when necessary.
>>
>> Benoît and I have been discussing this - I think we should probably fix
>> this problem for all of the DPLLs and HSDIVIDERs in one patch.  I'll let
>> Benoît comment further, but I think the current plan will be to generate a
>> CLKOUTX2 node after the DPLLs, and then to use that as the parent for
>> the various HSDIVIDERs that use that X2 output.
>
> Here is

That's a nice cliffhanger, isn't it? You'll have the remaining part in
a next episode...

Benoit

>> Also, I think we should make this change in a consistent way with regards
>> to what the autogeneration scripts should generate.  This way, we won't
>> have to redo it later and cause unnecessary patch noise.
>>
>> Perhaps you can help Benoît update the autogeneration scripts for the
>> above changes?
>>
>>
>> - Paul
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2010-09-30  9:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-30  8:00 [PATCH] OMAP4: Extend clock data Thara Gopinath
2010-09-30  8:57 ` Paul Walmsley
2010-09-30  9:16   ` Cousson, Benoit
2010-09-30  9:21     ` Cousson, Benoit [this message]
2010-09-30  9:31   ` Cousson, Benoit

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=4CA45687.1010205@ti.com \
    --to=b-cousson@ti.com \
    --cc=khilman@deeprootsystems.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=paul@pwsan.com \
    --cc=thara@ti.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 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.