On Wed, May 16, 2012 at 4:17 PM, Ming Lei <ming.lei@xxxxxxxxxxxxx> wrote:
> Jon,
>
> On Wed, May 16, 2012 at 6:05 AM, Ming Lei <ming.lei@xxxxxxxxxxxxx> wrote:
>>
>>
>> On Tuesday, May 15, 2012, Jon Hunter <jon-hunter@xxxxxx> wrote:
>>> Hi Ming,
>>>
>>> On 05/14/2012 11:53 PM, Ming Lei wrote:
>>>> On Thu, May 10, 2012 at 5:35 AM, Jon Hunter <jon-hunter@xxxxxx> wrote:
>>>>> From: Jon Hunter <jon-hunter@xxxxxx>
>>>>>
>>>>> This patch is based upon Ming Lei's patch to add runtime PM support for
>>>>> OMAP4
>>>>> [1]. In Ming's original patch the CTI interrupts were being enabled
>>>>> during
>>>>> runtime when the PMU was used but they were only configured once during
>>>>> init.
>>>>> Therefore move the configuration of the CTI interrupts to the runtime PM
>>>>> functions.
>>>>
>>>> As Shilimkar pointed out, you need to give the reason why the change
>>>> is introduced
>>>> in the patch.
>>>
>>> Yes will do. I have been waiting to get some feedback on HW_AUTO versus
>>> SW_SLEEP from design before posting a V2. I will enhance the changelog.
>>
>> Looks pandaboard will hang during kernel boot
>> with the latest next tree, so perf can't be tested now.
>> Once the problem is fixed, l will run perf test and provide my feedback.
>
> After bisecting, looks it is the 1st commit which triggers kernel
> boot hang:
>
> commit 5f3aa31f77733605f04a5a92ddc475ffd439585f
> Merge: 0f131ea ce4deaa
> Author: Stephen Rothwell <sfr@xxxxxxxxxxxxxxxx>
> Date: Mon May 14 18:55:39 2012 +1000
>
> Merge remote-tracking branch 'arm-soc/for-next'
The above kernel hang is caused by mmc driver probe failure,
which can be fixed by the patch in below link:
http://www.mail-archive.com/linux-omap@xxxxxxxxxxxxxxx/msg68848.html
After applying the patch, I can test the 6 patches and looks they work well
about perf support on omap4, also perf can work well after S2R.
Tested-by: Ming Lei <ming.lei@xxxxxxxxxxxxx>
Thanks,
--
Ming Lei
--
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
