2015-06-16 11:05 GMT+02:00 Stefan Agner <ste...@agner.ch>:
> The pltfm_suspend/resume functions have been used since quite some time.
> However, the Toradex branch carries a patch which introduces local
> suspend/resume functions to work around a system PM vs. runtime PM
> suspend issue.

Hence my confusion :).

> > I am thinking sdhci_suspend_host would be good location, but then the
> > change will effect a lot more drivers. Maybe a good thing?
>
> I guess most device trees don't have a specific idle/sleep state
> specification, how does the pinctrl API act in this situation?

pinctrl API can handle if states are not defined. Also the API calls
are considered successful when successfully set state or if no state
definition is present.

Undefined states are set to ERR_PTR(-ENODEV)

and in the API calls there is a

if (IS_ERR(state))
    return 0; /* No such state */

>
> FWIW, the Vybrid SoC is not able to control pins during LPSTOP suspend,
> hence configuring the sleep mode explicitly for system PM is not very
> useful on that platform. However, for runtime PM it coud still be
> valuable I guess.

I was testing the "standby" state and noticed unwanted states on some
pins and hence this patch :). Good to know about LPSTOP.

-- 
Med Vänliga Hälsningar / Best Regards

*******************************************************************
Mirza Krak
Host Mobility AB
mirza.k...@hostmobility.com
Anders Personsgatan 12, 416 64 Göteborg
Sweden
http://www.hostmobility.com
Direct: +46 31 31 32 704
Phone: +46 31 31 32 700
Fax: +46 31 80 67 51
Mobile: +46 730 28 06 22
*******************************************************************
--
To unsubscribe from this list: send the line "unsubscribe linux-mmc" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to