devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jun Guo <jun.guo@cixtech.com>
To: peter.chen@cixtech.com, fugang.duan@cixtech.com, robh@kernel.org,
	krzk+dt@kernel.org, conor+dt@kernel.org, broonie@kernel.org
Cc: linux-spi@vger.kernel.org, michal.simek@amd.com,
	cix-kernel-upstream@cixtech.com,
	linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, Jun Guo <jun.guo@cixtech.com>
Subject: [PATCH 1/3] dt-bindings: spi: spi-cadence: document optional fifo-width DT property
Date: Tue, 30 Sep 2025 15:56:42 +0800	[thread overview]
Message-ID: <20250930075644.1665970-2-jun.guo@cixtech.com> (raw)
In-Reply-To: <20250930075644.1665970-1-jun.guo@cixtech.com>

Add documentation for the optional 'fifo-width' device tree property
for the Cadence SPI controller.

Signed-off-by: Jun Guo <jun.guo@cixtech.com>
---
 .../devicetree/bindings/spi/spi-cadence.yaml          | 11 +++++++++++
 1 file changed, 11 insertions(+)

diff --git a/Documentation/devicetree/bindings/spi/spi-cadence.yaml b/Documentation/devicetree/bindings/spi/spi-cadence.yaml
index 8de96abe9da1..b2e3f217473b 100644
--- a/Documentation/devicetree/bindings/spi/spi-cadence.yaml
+++ b/Documentation/devicetree/bindings/spi/spi-cadence.yaml
@@ -62,6 +62,17 @@ properties:
     items:
       - const: spi
 
+  fifo-width:
+    description: |
+      This property specifies the FIFO data width (in bits) of the hardware.
+      It must be configured according to the actual FIFO width set during
+      the IP design. For instance, if the hardware FIFO is 32 bits wide,
+      this property should be set to 32.
+    $ref: /schemas/types.yaml#/definitions/uint32
+    minimum: 8
+    maximum: 32
+    default: 8
+
 required:
   - compatible
   - reg
-- 
2.34.1


  reply	other threads:[~2025-09-30  7:56 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-30  7:56 [PATCH 0/3] spi-cadence: support transmission with bits_per_word Jun Guo
2025-09-30  7:56 ` Jun Guo [this message]
2025-09-30 18:51   ` [PATCH 1/3] dt-bindings: spi: spi-cadence: document optional fifo-width DT property Conor Dooley
     [not found]     ` <SI6PR06MB7104F6012ADAFDBC7D553F9AFFE6A@SI6PR06MB7104.apcprd06.prod.outlook.com>
2025-10-01 14:36       ` 回复: " Jun Guo
2025-10-01 18:04         ` Conor Dooley
2025-10-02 14:55           ` 回复: " Jun Guo
2025-10-03 14:58           ` Jun Guo
2025-10-09  9:51             ` Jun Guo
2025-10-09 17:36               ` Conor Dooley
2025-09-30  7:56 ` [PATCH 2/3] spi: spi-cadence: supports transmission with bits_per_word of 16 and 32 Jun Guo
2025-10-10  7:50   ` 回复: " Jun Guo
2025-10-10 11:46     ` Mark Brown
2025-09-30  7:56 ` [PATCH 3/3] arm64: dts: cix: add the fifo-width configuration field for cadence SPI Jun Guo

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=20250930075644.1665970-2-jun.guo@cixtech.com \
    --to=jun.guo@cixtech.com \
    --cc=broonie@kernel.org \
    --cc=cix-kernel-upstream@cixtech.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=fugang.duan@cixtech.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=peter.chen@cixtech.com \
    --cc=robh@kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).