On 11 September 2012 00:51, Stephen Warren <swarren@xxxxxxxxxxxxx> wrote: > On 09/06/2012 05:06 AM, Thomas Abraham wrote: >> On 6 September 2012 15:04, Tomasz Figa <t.figa@xxxxxxxxxxx> wrote: >>> Hi, >>> >>> This patch shows the problem of the need to explicitly migrate all drivers >>> to pinctrl. >>> >>> Maybe we should consider extending the pinctrl subsystem to set the default >>> state automatically before binding a driver to a device, at least in case >>> of DT-based platforms? >> >> The pinctrl driver allows for activating default pin configuration >> when the pinctrl driver loads. This is referred to as "hogging". But >> should hog be used or not is something that needs to be decided. Some >> of the factors which favor the driver explicitly setting up the pin >> configuration are >> >> 1. After a suspend and resume cycle, the pin configuration registers >> may be reset to default values. Hence, during resume, the pin >> configuration has be redone. > > I'd think it's the pinctrl driver's responsibility to make hogging work > correctly across suspend/resume. Ok. I will add this functionality in the Samsung pinctrl driver. Thanks, Thomas. [...] -- To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
 |