From: sashiko-bot@kernel.org
To: "Omer PALA" <palaomer100@gmail.com>
Cc: devicetree@vger.kernel.org, conor+dt@kernel.org, robh@kernel.org
Subject: Re: [PATCH] dt-bindings: misc: add xlnx,axi-fifo-mm-s
Date: Thu, 17 Sep 2026 06:15:45 +0000 [thread overview]
Message-ID: <20260917061545.854E31F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260917060948.14700-1-palaomer100@gmail.com>
Thank you for your contribution! Sashiko AI review found 2 potential issue(s) to consider:
- [Low] dt-bindings: duplicate legacy text binding not removed
- [Low] dt-bindings: misc: xlnx,axi-fifo-mm-s node name contains underscores
--
commit 1e96a460ceedc5eaed86e4087bdc979b41dd1bd7
Author: Omer PALA <palaomer100@gmail.com>
dt-bindings: misc: add xlnx,axi-fifo-mm-s
Add Device Tree binding documentation for the Xilinx AXI FIFO Memory Mapped
Stream IP core. This commit covers compatible strings from version 4.1
through 4.3.
> diff --git a/Documentation/devicetree/bindings/misc/xlnx,axi-fifo-mm-s.yaml b/Documentation/devicetree/bindings/misc/xlnx,axi-fifo-mm-s.yaml
> new file mode 100644
[Severity: Low]
Is the original text binding at drivers/staging/axis-fifo/axis-fifo.txt
still needed?
Since this new YAML binding covers the same hardware in the core DT bindings
directory, should the old text binding in the staging directory be removed
in this patch to prevent documentation duplication?
> index 0000000000000..f53b353ccc2a1
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/misc/xlnx,axi-fifo-mm-s.yaml
> @@ -0,0 +1,228 @@
[ ... ]
> +required:
> + - compatible
> + - reg
> + - interrupts
> + - xlnx,axi-str-rxd-tdata-width
> + - xlnx,axi-str-txd-tdata-width
> + - xlnx,rx-fifo-depth
> + - xlnx,tx-fifo-depth
> + - xlnx,use-rx-data
> + - xlnx,use-tx-data
> +
> +additionalProperties: false
> +
> +examples:
> + - |
> + axi_fifo_mm_s@43c00000 {
[Severity: Low]
Does this node name violate standard Device Tree naming conventions?
Using underscores typically triggers node_name_chars_strict warnings during
dt_binding_check validation. Should a generic name with hyphens, like
fifo@43c00000, be used instead?
> + compatible = "xlnx,axi-fifo-mm-s-4.1";
> + reg = <0x43c00000 0x10000>;
> + interrupt-parent = <&intc>;
[ ... ]
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260917060948.14700-1-palaomer100@gmail.com?part=1
next prev parent reply other threads:[~2026-09-17 6:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-17 6:09 [PATCH] dt-bindings: misc: add xlnx,axi-fifo-mm-s Omer PALA
2026-09-17 6:15 ` sashiko-bot [this message]
2026-09-17 6:38 ` Krzysztof Kozlowski
2026-09-17 6:42 ` Ömer PALA
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=20260917061545.854E31F000FF@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=palaomer100@gmail.com \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.