Paul Sokolovsky 6b2a1af1cd pinmux: Make default init priority be between GPIO's prio and device prio. ... Pinmux driver almost certainly should be initialized before the rest of hardware devices (which may need specific pins already configured for them), and usually after generic GPIO drivers. Thus, its priority should be between KERNEL_INIT_PRIORITY_DEFAULT (default 40) and KERNEL_INIT_PRIORITY_DEVICE (default 50). Thus, we set PINMUX_INIT_PRIORITY to 45. There are exceptions to the rule above for particular boards. For example, BOARD=galileo has GPIO and pinmuxer on I2C bus and thus overrides PINMUX_INIT_PRIORITY to be much higher. Note that while PINMUX_INIT_PRIORITY was defined previously (at 60), it was used only for galileo, which overrides it anyway. This fix was prompted by investigation why eth_ksdk driver was non-functional after kernel priorities re-hashing: both eth_ksdk and pinmux used the same priority, and eth_ksdk happened to run before pinmux. While bumping eth_ksdk priority would help in the particular case, the same would likely reoccur with other drivers like I2C, SPI, etc. Change-Id: Ie5ca3135c1ee2fe8d9cf48d5c12e62eac63487f7 Signed-off-by: Paul Sokolovsky <paul.sokolovsky@linaro.org>		2016-11-18 16:43:45 +00:00
..
pinmux_board_frdm_k64f.c	pinmux: Make default init priority be between GPIO's prio and device prio.	2016-11-18 16:43:45 +00:00
pinmux_board_hexiwear.c	pinmux: Make default init priority be between GPIO's prio and device prio.	2016-11-18 16:43:45 +00:00
pinmux.c	pinmux: Rename frdm_k64f pinmux driver to k64	2016-10-18 21:42:31 +00:00
pinmux.h	pinmux: Rename frdm_k64f pinmux driver to k64	2016-10-18 21:42:31 +00:00