[PATCH 1/3] spi: dt-bindings: fsl-qspi: support SpacemiT K3

[Conor Dooley]

On Tue, May 19, 2026 at 02:15:55PM +0800, Zhengyu He wrote:
> Add the SpacemiT K3 QSPI compatible to the fsl-qspi binding.
> 
> K3 has its own SoC integration, so board DTs should describe it
> with a K3-specific compatible instead of reusing the K1 string.
> 
> Signed-off-by: Zhengyu He <hezhy472013 at gmail.com>
> Signed-off-by: Cody Kang <cody.kang.hk at outlook.com>
> ---
>  Documentation/devicetree/bindings/spi/fsl,spi-fsl-qspi.yaml | 5 ++++-
>  1 file changed, 4 insertions(+), 1 deletion(-)
> 
> diff --git a/Documentation/devicetree/bindings/spi/fsl,spi-fsl-qspi.yaml b/Documentation/devicetree/bindings/spi/fsl,spi-fsl-qspi.yaml
> index 1d10cfbad86c..025f10ed242c 100644
> --- a/Documentation/devicetree/bindings/spi/fsl,spi-fsl-qspi.yaml
> +++ b/Documentation/devicetree/bindings/spi/fsl,spi-fsl-qspi.yaml
> @@ -20,6 +20,7 @@ properties:
>            - fsl,ls1021a-qspi
>            - fsl,ls2080a-qspi
>            - spacemit,k1-qspi
> +          - spacemit,k3-qspi
>        - items:
>            - enum:
>                - fsl,ls1043a-qspi


Given the driver has:
|        { .compatible = "spacemit,k1-qspi", .data = &spacemit_k1_data, },
|+       { .compatible = "spacemit,k3-qspi", .data = &spacemit_k1_data, },
this looks wrong.
The k3 should fall back to the k1 compatible unless there's some
non-obvious reason why it can't.

pw-bot: changes-requested

Thanks,
Conor.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 228 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-riscv/attachments/20260519/86cd1f4f/attachment.sig>