Re: [PATCH v2 1/5] pinctrl: Allow modules to use pinctrl_[un]register_mappings

On Mon, 30 Dec 2019, Linus Walleij wrote: > On Mon, Dec 16, 2019 at 9:51 PM Hans de Goede wrote: > >> Currently only the drivers/pinctrl/devicetree.c code allows registering >> pinctrl-mappings which may later be unregistered, all other mappings >> are assumed to be permanent. >> >> Non-dt platfo

Re: [PATCH v2 1/5] pinctrl: Allow modules to use pinctrl_[un]register_mappings

Hi, On 30-12-2019 14:31, Linus Walleij wrote: On Mon, Dec 16, 2019 at 9:51 PM Hans de Goede wrote: Currently only the drivers/pinctrl/devicetree.c code allows registering pinctrl-mappings which may later be unregistered, all other mappings are assumed to be permanent. Non-dt platforms may al

Re: [PATCH v2 1/5] pinctrl: Allow modules to use pinctrl_[un]register_mappings

On Mon, Dec 16, 2019 at 9:51 PM Hans de Goede wrote: > Currently only the drivers/pinctrl/devicetree.c code allows registering > pinctrl-mappings which may later be unregistered, all other mappings > are assumed to be permanent. > > Non-dt platforms may also want to register pinctrl mappings from

[PATCH v2 1/5] pinctrl: Allow modules to use pinctrl_[un]register_mappings

Currently only the drivers/pinctrl/devicetree.c code allows registering pinctrl-mappings which may later be unregistered, all other mappings are assumed to be permanent. Non-dt platforms may also want to register pinctrl mappings from code which is build as a module, which requires being able to u