From: Benoit Cousson <b-cousson@ti.com>
To: Paul Walmsley <paul@pwsan.com>
Cc: Ruslan Bilovol <ruslan.bilovol@ti.com>,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
tony@atomide.com
Subject: Re: [PATCH] OMAP4: Clock: Correct OTG clock to use otg_60m_gfclk.
Date: Wed, 4 Jul 2012 15:09:32 +0200 [thread overview]
Message-ID: <4FF4408C.5070300@ti.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1207040307530.6760@utopia.booyaka.com>
Hi Paul,
On 07/04/2012 11:10 AM, Paul Walmsley wrote:
> On Mon, 2 Jul 2012, Benoit Cousson wrote:
>
>> Unfortunately the clock fmwk cannot handle module as a clock node.
>
> Hmm. We have to have similar support in the clockfw for the CLKDIV32K
> clock for AM33xx. That uses the modulemode bits to enable and disable the
> clock. Or does this require something more complicated?
I don't think so, in that case, that should probably be enough.
But playing with the modulemode in the clock frmwk still looks like a
hack to me.
Ideally it should be represented by a hwmod instead, but then it will
not fit in the clock fmwk.
That being said, using an IP (internal or not) as a source clock should
be supported.
That will allow us to handle the power dependency we have with Phoenix
audio that is the source clock of the McPDM.
Regards,
Benoit
WARNING: multiple messages have this Message-ID (diff)
From: b-cousson@ti.com (Benoit Cousson)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] OMAP4: Clock: Correct OTG clock to use otg_60m_gfclk.
Date: Wed, 4 Jul 2012 15:09:32 +0200 [thread overview]
Message-ID: <4FF4408C.5070300@ti.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1207040307530.6760@utopia.booyaka.com>
Hi Paul,
On 07/04/2012 11:10 AM, Paul Walmsley wrote:
> On Mon, 2 Jul 2012, Benoit Cousson wrote:
>
>> Unfortunately the clock fmwk cannot handle module as a clock node.
>
> Hmm. We have to have similar support in the clockfw for the CLKDIV32K
> clock for AM33xx. That uses the modulemode bits to enable and disable the
> clock. Or does this require something more complicated?
I don't think so, in that case, that should probably be enough.
But playing with the modulemode in the clock frmwk still looks like a
hack to me.
Ideally it should be represented by a hwmod instead, but then it will
not fit in the clock fmwk.
That being said, using an IP (internal or not) as a source clock should
be supported.
That will allow us to handle the power dependency we have with Phoenix
audio that is the source clock of the McPDM.
Regards,
Benoit
next prev parent reply other threads:[~2012-07-04 13:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-29 11:53 [PATCH] OMAP4: Clock: Correct OTG clock to use otg_60m_gfclk Ruslan Bilovol
2012-06-29 20:35 ` Paul Walmsley
2012-06-29 20:35 ` Paul Walmsley
2012-07-02 12:43 ` Benoit Cousson
2012-07-02 12:43 ` Benoit Cousson
2012-07-02 16:29 ` Ruslan Bilovol
2012-07-02 16:29 ` Ruslan Bilovol
2012-07-04 9:10 ` Paul Walmsley
2012-07-04 9:10 ` Paul Walmsley
2012-07-04 13:09 ` Benoit Cousson [this message]
2012-07-04 13:09 ` Benoit Cousson
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=4FF4408C.5070300@ti.com \
--to=b-cousson@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=paul@pwsan.com \
--cc=ruslan.bilovol@ti.com \
--cc=tony@atomide.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.