Santosh Shilimkar <santosh.shilimkar@xxxxxx> writes: >> -----Original Message----- >> From: Nishanth Menon [mailto:nm@xxxxxx] >> Sent: Friday, November 19, 2010 10:55 PM >> To: Santosh Shilimkar >> Cc: Kevin Hilman; linux-omap; Jean Pihet; Vishwanath Sripathy; Tony >> Subject: Re: [PATCH 08/13] OMAP3: PM: Deny MPU idle while saving secure >> RAM >> >> Santosh Shilimkar had written, on 11/19/2010 11:18 AM, the following: >> [..] >> >> I guess we need some more details on which secure mode calls can >> trigger >> >> this problem. If this is an isolated case, I'm OK with this fix. If >> >> it's more general, I'd like to see a more general fix. >> >> >> > On the related topic I posted a patch some time back. >> > http://www.spinics.net/lists/linux-omap/msg37907.html >> > I guess Kevin is referring to the above patch. Yes. >> I believe the fix we are attempting here is for a specific scenario >> which IMHO is different from the issue solved in the link above. > > It will also solve the above issue indirectly. Yes, it indirectly fixes the issue solved by $SUBJECT patch, but what else does it fix? This secure mode call is currently the only one I'm aware of that does a WFI. If there are others, then $SUBJECT patch is not enough. If TI cannot tell us definitively if other secure-mode calls may use WFI, then we have to assume there are others, and $SUBJECT patch has to be NAK'd in favor of a more generic fix like the one from Santosh. Kevin -- 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
