From: Conor Dooley <conor@kernel.org>
To: Stefan Wahren <wahrenst@gmx.net>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Florian Fainelli <florian.fainelli@broadcom.com>,
Mathias Nyman <mathias.nyman@intel.com>,
bcm-kernel-feedback-list@broadcom.com,
Cyril Brulebois <kibi@debian.org>,
linux-usb@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH V3 1/3] dt-bindings: usb: xhci: add support for BCM2711
Date: Sun, 3 Dec 2023 11:11:09 +0000 [thread overview]
Message-ID: <20231203-traffic-aide-cb03afdb3546@spud> (raw)
In-Reply-To: <20231203-chair-zen-afb8b280ca2f@spud>
[-- Attachment #1.1: Type: text/plain, Size: 2516 bytes --]
On Sun, Dec 03, 2023 at 11:06:43AM +0000, Conor Dooley wrote:
> On Sun, Dec 03, 2023 at 12:22:15AM +0100, Stefan Wahren wrote:
> > The xHCI IP on the BCM2711 SoC is compatible to "brcm,xhci-brcm-v2",
> > but also requires a power domain.
Hmm
This & the driver change makes it look like your compatible setup should
be `compatible = "brcm,bcm2711-xhci", "brcm,xhci-brcm-v2";.
If the pattern in this patch was repeated, we'd have to modify the
driver like your 2nd patch does for each and new broadcom system that
needs the power domain.
> > So introduce a new compatible
> > and the specific constraints. Since the key allOf can only occur
> > once, merge the reference below.
> >
> > Signed-off-by: Stefan Wahren <wahrenst@gmx.net>
>
> Reviewed-by: Conor Dooley <conor.dooley@microchip.com>
>
> Cheers,
> Conor.
>
> > ---
> > .../devicetree/bindings/usb/generic-xhci.yaml | 21 ++++++++++++++++---
> > 1 file changed, 18 insertions(+), 3 deletions(-)
> >
> > diff --git a/Documentation/devicetree/bindings/usb/generic-xhci.yaml b/Documentation/devicetree/bindings/usb/generic-xhci.yaml
> > index 594ebb3ee432..b6e10b0a3c24 100644
> > --- a/Documentation/devicetree/bindings/usb/generic-xhci.yaml
> > +++ b/Documentation/devicetree/bindings/usb/generic-xhci.yaml
> > @@ -9,9 +9,6 @@ title: USB xHCI Controller
> > maintainers:
> > - Mathias Nyman <mathias.nyman@intel.com>
> >
> > -allOf:
> > - - $ref: usb-xhci.yaml#
> > -
> > properties:
> > compatible:
> > oneOf:
> > @@ -28,6 +25,7 @@ properties:
> > - description: Broadcom STB SoCs with xHCI
> > enum:
> > - brcm,xhci-brcm-v2
> > + - brcm,bcm2711-xhci
> > - brcm,bcm7445-xhci
> > - description: Generic xHCI device
> > const: xhci-platform
> > @@ -49,6 +47,9 @@ properties:
> > - const: core
> > - const: reg
> >
> > + power-domains:
> > + maxItems: 1
> > +
> > unevaluatedProperties: false
> >
> > required:
> > @@ -56,6 +57,20 @@ required:
> > - reg
> > - interrupts
> >
> > +allOf:
> > + - $ref: usb-xhci.yaml#
> > + - if:
> > + properties:
> > + compatible:
> > + contains:
> > + const: brcm,bcm2711-xhci
> > + then:
> > + required:
> > + - power-domains
> > + else:
> > + properties:
> > + power-domains: false
> > +
> > examples:
> > - |
> > usb@f0931000 {
> > --
> > 2.34.1
> >
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-12-03 11:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-02 23:22 [PATCH V3 0/3] ARM: dts: bcm2711: Add BCM2711 xHCI support Stefan Wahren
2023-12-02 23:22 ` [PATCH V3 1/3] dt-bindings: usb: xhci: add support for BCM2711 Stefan Wahren
2023-12-03 11:06 ` Conor Dooley
2023-12-03 11:11 ` Conor Dooley [this message]
2023-12-03 16:56 ` Stefan Wahren
2023-12-04 17:04 ` Conor Dooley
2023-12-04 17:49 ` Florian Fainelli
2023-12-04 20:27 ` Stefan Wahren
2023-12-04 20:42 ` Conor Dooley
2023-12-02 23:22 ` [PATCH V3 2/3] usb: xhci: xhci-plat: Add " Stefan Wahren
2023-12-02 23:22 ` [PATCH V3 3/3] ARM: dts: bcm2711: Add BCM2711 xHCI support Stefan Wahren
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=20231203-traffic-aide-cb03afdb3546@spud \
--to=conor@kernel.org \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=florian.fainelli@broadcom.com \
--cc=gregkh@linuxfoundation.org \
--cc=kibi@debian.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@intel.com \
--cc=robh+dt@kernel.org \
--cc=wahrenst@gmx.net \
/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