Devicetree
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: sashiko-reviews@lists.linux.dev
Cc: conor+dt@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: bus: Add HiSilicon local bus
Date: Tue, 6 Oct 2026 09:46:25 -0500	[thread overview]
Message-ID: <20261006144625.GA2194299-robh@kernel.org> (raw)
In-Reply-To: <20261005210035.1FD341F000FF@smtp.kernel.org>

On Mon, Oct 05, 2026 at 09:00:34PM +0000, sashiko-bot@kernel.org wrote:
> Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
> - [Low] dt-bindings: missing `required` block allows nodes without `reg` to pass
> --
> 
> commit 31cf8e8c992601dbcd36de1b649ef5c513febf6f
> Author: Rob Herring (Arm) <robh@kernel.org>
> 
> dt-bindings: bus: Add HiSilicon local bus
> 
> This commit introduces a new device tree binding schema for the HiSilicon local
> bus. It sets up validation constraints for the compatible string and registers.
> 
> > diff --git a/Documentation/devicetree/bindings/bus/hisilicon,hisi-localbus.yaml b/Documentation/devicetree/bindings/bus/hisilicon,hisi-localbus.yaml
> > new file mode 100644
> > index 0000000000000..cd9ecea88269f
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/bus/hisilicon,hisi-localbus.yaml
> 
> [ ... ]
> 
> > +properties:
> > +  compatible:
> > +    items:
> > +      - const: hisilicon,hisi-localbus
> > +      - const: simple-bus
> > +
> > +  reg:
> > +    maxItems: 1
> > +
> > +unevaluatedProperties: false
> 
> [Severity: Low]
> Should this schema include a required array to enforce the presence of the
> compatible and reg properties?

compatible is implied, but will add 'reg' when applying.

Rob

      reply	other threads:[~2026-10-06 14:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-05 20:53 [PATCH] dt-bindings: bus: Add HiSilicon local bus Rob Herring (Arm)
2026-10-05 21:00 ` sashiko-bot
2026-10-06 14:46   ` Rob Herring [this message]

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=20261006144625.GA2194299-robh@kernel.org \
    --to=robh@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.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