On Sat, Jul 07, 2012 at 02:41:31PM +0200, Ladislav Michl wrote:
> On Mon, Jul 02, 2012 at 10:41:38AM -0700, Mark A. Greer wrote:
> > On Mon, Jul 02, 2012 at 05:54:57AM +0000, Kim, Milo wrote:
> > > In am35x board , iva2 clock domain doesn't be used.
> > > So mpu_am35x_clkdm should be used rather than mpu_3xxx_clkdm.
> > > OMAP3430 : mpu_3xxx_clkdm (with iva2 clkdm)
> > > AM35x : mpu_am35x_clkdm (without iva2 clkdm)
> > > diff --git a/arch/arm/mach-omap2/clockdomains3xxx_data.c b/arch/arm/mach-omap2/clockdomains3xxx_data.c
> > > index d625844..56089c4 100644
> > > --- a/arch/arm/mach-omap2/clockdomains3xxx_data.c
> > > +++ b/arch/arm/mach-omap2/clockdomains3xxx_data.c
> > > @@ -454,7 +454,6 @@ static struct clkdm_autodep clkdm_am35x_autodeps[] = {
> > >
> > > static struct clockdomain *clockdomains_common[] __initdata = {
> > > &wkup_common_clkdm,
> > > - &mpu_3xxx_clkdm,
> > > &neon_clkdm,
> > > &core_l3_3xxx_clkdm,
> > > &core_l4_3xxx_clkdm,
> > > --
> > > 1.7.2.5
> >
> > Hi Milo.
> >
> > Thanks for the patch but this issue should already be fixed in a patch
> > that Tony just made a pull request for
> > (http://www.spinics.net/lists/linux-omap/msg73080.html).
> >
> > >From that email (and branch in the email), look for this patch:
> >
> > > Mark A. Greer (4):
> >
> > > ARM: OMAP AM35x: clockdomain data: Fix clockdomain dependencies
> >
> > Please take a look as another set of eyes never hurts. :)
>
> Hi Mark,
>
> just tested above patch on Technexion's TAM-3517 and it indeed fixes above
> warning. Without patch, warning is generated. Tested on Tony's master branch.
Great, thanks for the follow up, Ladis.
Mark
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
