Re: [RFC] OMAP3: CPUIDLE & PM: Modifications and fixes

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



"ext Paul Walmsley" <paul@xxxxxxxxxxx> writes:

> Hello Jouni,
>
> a couple of questions about these patches....
>
> On Tue, 8 Jul 2008, Jouni Hogander wrote:
>
>> With this patch cpuidle boot problem with cpuidle doesn't exist. Also hang on wake-up seems to
>> disappear (haven't seen this far).
>> 
>> Main points in this patch are:
>> 1. Add wkdep between neon and mpu
>> 2. Add wkdep between per and core
>
> Could you explain a little further why PER would have a wakeup dependency 
> on CORE?  Is this something that we should only enable under certain 
> conditions, e.g., latency requirements for a device in PER?

This is done to make sure we don't loose any gpio interrupts: GPIO
wakeup/interrupt doesn't work for GPIOs in PER domain if PER is not
active.

>
>> 3. Deny hwsup mode before writing next pwrst state
>
> I missed this part of the patch - could you point me at that
> section?

Patch changes code to use set_pwrdm_state from pm34xx.c instead of
pwrdm_set_next_pwrst from powerdomain code. That function contains
denying hwsup mode.

>
>
> regards,
>
> - Paul
> --
> 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
>
>

-- 
Jouni Högander

--
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

[Index of Archives]     [Linux Arm (vger)]     [ARM Kernel]     [ARM MSM]     [Linux Tegra]     [Linux WPAN Networking]     [Linux Wireless Networking]     [Maemo Users]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux