public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>,
	linux-renesas-soc@vger.kernel.org
Cc: Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	devicetree@vger.kernel.org
Subject: Re: [RFC PATCH] dt-bindings: incomplete-devices: allow additional properties
Date: Thu, 2 Apr 2026 15:24:39 +0200	[thread overview]
Message-ID: <c2095c20-834d-4f52-aa82-07f0cd6fb228@kernel.org> (raw)
In-Reply-To: <20260402123444.14177-2-wsa+renesas@sang-engineering.com>

On 02/04/2026 14:27, Wolfram Sang wrote:
> Linux test infrastructure is rightfully handled as 'incomplete devices.'
> It may need additional properties, though, like this mailbox test entry:
> 
> mailbox_test_send_to_recv@c1000000 {
>         compatible = "mailbox-test";
>         broken-usage-of-incorrect-compatible;
>         reg = <0x0 0xc1000000 0x0 0x100>;
>         mboxes = <&mfis 0 (MFIS_CHANNEL_IICR | MFIS_CHANNEL_TX)>,
>                  <&mfis 0 (MFIS_CHANNEL_EICR | MFIS_CHANNEL_RX)>;
>         mbox-names = "tx", "rx";
>  };
> 
> So, allow additional properties to prevent:
> 
> .../arch/arm64/boot/dts/renesas/r8a78000-ironhide.dtb: mailbox_test_send_to_recv@c1000000 (mailbox-test): 'broken-usage-of-incorrect-compatible', 'mbox-names', 'mboxes', 'reg' do not match any of the regexes: '^pinctrl-[0-9]+$'
> 
> Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com>

And with your patch how does the warning look like?

This solves nothing - the entire point is to have warning for
'broken-usage-of-incorrect-compatible'. If there are warnings for
mboxes, does not really matter.


> ---
> 
> Maybe this is not worth the hazzle because these testing bindings should
> never be used in production DTs. During development, however, this is
> useful because it reduces noise, so real bugs become more visible.
> 
> If this is not applicable for reasons I overlooked, another approach
> could be to use 'broken-usage-of-incorrect-compatible' as an early exit
> in fixup_node_props() of the validator?
> 
> RFC because of all of the above. Is this worth it?
> 
>  Documentation/devicetree/bindings/incomplete-devices.yaml | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/Documentation/devicetree/bindings/incomplete-devices.yaml b/Documentation/devicetree/bindings/incomplete-devices.yaml
> index 4bb6c0141e9f..8f6df738f5e9 100644
> --- a/Documentation/devicetree/bindings/incomplete-devices.yaml
> +++ b/Documentation/devicetree/bindings/incomplete-devices.yaml
> @@ -282,4 +282,4 @@ required:
>    - compatible
>    - broken-usage-of-incorrect-compatible
>  
> -additionalProperties: false
> +additionalProperties: true


Best regards,
Krzysztof

  reply	other threads:[~2026-04-02 13:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-02 12:27 [RFC PATCH] dt-bindings: incomplete-devices: allow additional properties Wolfram Sang
2026-04-02 13:24 ` Krzysztof Kozlowski [this message]
2026-04-02 14:52   ` Wolfram Sang
2026-04-02 13:26 ` 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=c2095c20-834d-4f52-aa82-07f0cd6fb228@kernel.org \
    --to=krzk@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=wsa+renesas@sang-engineering.com \
    /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