On Tue, Jun 27, 2017 at 9:59 AM, Baolin Wang <baolin.wang@xxxxxxxxxx> wrote: > On 26 June 2017 at 06:19, Linus Walleij <linus.walleij@xxxxxxxxxx> wrote: >> I meant, as part of setting the "default" state or even the "init" >> state, we would inspect the "sleep" state, use those settings, and >> program them into the registers at this early point. > > I understood your points. But we can not program all into the > registers at one early point, sometimes these sleep-related configs > need depend on some conditions in users' drivers, like on condition 1: > driver need to set one pin as input-enable when specified system goes > into deep sleep, on condition 2: driver need set this pin as > output-enable when specified system goes into deep sleep. So I still > think it is better if we introduce some standard sleep related > configs. So you mean you need special runtime states to set up sleep states? Do you have an example of how this would look in the device tree? I am sorry but I have a hard time following the use case :( Yours, Linus Walleij -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
