Add new compatible string for SpacemiT K3 SoC, the pinctrl IP shares
almost same logic with previous K1 generation, but has different register
offset and pin configuration, for example the drive strength and
schmitter trigger settings has been changed.
Signed-off-by: Yixun Lan <dlan@gentoo.org>
---
Documentation/devicetree/bindings/pinctrl/spacemit,k1-pinctrl.yaml | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/pinctrl/spacemit,k1-pinctrl.yaml b/Documentation/devicetree/bindings/pinctrl/spacemit,k1-pinctrl.yaml
index d80e88aa07b4..c5b0218ad625 100644
--- a/Documentation/devicetree/bindings/pinctrl/spacemit,k1-pinctrl.yaml
+++ b/Documentation/devicetree/bindings/pinctrl/spacemit,k1-pinctrl.yaml
@@ -11,7 +11,9 @@ maintainers:
properties:
compatible:
- const: spacemit,k1-pinctrl
+ enum:
+ - spacemit,k1-pinctrl
+ - spacemit,k3-pinctrl
reg:
items:
--
2.52.0
Hi Yixun,
On Sat, Dec 20, 2025 at 06:14:53PM +0800, Yixun Lan wrote:
> Add new compatible string for SpacemiT K3 SoC, the pinctrl IP shares
> almost same logic with previous K1 generation, but has different register
> offset and pin configuration, for example the drive strength and
> schmitter trigger settings has been changed.
>
> Signed-off-by: Yixun Lan <dlan@gentoo.org>
> ---
> Documentation/devicetree/bindings/pinctrl/spacemit,k1-pinctrl.yaml | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/Documentation/devicetree/bindings/pinctrl/spacemit,k1-pinctrl.yaml b/Documentation/devicetree/bindings/pinctrl/spacemit,k1-pinctrl.yaml
> index d80e88aa07b4..c5b0218ad625 100644
> --- a/Documentation/devicetree/bindings/pinctrl/spacemit,k1-pinctrl.yaml
> +++ b/Documentation/devicetree/bindings/pinctrl/spacemit,k1-pinctrl.yaml
> @@ -11,7 +11,9 @@ maintainers:
>
> properties:
> compatible:
> - const: spacemit,k1-pinctrl
> + enum:
> + - spacemit,k1-pinctrl
> + - spacemit,k3-pinctrl
The drive-strength description should be updated. The driver uses a
different current table between K1 and K3, but the binding description does not
mention K3.
- Troy
>
> reg:
> items:
>
> --
> 2.52.0
>
>
Hi Troy, On 10:56 Wed 24 Dec , Troy Mitchell wrote: > Hi Yixun, > > On Sat, Dec 20, 2025 at 06:14:53PM +0800, Yixun Lan wrote: > > Add new compatible string for SpacemiT K3 SoC, the pinctrl IP shares > > almost same logic with previous K1 generation, but has different register > > offset and pin configuration, for example the drive strength and > > schmitter trigger settings has been changed. > > > > Signed-off-by: Yixun Lan <dlan@gentoo.org> > > --- > > Documentation/devicetree/bindings/pinctrl/spacemit,k1-pinctrl.yaml | 4 +++- > > 1 file changed, 3 insertions(+), 1 deletion(-) > > > > diff --git a/Documentation/devicetree/bindings/pinctrl/spacemit,k1-pinctrl.yaml b/Documentation/devicetree/bindings/pinctrl/spacemit,k1-pinctrl.yaml > > index d80e88aa07b4..c5b0218ad625 100644 > > --- a/Documentation/devicetree/bindings/pinctrl/spacemit,k1-pinctrl.yaml > > +++ b/Documentation/devicetree/bindings/pinctrl/spacemit,k1-pinctrl.yaml > > @@ -11,7 +11,9 @@ maintainers: > > > > properties: > > compatible: > > - const: spacemit,k1-pinctrl > > + enum: > > + - spacemit,k1-pinctrl > > + - spacemit,k3-pinctrl > The drive-strength description should be updated. The driver uses a > different current table between K1 and K3, but the binding description does not > mention K3. > yes, I realised already, will update in next version -- Yixun Lan (dlan)
© 2016 - 2026 Red Hat, Inc.