On 07/29/2013 03:05 AM, Tony Lindgren wrote: > * Stephen Warren <swarren@xxxxxxxxxxxxx> [130719 11:59]: >> On 07/19/2013 01:29 AM, Tony Lindgren wrote: >>> >>> I'd vote for keeping the existing behaviour with pinctrl_select_state() >>> when no active state is defined. >> >> Yes, I think that will work, since the active state cannot exist before >> this new scheme is in place. > > Right. > >> But, this needs to be very clearly spell out in the DT binding >> documentation: If you have states default/idle/sleep, they're complete >> alternatives, whereas if you have states default/active/idle/sleep, the >> latter 3 are alternatives that build on top of the first. I foresee mass >> confusion, but perhaps I'm being pessimistic. > > I'm hoping we can automate the runtime PM handling with default/active/idle > completely from the consumer driver point of view. And then when that's > working, we can probably deprecate any runtime PM related handling using > pinctr_select_state() and print warnings. And we can also improve the > documentation so no new users will use the default/idle/sleep for runtime > PM unless they really want to. I was thinking more about people writing the device trees that define these states; they need to explicitly make the choice re: overlapping states or independent states. We should not plan to obsolete any current usage of overlapping states since that will mean an incompatible change to the DT ABI (deprecate yes so that no more usage is added, but the kernel should still support the old way). -- 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
