From: Marek Vasut <marek.vasut@mailbox.org>
To: Conor Dooley <conor@kernel.org>,
Marek Vasut <marek.vasut+renesas@mailbox.org>
Cc: linux-usb@vger.kernel.org, Conor Dooley <conor+dt@kernel.org>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Rob Herring <robh@kernel.org>,
Thinh Nguyen <Thinh.Nguyen@synopsys.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH v7 1/2] dt-bindings: usb: dwc3: Document Renesas R-Car Gen5 DWC3 xHCI USB controller
Date: Fri, 4 Sep 2026 18:24:04 +0200 [thread overview]
Message-ID: <7771adfd-7447-4802-ad75-7c889ad32ee7@mailbox.org> (raw)
In-Reply-To: <20260904-colonial-wimp-b37c27657664@spud>
On 9/4/26 5:32 PM, Conor Dooley wrote:
Hello Conor,
[...]
>> +required:
>> + - compatible
>> + - reg
>> + - reg-names
>> + - clocks
>> + - interrupts
>> + - phys
>> + - phy-names
>> + - power-domains
>> + - resets
>> +
>> +unevaluatedProperties: false
>
> I said this elsewhere today, but this binding has lots of "distasteful"
> properties for things that should be determined from the compatible
Which properties would those be ? (it seems
reg/clocks/interrupts/phys/power-domains/resets really need to be there
as separate properties, but maybe I am missing the point?)
> , so I
> would appreciate it if you could use additionalProperties: false here
> cite the ones you need to use explicitly.
May I ask, what exactly is the rule of thumb for
additionalProperties:false and unevaluatedProperties:false ? I seem to
struggle with picking the right one for a while now.
> Sounds like dr_mode: true and
> maximum-speed: true are all you'd need?
Ah, I think this also answers my previous question a bit. And, as for
limiting the properties that are really needed -- this pulls in the
common DWC3 USB IP core properties, which all do apply to the DWC3 core.
They might not be used on current hardware, but they are still valid for
the DWC3 core (IP).
Thank you for your help !
prev parent reply other threads:[~2026-09-04 16:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-03 21:30 Marek Vasut
2026-09-03 21:30 ` [PATCH v7 2/2] usb: dwc3: dwc3-generic-plat: Add Renesas R-Car Gen5 DWC3 xHCI USB controller glue Marek Vasut
2026-09-04 23:10 ` Thinh Nguyen
2026-09-04 15:32 ` [PATCH v7 1/2] dt-bindings: usb: dwc3: Document Renesas R-Car Gen5 DWC3 xHCI USB controller Conor Dooley
2026-09-04 16:24 ` Marek Vasut [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=7771adfd-7447-4802-ad75-7c889ad32ee7@mailbox.org \
--to=marek.vasut@mailbox.org \
--cc=Thinh.Nguyen@synopsys.com \
--cc=conor+dt@kernel.org \
--cc=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=gregkh@linuxfoundation.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=marek.vasut+renesas@mailbox.org \
--cc=robh@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®