Re: [PATCH v3 1/2] dt-bindings: spi: nuvoton,ma35d1-qspi: Allow additional GPIO chip selects

Krzysztof Kozlowski <[email protected]> Tue, 4 Aug 2026 09:05:15 +0200

Newsgroups	org.kernel.vger.linux-devicetree,org.infradead.lists.linux-arm-kernel,org.kernel.vger.linux-kernel,org.kernel.vger.linux-spi
Message-ID	<20260804-smilodon-of-imminent-recreation-aa579b@quoll>

On Mon, Aug 03, 2026 at 03:49:12PM +0800, Chi-Wen Weng wrote:
> From: Chi-Wen Weng <[email protected]>
> 
> The MA35D1 QSPI controller provides two native chip selects, but the
> generic SPI controller binding defines num-cs as the total number of
> native and GPIO-based chip selects.
> 
> Remove the maximum value of two from num-cs so that board device trees
> can describe additional GPIO chip selects while retaining two as the
> default chip-select count.
> 
> Signed-off-by: Chi-Wen Weng <[email protected]>
> ---
>  Documentation/devicetree/bindings/spi/nuvoton,ma35d1-qspi.yaml | 1 -
>  1 file changed, 1 deletion(-)
> 
> diff --git a/Documentation/devicetree/bindings/spi/nuvoton,ma35d1-qspi.yaml b/Documentation/devicetree/bindings/spi/nuvoton,ma35d1-qspi.yaml
> index 377ccf4fb224..f837367e6d5f 100644
> --- a/Documentation/devicetree/bindings/spi/nuvoton,ma35d1-qspi.yaml
> +++ b/Documentation/devicetree/bindings/spi/nuvoton,ma35d1-qspi.yaml
> @@ -30,7 +30,6 @@ properties:
>  
>    num-cs:
>      minimum: 1
> -    maximum: 2
>      default: 2

Isn't num-cs the number of native chip selects?

Best regards,
Krzysztof