Re: [PATCH v2 3/6] omap3: pm: Update Triton2 scripts

[Nishanth Menon <nm@ti.com>]

Manuel, Lesly Arackal had written, on 01/21/2010 02:34 AM, the following:
> From: "Nishanth Menon" <nm@ti.com>
> To: "Manuel, Lesly Arackal" <x0080970@ti.com>
> Cc: <linux-omap@vger.kernel.org>; "Derrick, David" <dderrick@ti.com>; 
> 
> 
>> Manuel, Lesly Arackal had written, on 01/19/2010 11:35 AM, the following:
>>> From: Lesly A M <x0080970@ti.com>
>>>
>>> omap3: pm: Update Triton2 scripts
>>>
>>> Updated the sleep, wakeup & warm_reset sequence as recommended by David 
>>> Derrick.
>>> Used broadcast command, modified the resource type association and remap 
>>> sleep_state.
>>> Added the new script changes for zoom[2,3] boards.
>>>
>>> VDD1, VDD2 and VPLL1 are remapped to turn off during sleep state.
>>> Changed RES_TYPE2 of VPLL1, VDD1, VDD2, REGEN, NRESPWRON & SYSEN to '1'
>>> and VINTANA1, VINTANA2, VINTDIG, VIO, CLKEN & HFCLKOUT to '2'.
>> How about VMMC,VAUX and other resources?
>>
> These LDOs are controlled by drivers using regulator frame work, not through 
> TRITON power sequence.
Context of my question was - how do we handle devices such as eMMC which 
is required on bootup? I suppose the suspend/resume of those driver 
should ideally handle it..

but overall fair enough from me, if relevant comments are available in 
commit message.

[..]

-- 
Regards,
Nishanth Menon