pinctrl: pinctrl_register_mappings() shouldn't be __init

It may be common for pinctrl_register_mappings() to be used from __init
context, but there's no reason that additional mappings shouldn't be
added at a later point, e.g. if loading modules that add pin controllers
and their mapping tables.

Signed-off-by: Stephen Warren <swarren@nvidia.com>
Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
This commit is contained in:
Stephen Warren 2012-02-19 23:45:41 -07:00 committed by Linus Walleij
parent 449d16b025
commit 13398a4b90
1 changed files with 5 additions and 10 deletions

View File

@ -641,18 +641,13 @@ EXPORT_SYMBOL_GPL(pinctrl_disable);
/** /**
* pinctrl_register_mappings() - register a set of pin controller mappings * pinctrl_register_mappings() - register a set of pin controller mappings
* @maps: the pincontrol mappings table to register, this should be marked with * @maps: the pincontrol mappings table to register. This should probably be
* __initdata so it can be discarded after boot, this function will * marked with __initdata so it can be discarded after boot. This
* perform a shallow copy for the mapping entries. * function will perform a shallow copy for the mapping entries.
* @num_maps: the number of maps in the mapping table * @num_maps: the number of maps in the mapping table
*
* Only call this once during initialization of your machine, the function is
* tagged as __init and won't be callable after init has completed. The map
* passed into this function will be owned by the pinmux core and cannot be
* freed.
*/ */
int __init pinctrl_register_mappings(struct pinctrl_map const *maps, int pinctrl_register_mappings(struct pinctrl_map const *maps,
unsigned num_maps) unsigned num_maps)
{ {
void *tmp_maps; void *tmp_maps;
int i; int i;