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
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
Thanks Benoit for the explanation. It seems you are right.
+ Wenbiao who is the original patch author that may have another point
of view and some additional explanations.
--
Best regards,
Ruslan Bilovol
On Mon, Jul 2, 2012 at 3:43 PM, Benoit Cousson b-cous...@ti.com wrote:
On 06/29/2012
On 06/29/2012 10:35 PM, Paul Walmsley wrote:
+ Benoît who is the maintainer of this file
+ the linux-arm-kernel mailing list, which should be cc'ed on all OMAP
patches
On Fri, 29 Jun 2012, Ruslan Bilovol wrote:
From: Wenbiao Wang ww...@ti.com
OTG clock usb_otg_hs_ick used a incorrect parent
From: Wenbiao Wang ww...@ti.com
OTG clock usb_otg_hs_ick used a incorrect parent l3_div_ck.
Correct it to use the right colck otg_60m_gfclk as its
parent.
Signed-off-by: Wenbiao Wang ww...@ti.com
Signed-off-by: Ruslan Bilovol ruslan.bilo...@ti.com
---
arch/arm/mach-omap2/clock44xx_data.c | 15
+ Benoît who is the maintainer of this file
+ the linux-arm-kernel mailing list, which should be cc'ed on all OMAP
patches
On Fri, 29 Jun 2012, Ruslan Bilovol wrote:
From: Wenbiao Wang ww...@ti.com
OTG clock usb_otg_hs_ick used a incorrect parent l3_div_ck.
Correct it to use the right
