> -----Original Message----- > From: linux-omap-owner@xxxxxxxxxxxxxxx [mailto:linux-omap- > owner@xxxxxxxxxxxxxxx] On Behalf Of Tero.Kristo@xxxxxxxxx > Sent: Wednesday, January 19, 2011 1:52 PM > To: vishwanath.bs@xxxxxx; linux-omap@xxxxxxxxxxxxxxx > Cc: paul@xxxxxxxxx; khilman@xxxxxxxxxxxxxxxxxxx > Subject: RE: [PATCH] OMAP3: CPUIdle: prevent CORE from going off if > doing so would reset an active clockdomain > > > > >-----Original Message----- > >From: linux-omap-owner@xxxxxxxxxxxxxxx [mailto:linux-omap- > >owner@xxxxxxxxxxxxxxx] On Behalf Of ext Vishwanath Sripathy > >Sent: 19 January, 2011 06:39 > >To: Kristo Tero (Nokia-MS/Tampere); linux-omap@xxxxxxxxxxxxxxx > >Cc: Paul Walmsley; Kevin Hilman > >Subject: RE: [PATCH] OMAP3: CPUIdle: prevent CORE from going off if > >doing so would reset an active clockdomain > > > >Tero, > > > >> -----Original Message----- > >> From: linux-omap-owner@xxxxxxxxxxxxxxx [mailto:linux-omap- > >> owner@xxxxxxxxxxxxxxx] On Behalf Of Tero Kristo > >> Sent: Tuesday, January 18, 2011 3:18 PM > >> To: linux-omap@xxxxxxxxxxxxxxx > >> Cc: Paul Walmsley; Kevin Hilman > >> Subject: [PATCH] OMAP3: CPUIdle: prevent CORE from going off if > doing > >> so would reset an active clockdomain > >> > >> On OMAP3 SoCs, if the CORE powerdomain enters off-mode, many > other > >> parts of the chip will be reset. If those parts of the chip are > busy, > >> the reset will disrupt them, causing unpredictable and generally > >> undesirable results. > >If some parts of the chip are busy, then how can Core domain enter > off > >state? The necessary condition for Core to enter low power state is > that > >all the clock domains (including DSS, CAM, IVA, USB, PER etc) > should > >have > >idled. Doesn't it mean that all the modules have idled and asserted > >idleack when Core is entering off state? > > This can happen e.g. when some powerdomain has entered RET state. We > have faced this issue at least with IVA2 because it has its own > power management. > IVA2 PD managed directly instead of linux side PM frameworks is one problem. If the IVA2 hits retention, and if there is no dependency on core PD, it should be still fine for core to enter OFF. I hope it's not the case where some modules from CORE PD are used by IVA side software ( may be SDMA, GPIO etc) and as part of CORE OFF you loose context of these which leads to the issue. Regards, Santosh -- 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
