Commit 13398a4b authored by Stephen Warren's avatar Stephen Warren Committed by Linus Walleij
Browse files

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: default avatarStephen Warren <swarren@nvidia.com>
Signed-off-by: default avatarLinus Walleij <linus.walleij@linaro.org>
parent 449d16b0

drivers/pinctrl/core.c

+5 −10
Original line number Diff line number Diff line
@@ -641,17 +641,12 @@ EXPORT_SYMBOL_GPL(pinctrl_disable); 


/**

 * pinctrl_register_mappings() - register a set of pin controller mappings

 * @maps: the pincontrol mappings table to register, this should be marked with

 *	__initdata so it can be discarded after boot, this function will

 *	perform a shallow copy for the mapping entries.

 * @maps: the pincontrol mappings table to register. This should probably be

 *	marked with __initdata so it can be discarded after boot. This

 *	function will perform a shallow copy for the mapping entries.

 * @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)

{

	void *tmp_maps;

CRA Git | Maintained and supported by SUSTech CRA and CCSE