All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Duje Mihanović" <duje.mihanovic@skole.hr>
To: Rob Herring <robh@kernel.org>
Cc: Conor Dooley <conor@kernel.org>, Vinod Koul <vkoul@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	dmaengine@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: mmp-dma: convert to YAML
Date: Wed, 31 Jan 2024 22:08:07 +0100	[thread overview]
Message-ID: <4894227.31r3eYUQgx@radijator> (raw)
In-Reply-To: <20240131171857.GA1531631-robh@kernel.org>

On Wednesday, January 31, 2024 6:18:57 PM CET Rob Herring wrote:
> On Sun, Jan 28, 2024 at 07:01:36PM +0100, Duje Mihanović wrote:
> > On Sunday, January 28, 2024 6:28:03 PM CET Conor Dooley wrote:
> > > That said, for properties that are only usable on some platforms, please
> > > define them at the top level and conditionally permit/constrain them.
> > 
> > Could you please point me to how to do so if this if/then does not do it
> > properly?
> 
> Negate the if and then:
> 
> then:
>   properties:
>     asram: false
> 
> There are lots of examples in the tree.

This works as expected, thanks.

> > > > +unevaluatedProperties: false
> > > > +
> > > > +examples:
> > > > +  # Peripheral controller
> > > > +  - |
> > > > +    pdma0: dma-controller@d4000000 {
> > > 
> > > The label is not needed here or below.
> > > In fact, I'd probably delete the second example as it shows nothing that
> > > the first one does not.
> > 
> > I'd rather add the asram property in the second node (adding onto the 
above
> > comment, I now see that it shouldn't have even passed dt_binding_check
> > because of the missing asram, but it did).
> 
> It passed because 'required' is what checks for property presence and
> nowhere is asram required. It is missing a type definition which should
> have warned, but may not since it is under an 'if'.

I thought specifying minItems would have the same effect, but that turned out 
not to be the case. Also, the 'if' did indeed suppress the missing type 
warning.

Regards,
-- 
Duje




      reply	other threads:[~2024-01-31 21:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-27 16:53 [PATCH] dt-bindings: mmp-dma: convert to YAML Duje Mihanović
2024-01-28 17:28 ` Conor Dooley
2024-01-28 18:01   ` Duje Mihanović
2024-01-31 17:18     ` Rob Herring
2024-01-31 21:08       ` Duje Mihanović [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=4894227.31r3eYUQgx@radijator \
    --to=duje.mihanovic@skole.hr \
    --cc=conor@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmaengine@vger.kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=vkoul@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 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.