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 1/3] dt-bindings: usb: xhci: Add optional power-domains
Date: Sun, 26 Nov 2023 11:14:12 +0000 [thread overview]
Message-ID: <20231126-tripping-kebab-0ce2ad6a3719@spud> (raw)
In-Reply-To: <20231126025612.12522-2-wahrenst@gmx.net>
[-- Attachment #1: Type: text/plain, Size: 909 bytes --]
On Sun, Nov 26, 2023 at 03:56:10AM +0100, Stefan Wahren wrote:
> BCM2711 SoC use a power domain for the xHCI. So allow supplying this
> domain in bindings.
>
> Signed-off-by: Stefan Wahren <wahrenst@gmx.net>
Acked-by: Conor Dooley <conor.dooley@microchip.com>
Cheers,
Conor.
> ---
> Documentation/devicetree/bindings/usb/generic-xhci.yaml | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/usb/generic-xhci.yaml b/Documentation/devicetree/bindings/usb/generic-xhci.yaml
> index 594ebb3ee432..e48beaff7d0d 100644
> --- a/Documentation/devicetree/bindings/usb/generic-xhci.yaml
> +++ b/Documentation/devicetree/bindings/usb/generic-xhci.yaml
> @@ -49,6 +49,9 @@ properties:
> - const: core
> - const: reg
>
> + power-domains:
> + maxItems: 1
> +
> unevaluatedProperties: false
>
> required:
> --
> 2.34.1
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-11-26 11:14 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-26 2:56 [PATCH 0/3] ARM: dts: bcm2711-rpi-cm4-io: Enable xHCI host Stefan Wahren
2023-11-26 2:56 ` [PATCH 1/3] dt-bindings: usb: xhci: Add optional power-domains Stefan Wahren
2023-11-26 11:14 ` Conor Dooley [this message]
2023-11-26 2:56 ` [PATCH 2/3] ARM: dts: bcm2711: Add generic xHCI Stefan Wahren
2023-11-26 2:56 ` [PATCH 3/3] ARM: dts: bcm2711-rpi-cm4-io: Enable xHCI host Stefan Wahren
2023-11-27 0:34 ` [PATCH 0/3] " Cyril Brulebois
2023-11-27 10:57 ` Stefan Wahren
2023-11-27 11:55 ` Cyril Brulebois
2023-11-27 12:38 ` Stefan Wahren
2023-11-27 13:02 ` Cyril Brulebois
2023-11-27 15:16 ` Stefan Wahren
2023-11-27 15:59 ` Cyril Brulebois
2023-11-27 16:56 ` Stefan Wahren
2023-11-27 18:21 ` Cyril Brulebois
2023-11-27 18:52 ` Stefan Wahren
2023-11-27 6:02 ` Justin Chen
2023-11-27 11:08 ` Stefan Wahren
2023-11-27 11:22 ` Phil Elwell
2023-11-27 11:38 ` Stefan Wahren
2023-11-27 11:58 ` Phil Elwell
2023-11-27 12:33 ` Stefan Wahren
2023-11-27 16:28 ` Phil Elwell
2023-11-27 17:44 ` Justin Chen
2023-11-27 18:41 ` Florian Fainelli
2023-11-27 19:22 ` Stefan Wahren
2023-11-27 21:49 ` Florian Fainelli
2023-11-28 6:44 ` Stefan Wahren
2023-11-28 14:46 ` Phil Elwell
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=20231126-tripping-kebab-0ce2ad6a3719@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;
as well as URLs for NNTP newsgroup(s).