Skip to content

Road from pinmux to pinctrl #39740

@carlescufi

Description

@carlescufi

Goals of the transition for each SoC family

  • nRF
    • Allow users to continue using <signal>-pin properties during the transition period (when CONFIG_PINCTRL=n)
    • No pre-defined combinations since almost every pin can take any function
  • NXP
    • i.MX
    • Kinetis
    • LPC
  • STM32
    • Existing Devicetree representation will be kept
    • Pinmux driver will be kept in tree during the transition period, but will not be used by any driver

Timeline

  • Grace period between 2.7.99 and 3.1 where both pinctrl and pinmux coexist, no deprecation
  • By 3.1 all in-tree boards must've switched to pinctrl:
    • Pinctrl driver complete
    • All peripheral drivers for the SoC family supporting pinctrl
    • In-tree boards use the new pinctrl representation
  • After 3.1 is released (3.1.99) we deprecate pinmux
  • Zephyr 3.2 deprecates pinmux, Zephyr 3.4 removes pinmux

Porting status

Custom APIs

New drivers

List of new driver proposals for SoCs that did not have an existing pinmux driver.

Metadata

Metadata

Assignees

Labels

DeprecationAPI planned for deprecationEnhancementChanges/Updates/Additions to existing featuresMetaA collection of features, enhancements or bugsarea: Pinctrlarea: Pinmux

Projects

Status

No status

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions