From: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
To: CL Wang <cl634@andestech.com>, Mark Brown <broonie@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Kousik Sanagavarapu <five231003@gmail.com>,
Vladimir Moravcevic <vmoravcevic@axiado.com>,
Tzu-Hao Wei <twei@axiado.com>, Swark Yang <syang@axiado.com>,
Prasad Bolisetty <pbolisetty@axiado.com>,
Karthikeyan Mitran <kmitran@axiado.com>,
Michal Simek <michal.simek@amd.com>
Cc: linux-spi@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
Subject: [PATCH 1/5] spi: dt-bindings: andestech,ae350-spi: Drop redundant num-cs
Date: Tue, 04 Aug 2026 09:16:57 +0200 [thread overview]
Message-ID: <20260804-spi-num-cs-v1-1-4ccb13dcc7b0@oss.qualcomm.com> (raw)
In-Reply-To: <20260804-spi-num-cs-v1-0-4ccb13dcc7b0@oss.qualcomm.com>
'num-cs' property is a single integer, thus the binding should not set
maxItems. This could be replaced with proper min/max constraints for
values, except that hardware (as expressed in driver) supports only one
native chipselect, thus constraint of "const:1" would make the property
implied by the compatible. spi-controller.yaml schema already defines
this property, so its presence here is redundant.
Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
---
Documentation/devicetree/bindings/spi/andestech,ae350-spi.yaml | 4 ----
1 file changed, 4 deletions(-)
diff --git a/Documentation/devicetree/bindings/spi/andestech,ae350-spi.yaml b/Documentation/devicetree/bindings/spi/andestech,ae350-spi.yaml
index 8e441742cee6..381042e07fd0 100644
--- a/Documentation/devicetree/bindings/spi/andestech,ae350-spi.yaml
+++ b/Documentation/devicetree/bindings/spi/andestech,ae350-spi.yaml
@@ -24,10 +24,6 @@ properties:
clocks:
maxItems: 1
- num-cs:
- description: Number of chip selects supported
- maxItems: 1
-
dmas:
items:
- description: Transmit FIFO DMA channel
--
2.53.0
next prev parent reply other threads:[~2026-08-04 7:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-04 7:16 [PATCH 0/5] spi: Few cleanups while looking at num-cs Krzysztof Kozlowski
2026-08-04 7:16 ` Krzysztof Kozlowski [this message]
2026-08-04 7:16 ` [PATCH 2/5] spi: dt-bindings: marvell,armada-3700-spi: Drop redundant num-cs Krzysztof Kozlowski
2026-08-04 7:16 ` [PATCH 3/5] spi: dt-bindings: axiado,ax3000-spi: Drop duplicated type/ref Krzysztof Kozlowski
2026-08-04 7:17 ` [PATCH 4/5] spi: dt-bindings: spi-cadence: " Krzysztof Kozlowski
2026-08-04 7:17 ` [PATCH 5/5] spi: atcspi200: Drop redundant andestech,qilai-spi compatible Krzysztof Kozlowski
2026-08-04 7:27 ` sashiko-bot
2026-08-04 17:51 ` [PATCH 0/5] spi: Few cleanups while looking at num-cs Mark Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260804-spi-num-cs-v1-1-4ccb13dcc7b0@oss.qualcomm.com \
--to=krzysztof.kozlowski@oss.qualcomm.com \
--cc=broonie@kernel.org \
--cc=cl634@andestech.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=five231003@gmail.com \
--cc=kmitran@axiado.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=michal.simek@amd.com \
--cc=pbolisetty@axiado.com \
--cc=robh@kernel.org \
--cc=syang@axiado.com \
--cc=twei@axiado.com \
--cc=vmoravcevic@axiado.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox