Hi Paul, > -----Original Message----- > From: Paul Walmsley [mailto:paul@xxxxxxxxx] > Sent: Tuesday, February 12, 2013 12:09 PM > To: J, KEERTHY > Cc: linux-omap@xxxxxxxxxxxxxxx; linux-arm-kernel@xxxxxxxxxxxxxxxxxxx > Subject: RE: [PATCH] ARM: OMAP: Clock: Remove CK_* flags > > On Tue, 12 Feb 2013, J, KEERTHY wrote: > > > > -----Original Message----- > > > From: Paul Walmsley [mailto:paul@xxxxxxxxx] > > > Sent: Monday, February 11, 2013 9:10 PM > > > To: J, KEERTHY > > > Cc: linux-omap@xxxxxxxxxxxxxxx; linux-arm- > kernel@xxxxxxxxxxxxxxxxxxx > > > Subject: RE: [PATCH] ARM: OMAP: Clock: Remove CK_* flags > > > > > > On Mon, 11 Feb 2013, J, KEERTHY wrote: > > > > > > > Can I pull the other patches and rebase this patch on top of > them? > > > > I need the branch where I can pull the other clock related > patches. > > > > I will rebase this patch on top, Verify the PM suspend on > OMAP4460 > > > > And post it. > > > > > > It's based on Tony's omap-for-v3.9/pm branch. > > > > > > > I am on the above branch. I am not seeing retention with/without the > patch. > > Sounds like you get to do some bisecting :-) > Heh :-). It narrowed down to this patch: commit 17b7e7d33530e2bbd3bdc90f4db09b91cfdde2bb Author: Paul Walmsley <paul@xxxxxxxxx> Date: Sat Jan 26 00:48:54 2013 -0700 ARM: OMAP4: clock/hwmod data: start to remove some IP block control "clocks" Remove some leaf "clocks" that are actually IP block idle control points, since these should now be handled by the hwmod code. There are still a few types of MODULEMODE clocks that need to be cleaned up: - those still in use by driver or integration code - those in DEFINE_CLK_OMAP_MUX_GATE() blocks; the gate portion of these should be removed A similar process may also be possible on OMAP2/3. Signed-off-by: Paul Walmsley <paul@xxxxxxxxx> Cc: Benoît Cousson <b-cousson@xxxxxx> Cc: Mike Turquette <mturquette@xxxxxxxxxx> > > - Paul Regards, Keerthy -- 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
