On Thu, Jun 4, 2015 at 10:24 PM, Stefan Agner wrote:
> I actually tried to experiment with pinctrl_pm_select_default_state and
> pinctrl_pm_select_sleep_state. I think, one solution would be to create
> sleep states for all drivers. However, it's not necessary to change to a
> sleep state, since
On 2015-06-04 17:00, Zhi Li wrote:
> On Mon, Jun 1, 2015 at 10:12 AM, Stefan Agner wrote:
>> If no other SoC is making use of it, its probably better to implement
>> it in the SoC specific code (e.g. pinctrl-vf610.c?) Although, currently
>> the mapped access to the registers is only locally avail
On Mon, Jun 1, 2015 at 10:12 AM, Stefan Agner wrote:
> In some SoC's using the IMX pin controller, the IP looses its state
> when entering lowest power modes. Enhance the driver with suspend/
> resume functions restoring the pin states.
> ---
> Hi all,
>
> Currently I'm working on implementing sus
On Mon, Jun 1, 2015 at 5:12 PM, Stefan Agner wrote:
> In some SoC's using the IMX pin controller, the IP looses its state
> when entering lowest power modes. Enhance the driver with suspend/
> resume functions restoring the pin states.
(...)
This is weird:
> + for (i = 0; i < info->ninpu
In some SoC's using the IMX pin controller, the IP looses its state
when entering lowest power modes. Enhance the driver with suspend/
resume functions restoring the pin states.
---
Hi all,
Currently I'm working on implementing suspend-to-memory for Freescale
Vybrid (vf610) using the SoC's LPSTOP2
5 matches
Mail list logo
