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¶

(PINMUX && SOC_SERIES_LPC11U6X) || PINMUX

(Includes any dependencies from ifs and menus.)

Defaults¶

1
45

Kconfig definitions¶

At <Zephyr>/soc/arm/nxp_lpc/lpc11u6x/Kconfig.defconfig.series:22

Included via <Zephyr>/Kconfig:8 → <Zephyr>/Kconfig.zephyr:25 → <BuildDir>/Kconfig/Kconfig.soc.defconfig:1 → <Zephyr>/soc/arm/nxp_lpc/Kconfig.defconfig:4

Menu path: (Top)

config PINMUX_INIT_PRIORITY
    int
    default 1
    depends on PINMUX && SOC_SERIES_LPC11U6X

At <Zephyr>/drivers/pinmux/Kconfig:20

Included via <Zephyr>/Kconfig:8 → <Zephyr>/Kconfig.zephyr:32 → <Zephyr>/drivers/Kconfig:46

Menu path: (Top) → Device Drivers → Enable board pinmux driver

config PINMUX_INIT_PRIORITY
    int "Init priority"
    default 45
    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.

(The ‘depends on’ condition includes propagated dependencies from ifs and menus.)