-
CONFIG_PINMUX_INIT_PRIORITY¶
Init priority
Type: int
Help¶
Pinmux driver initialization priority. 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 and KERNEL_INIT_PRIORITY_DEVICE. There are exceptions to this rule for particular boards. Don’t change this value unless you know what you are doing.
Direct dependencies¶
BOARD_GALILEO || SOC_SERIES_QUARK_X1000 || PINMUX
(Includes any dependencies from if’s and menus.)
Defaults¶
- 80 if
PINMUX&&BOARD_GALILEO - 80 if
PINMUX&&SOC_SERIES_QUARK_X1000 - 45 if
PINMUX
Kconfig definitions¶
At boards/x86/galileo/Kconfig.defconfig:111
Included via Kconfig:10 → Kconfig.zephyr:21
Menu path: (top menu)
config PINMUX_INIT_PRIORITY
int
default 80 if PINMUX && BOARD_GALILEO
depends on BOARD_GALILEO
At soc/x86/intel_quark/quark_x1000/Kconfig.defconfig.series:182
Included via Kconfig:10 → Kconfig.zephyr:23 → soc/x86/intel_quark/Kconfig.defconfig:3
Menu path: (top menu)
config PINMUX_INIT_PRIORITY
int
default 80 if PINMUX && SOC_SERIES_QUARK_X1000
depends on SOC_SERIES_QUARK_X1000
At drivers/pinmux/Kconfig:23
Included via Kconfig:10 → Kconfig.zephyr:35 → drivers/Kconfig:44
Menu path: (top menu) → Device Drivers → Enable board pinmux driver
config PINMUX_INIT_PRIORITY
int
prompt "Init priority" if PINMUX
default 45 if PINMUX
depends on PINMUX
help
Pinmux driver initialization priority.
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
and KERNEL_INIT_PRIORITY_DEVICE. There are exceptions to this
rule for particular boards. Don't change this value unless you
know what you are doing.
(Definitions include propagated dependencies, including from if’s and menus.)