On Wed, Nov 12, 2008 at 11:07 AM, Paul Walmsley <paul@xxxxxxxxx> wrote:
> Hi Jouni, Kevin,
>
> On Tue, 11 Nov 2008, Högander Jouni wrote:
>
>> I wouldn't add any flags for this. The goal is finally to set all
>> next_states as OFF until someone has set some constraint which
>> prevents OFF usage. For now we need to use RET as default, because
>> drivers are not supporting OFF mode. Do you agree this?
>
> Yes.
>
>> Easiest way here would be to add own hook for SGX in pwrdms_setup? One
>> more strcmp("*_pwrdm, pwrdm->name) :)
>>
>> What do you think?
>
> That is okay with me. This seems to be an unusual case - I guess it's due
> to an SGX firmware bug.
>
> So Kevin, if you have a strong opposition to that strcmp, maybe we should
> use a powerdomain flag for the SGX pwrdm. Otherwise, let's go with a
> strcmp as Jouni suggested. Thoughts?
Has there been a final resolution on this?
I am unable to boot reliably on Overo with 2.6.28-rc5 -- almost every
boot attempt gives me:
Power Management for TI OMAP3.
Unable to set state of powerdomain: sgx_pwrdm
Failed to setup powerdomains
omap2|3_pm_init failed: -22
Steve
--
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
