This series attempt to add pinctrl support for SpacemiT K3 SoC,
I've removed the RFC tag as the driver is tested on K3 SoC.
The K3 pinctrl IP shares almost same logic with previous K1 SoC generation,
but has different register offset and pin configuration, I've introduced
a pin_to_offset() function to handle the difference of register offset.
for the drive strength and schmitter trigger settings, they are also changed.
Patch #1 convert the dt-binding's drive-strength property from free text to
a more standard schema format, then patch #2 try to add pin support which
should handle pin mux, while patch #3 adjust drive strength and schmitter trigger
settings accordingly for new SoC.
Signed-off-by: Yixun Lan <dlan@gentoo.org>
---
Changes in v3:
- convert drive-strength to schema format
- Link to v2: https://lore.kernel.org/r/20251226-02-k3-pinctrl-v2-0-5172397e6831@gentoo.org
Changes in v2:
- RFC tag removed
- update dt-binding docs for drive strength
- fix wrong argument for drive strength
- Link to v1: https://lore.kernel.org/r/20251220-02-k3-pinctrl-v1-0-f6f4aea60abf@gentoo.org
---
Yixun Lan (4):
dt-bindings: pinctrl: spacemit: convert drive strength to schema format
dt-bindings: pinctrl: spacemit: add K3 SoC support
pinctrl: spacemit: k3: add initial pin support
pinctrl: spacemit: k3: adjust drive strength and schmitter trigger
.../bindings/pinctrl/spacemit,k1-pinctrl.yaml | 22 +-
drivers/pinctrl/spacemit/Kconfig | 4 +-
drivers/pinctrl/spacemit/pinctrl-k1.c | 517 +++++++++++++++++++--
3 files changed, 485 insertions(+), 58 deletions(-)
---
base-commit: 8f0b4cce4481fb22653697cced8d0d04027cb1e8
change-id: 20251125-02-k3-pinctrl-738cbddbe49d
Best regards,
--
Yixun Lan