>>-----Original Message----- >>From: Menon, Nishanth >>Sent: Tuesday, October 06, 2009 8:48 PM >>To: Kevin Hilman >>Cc: Gopinath, Thara; linux-omap@xxxxxxxxxxxxxxx; Gulati, Shweta >>Subject: Re: [PATCH] OMAP3: PM: Fix for Silicon bug on Context Restore on OMAP3430 >> >>Kevin Hilman had written, on 10/06/2009 10:05 AM, the following: >>> "Gopinath, Thara" <thara@xxxxxx> writes: >>> >>>> Will repost the patch with the defconfig option added. So that this can be disabled if not needed. >>> >>> ok, please update the changelog as well as describe the 300usec value >>> in terms of cycles. IOW, is 300usecs going to work at lower OPPs also? >>> >>Could I request for 2 options: >>a) workaround with no delay (manual save restore) - power savings for >>boards which dont use the pin >>b) workaround with 300uSec - for boards which use the pin ->functional How do we find out if the pin is functional or not? >> >>Also please have a check based on CPU revision and add errata number? I do not think this is yet published as an errata. >> >>-- >>Regards, >>Nishanth Menon -- 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
