Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: Daniel28972897 <danyboy28sep@gmail.com>
Cc: conor+dt@kernel.org, devicetree@vger.kernel.org, robh@kernel.org
Subject: Re: [PATCH v2 1/2] dt-bindings: misc: convert axis-fifo binding to YAML
Date: Sat, 19 Sep 2026 03:09:59 +0000	[thread overview]
Message-ID: <20260919031000.7508D1F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260919025900.169703-2-danyboy28sep@gmail.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] dt-bindings: missing type definition for vendor properties
--

commit e279d5a2991ae1467a7af717115f8a8656d5f101
Author: Daniel28972897 <danyboy28sep@gmail.com>

dt-bindings: misc: convert axis-fifo binding to YAML

This commit converts the text-based axis-fifo binding to a YAML schema to
enable validation via dtbs_check. It preserves all original properties,
including those generated by the Xilinx IP integrator that are currently
ignored by the Linux driver.

> 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
> index 0000000000000..fffd69b128111
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/misc/xlnx,axi-fifo-mm-s.yaml
[ ... ]
> +  # The following properties are generated by the Xilinx IP integrator
> +  # for this core and may be present in real-world devicetrees, but are
> +  # not currently read by the Linux driver.
> +  xlnx,axi-str-rxd-protocol: true
> +  xlnx,axi-str-txc-protocol: true
> +  xlnx,axi-str-txc-tdata-width: true
> +  xlnx,axi-str-txd-protocol: true
> +  xlnx,axis-tdest-width: true
> +  xlnx,axis-tid-width: true

[Severity: Low]
Does this properties block in
Documentation/devicetree/bindings/misc/xlnx,axi-fifo-mm-s.yaml pass make
dt_binding_check?

The dtschema meta-schema requires all custom vendor-specific properties to
have an explicitly defined type constraint (e.g.,
$ref: /schemas/types.yaml#/definitions/uint32).

Setting these vendor properties to true without mandatory $ref type
definitions or descriptions causes a build-time validation failure when
running make dt_binding_check on the added schema.

Will these properties be updated to include the appropriate type constraints?

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260919025900.169703-1-danyboy28sep@gmail.com?part=1

  reply	other threads:[~2026-09-19  3:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-19  1:14 [PATCH] dt-bindings: misc: add binding for Xilinx AXI4-Stream FIFO MM S Daniel28972897
2026-09-19  1:24 ` sashiko-bot
2026-09-19  2:58 ` [PATCH v2 0/2] dt-bindings: misc: convert axis-fifo binding to YAML Daniel28972897
2026-09-19  2:58   ` [PATCH v2 1/2] " Daniel28972897
2026-09-19  3:09     ` sashiko-bot [this message]
2026-09-19  6:58     ` Krzysztof Kozlowski
2026-09-19  2:59   ` [PATCH v2 2/2] staging: axis-fifo: remove superseded text binding Daniel28972897
2026-09-19  6:59     ` Krzysztof Kozlowski
2026-09-19  7:47   ` [PATCH v2 0/2] dt-bindings: misc: convert axis-fifo binding to YAML Greg Kroah-Hartman

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=20260919031000.7508D1F000FF@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=danyboy28sep@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox