Isn't this patch meant to be pushed after "Update powerdomains and clockdomains" series from Paul?
I don't see that yet. Regards, Sergio -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Tony Lindgren Sent: Wednesday, September 10, 2008 6:48 PM To: Paul Walmsley Cc: [email protected] Subject: Re: [PATCH] OMAP3 clock: remove extra init from csi2_96m_fck * Paul Walmsley <[EMAIL PROTECTED]> [080909 09:59]: > > csi2_96m_fck no longer should attempt to init its clockdomain pointer; the > clock framework now does this by default. Applies on top of the "Update > powerdomains and clockdomains" series sent earlier. > > Verified on 3430SDP ES2. Pushing today. Tony > > Signed-off-by: Paul Walmsley <[EMAIL PROTECTED]> > --- > arch/arm/mach-omap2/clock34xx.h | 1 - > 1 files changed, 0 insertions(+), 1 deletions(-) > > diff --git a/arch/arm/mach-omap2/clock34xx.h b/arch/arm/mach-omap2/clock34xx.h > index 65568c3..56ae83f 100644 > --- a/arch/arm/mach-omap2/clock34xx.h > +++ b/arch/arm/mach-omap2/clock34xx.h > @@ -2298,7 +2298,6 @@ static struct clk cam_ick = { > static struct clk csi2_96m_fck = { > .name = "csi2_96m_fck", > .parent = &core_96m_fck, > - .init = &omap2_init_clk_clkdm, > .enable_reg = _OMAP34XX_CM_REGADDR(OMAP3430_CAM_MOD, CM_FCLKEN), > .enable_bit = OMAP3430_EN_CSI2_SHIFT, > .flags = CLOCK_IN_OMAP343X, > -- > To unsubscribe from this list: send the line "unsubscribe linux-omap" in > the body of a message to [EMAIL PROTECTED] > 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 [EMAIL PROTECTED] 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 [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
