From: Daniel Matyas <matyasdaniel005@gmail.com>
To: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
matyasdaniel005@gmail.com, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, gregkh@linuxfoundation.org,
linux-staging@lists.linux.dev
Subject: [PATCH] dt-bindings: axis-fifo: Added missing binding
Date: Wed, 16 Sep 2026 23:11:50 +0300 [thread overview]
Message-ID: <20260916201253.483877-1-matyasdaniel005@gmail.com> (raw)
drivers/staging/axis-fifo/axis-fifo.txt file described how the
devicetree of the driver should look like. Convert it to .yaml file.
Issue found by checkpatch.
Signed-off-by: Daniel Matyas <matyasdaniel005@gmail.com>
---
.../axis-fifo/xlnx,axi-fifo-mm-s.yaml | 257 ++++++++++++++++++
1 file changed, 257 insertions(+)
create mode 100644 Documentation/devicetree/bindings/axis-fifo/xlnx,axi-fifo-mm-s.yaml
diff --git a/Documentation/devicetree/bindings/axis-fifo/xlnx,axi-fifo-mm-s.yaml b/Documentation/devicetree/bindings/axis-fifo/xlnx,axi-fifo-mm-s.yaml
new file mode 100644
index 000000000000..ef1e6bcf782d
--- /dev/null
+++ b/Documentation/devicetree/bindings/axis-fifo/xlnx,axi-fifo-mm-s.yaml
@@ -0,0 +1,257 @@
+# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/axis-fifo/xlnx,axi-fifo-mm-s.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: Xilinx AXI-Stream FIFO v4.1 IP core
+
+maintainers:
+ - Daniel Matyas <matyasdaniel005@gmail.com>
+
+description: |
+ This IP core has read and write AXI-Stream FIFOs, the contents of which can
+ be accessed from the AXI4 memory-mapped interface. This is useful for
+ transferring data from a processor into the FPGA fabric. The driver creates
+ a character device that can be read/written to with standard
+ open/read/write/close.
+
+ See Xilinx PG080 document for IP details.
+
+ Currently supports only store-forward mode with a 32-bit AXI4-Lite
+ interface. DOES NOT support:
+ - cut-through mode
+ - AXI4 (non-lite)
+
+properties:
+ compatible:
+ enum:
+ - xlnx,axis-fifo-mm-s-4.1
+ - xlnx,axis-fifo-mm-s-4.2
+ - xlnx,axis-fifo-mm-s-4.3
+
+ interrupt-names:
+ const: interrupt
+
+ interrupts:
+ maxItems: 1
+
+ reg:
+ maxItems: 1
+
+ xlnx,axi-str-rxd-protocol:
+ $ref: /schemas/types.yaml#/definitions/string
+ const: XIL_AXI_STREAM_ETH_DATA
+ description: AXI4-Stream RX data protocol
+
+ xlnx,axi-str-rxd-tdata-width:
+ $ref: /schemas/types.yaml#/definitions/uint32
+ const: 0x20
+ description: AXI4-Stream RX data width
+
+ xlnx,axi-str-txc-protocol:
+ $ref: /schemas/types.yaml#/definitions/string
+ const: XIL_AXI_STREAM_ETH_CTRL
+ description: AXI4-Stream TX control protocol
+
+ xlnx,axi-str-txc-tdata-width:
+ $ref: /schemas/types.yaml#/definitions/uint32
+ const: 0x20
+ description: AXI4-Stream TX control data width
+
+ xlnx,axi-str-txd-protocol:
+ $ref: /schemas/types.yaml#/definitions/string
+ const: XIL_AXI_STREAM_ETH_DATA
+ description: AXI4-Stream TX data protocol
+
+ xlnx,axi-str-txd-tdata-width:
+ $ref: /schemas/types.yaml#/definitions/uint32
+ const: 0x20
+ description: AXI4-Stream TX data width
+
+ xlnx,axis-tdest-width:
+ $ref: /schemas/types.yaml#/definitions/uint32
+ description: AXI-Stream TDEST width (ignored by the driver)
+
+ xlnx,axis-tid-width:
+ $ref: /schemas/types.yaml#/definitions/uint32
+ description: AXI-Stream TID width (ignored by the driver)
+
+ xlnx,axis-tuser-width:
+ $ref: /schemas/types.yaml#/definitions/uint32
+ description: AXI-Stream TUSER width (ignored by the driver)
+
+ xlnx,data-interface-type:
+ $ref: /schemas/types.yaml#/definitions/uint32
+ const: 0x0
+ description: ignored by the driver
+
+ xlnx,has-axis-tdest:
+ $ref: /schemas/types.yaml#/definitions/uint32
+ const: 0x0
+ description: this feature isn't supported
+
+ xlnx,has-axis-tid:
+ $ref: /schemas/types.yaml#/definitions/uint32
+ const: 0x0
+ description: this feature isn't supported
+
+ xlnx,has-axis-tkeep:
+ $ref: /schemas/types.yaml#/definitions/uint32
+ const: 0x0
+ description: this feature isn't supported
+
+ xlnx,has-axis-tstrb:
+ $ref: /schemas/types.yaml#/definitions/uint32
+ const: 0x0
+ description: this feature isn't supported
+
+ xlnx,has-axis-tuser:
+ $ref: /schemas/types.yaml#/definitions/uint32
+ const: 0x0
+ description: this feature isn't supported
+
+ xlnx,rx-fifo-depth:
+ $ref: /schemas/types.yaml#/definitions/uint32
+ description: Depth of RX FIFO in words
+
+ xlnx,rx-fifo-pe-threshold:
+ $ref: /schemas/types.yaml#/definitions/uint32
+ description: RX programmable empty interrupt threshold
+ (ignored by the driver)
+
+ xlnx,rx-fifo-pf-threshold:
+ $ref: /schemas/types.yaml#/definitions/uint32
+ description: RX programmable full interrupt threshold
+ (ignored by the driver)
+
+ xlnx,s-axi-id-width:
+ $ref: /schemas/types.yaml#/definitions/uint32
+ const: 0x4
+ description: ignored by the driver
+
+ xlnx,s-axi4-data-width:
+ $ref: /schemas/types.yaml#/definitions/uint32
+ const: 0x20
+ description: ignored by the driver
+
+ xlnx,select-xpm:
+ $ref: /schemas/types.yaml#/definitions/uint32
+ const: 0x0
+ description: ignored by the driver
+
+ xlnx,tx-fifo-depth:
+ $ref: /schemas/types.yaml#/definitions/uint32
+ description: Depth of TX FIFO in words
+
+ xlnx,tx-fifo-pe-threshold:
+ $ref: /schemas/types.yaml#/definitions/uint32
+ description: TX programmable empty interrupt threshold
+ (ignored by the driver)
+
+ xlnx,tx-fifo-pf-threshold:
+ $ref: /schemas/types.yaml#/definitions/uint32
+ description: TX programmable full interrupt threshold
+ (ignored by the driver)
+
+ xlnx,use-rx-cut-through:
+ $ref: /schemas/types.yaml#/definitions/uint32
+ const: 0x0
+ description: this feature isn't supported
+
+ xlnx,use-rx-data:
+ $ref: /schemas/types.yaml#/definitions/uint32
+ enum: [0x0, 0x1]
+ description: <0x1> if RX FIFO is enabled, <0x0> otherwise
+
+ xlnx,use-tx-ctrl:
+ $ref: /schemas/types.yaml#/definitions/uint32
+ const: 0x0
+ description: this feature isn't supported
+
+ xlnx,use-tx-cut-through:
+ $ref: /schemas/types.yaml#/definitions/uint32
+ const: 0x0
+ description: this feature isn't supported
+
+ xlnx,use-tx-data:
+ $ref: /schemas/types.yaml#/definitions/uint32
+ enum: [0x0, 0x1]
+ description: <0x1> if TX FIFO is enabled, <0x0> otherwise
+
+required:
+ - compatible
+ - interrupt-names
+ - interrupts
+ - reg
+ - xlnx,axi-str-rxd-protocol
+ - xlnx,axi-str-rxd-tdata-width
+ - xlnx,axi-str-txc-protocol
+ - xlnx,axi-str-txc-tdata-width
+ - xlnx,axi-str-txd-protocol
+ - xlnx,axi-str-txd-tdata-width
+ - xlnx,axis-tdest-width
+ - xlnx,axis-tid-width
+ - xlnx,axis-tuser-width
+ - xlnx,data-interface-type
+ - xlnx,has-axis-tdest
+ - xlnx,has-axis-tid
+ - xlnx,has-axis-tkeep
+ - xlnx,has-axis-tstrb
+ - xlnx,has-axis-tuser
+ - xlnx,rx-fifo-depth
+ - xlnx,rx-fifo-pe-threshold
+ - xlnx,rx-fifo-pf-threshold
+ - xlnx,s-axi-id-width
+ - xlnx,s-axi4-data-width
+ - xlnx,select-xpm
+ - xlnx,tx-fifo-depth
+ - xlnx,tx-fifo-pe-threshold
+ - xlnx,tx-fifo-pf-threshold
+ - xlnx,use-rx-cut-through
+ - xlnx,use-rx-data
+ - xlnx,use-tx-ctrl
+ - xlnx,use-tx-cut-through
+ - xlnx,use-tx-data
+
+additionalProperties: false
+
+examples:
+ - |
+ axi_fifo_mm_s_0: axi_fifo_mm_s@43c00000 {
+ compatible = "xlnx,axi-fifo-mm-s-4.1";
+ interrupt-names = "interrupt";
+ interrupt-parent = <&intc>;
+ interrupts = <0 29 4>;
+ reg = <0x43c00000 0x10000>;
+ xlnx,axi-str-rxd-protocol = "XIL_AXI_STREAM_ETH_DATA";
+ xlnx,axi-str-rxd-tdata-width = <0x20>;
+ xlnx,axi-str-txc-protocol = "XIL_AXI_STREAM_ETH_CTRL";
+ xlnx,axi-str-txc-tdata-width = <0x20>;
+ xlnx,axi-str-txd-protocol = "XIL_AXI_STREAM_ETH_DATA";
+ xlnx,axi-str-txd-tdata-width = <0x20>;
+ xlnx,axis-tdest-width = <0x4>;
+ xlnx,axis-tid-width = <0x4>;
+ xlnx,axis-tuser-width = <0x4>;
+ xlnx,data-interface-type = <0x0>;
+ xlnx,has-axis-tdest = <0x0>;
+ xlnx,has-axis-tid = <0x0>;
+ xlnx,has-axis-tkeep = <0x0>;
+ xlnx,has-axis-tstrb = <0x0>;
+ xlnx,has-axis-tuser = <0x0>;
+ xlnx,rx-fifo-depth = <0x200>;
+ xlnx,rx-fifo-pe-threshold = <0x2>;
+ xlnx,rx-fifo-pf-threshold = <0x1fb>;
+ xlnx,s-axi-id-width = <0x4>;
+ xlnx,s-axi4-data-width = <0x20>;
+ xlnx,select-xpm = <0x0>;
+ xlnx,tx-fifo-depth = <0x8000>;
+ xlnx,tx-fifo-pe-threshold = <0x200>;
+ xlnx,tx-fifo-pf-threshold = <0x7ffb>;
+ xlnx,use-rx-cut-through = <0x0>;
+ xlnx,use-rx-data = <0x0>;
+ xlnx,use-tx-ctrl = <0x0>;
+ xlnx,use-tx-cut-through = <0x0>;
+ xlnx,use-tx-data = <0x1>;
+ };
+...
--
2.43.0
next reply other threads:[~2026-09-16 20:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-16 20:11 Daniel Matyas [this message]
2026-09-16 23:19 ` Rob Herring (Arm)
2026-09-17 6:29 ` Greg KH
2026-09-17 6:37 ` Krzysztof Kozlowski
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=20260916201253.483877-1-matyasdaniel005@gmail.com \
--to=matyasdaniel005@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--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
all inboxes | Powered by JetHome®