devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Haotien Hsu <haotienh@nvidia.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Thierry Reding <thierry.reding@gmail.com>,
	Jonathan Hunter <jonathanh@nvidia.com>,
	Mathias Nyman <mathias.nyman@intel.com>,
	Brad Griffis <bgriffis@nvidia.com>,
	Sumit Gupta <sumitg@nvidia.com>,
	Vedant Deshpande <vedantd@nvidia.com>,
	Akhil R <akhilrajeev@nvidia.com>,
	Jinjie Ruan <ruanjinjie@huawei.com>,
	linux-usb@vger.kernel.org, devicetree@vger.kernel.org,
	linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org,
	Henry Lin <henryl@nvidia.com>, Jui Chang Kuo <jckuo@nvidia.com>,
	Wayne Chang <waynec@nvidia.com>, WK Tsai <wtsai@nvidia.com>
Subject: Re: [PATCH v2 1/4] dt-bindings: usb: Add wake-up support for Tegra234 XUSB host controller
Date: Fri, 8 Aug 2025 11:45:11 -0500	[thread overview]
Message-ID: <20250808164511.GA340427-robh@kernel.org> (raw)
In-Reply-To: <20250808065733.347264-2-haotienh@nvidia.com>

On Fri, Aug 08, 2025 at 02:57:30PM +0800, Haotien Hsu wrote:
> Populate USB wake events for Tegra234 XUSB host controller.
> These wake-up events are optional to maintain backward compatibility and
> because the USB controller does not require them for normal operation.
> 
> Signed-off-by: Haotien Hsu <haotienh@nvidia.com>
> Acked-by: Conor Dooley <conor.dooley@microchip.com>
> ---
> V1->V2
> - Add the Acked-by tag to the commit message.
> ---
>  .../bindings/usb/nvidia,tegra234-xusb.yaml    | 28 +++++++++++++++++--
>  1 file changed, 26 insertions(+), 2 deletions(-)
> 
> diff --git a/Documentation/devicetree/bindings/usb/nvidia,tegra234-xusb.yaml b/Documentation/devicetree/bindings/usb/nvidia,tegra234-xusb.yaml
> index db761dcbf72a..6365c6647cd7 100644
> --- a/Documentation/devicetree/bindings/usb/nvidia,tegra234-xusb.yaml
> +++ b/Documentation/devicetree/bindings/usb/nvidia,tegra234-xusb.yaml
> @@ -32,9 +32,32 @@ properties:
>        - const: bar2
>  
>    interrupts:
> +    minItems: 2
>      items:
>        - description: xHCI host interrupt
>        - description: mailbox interrupt
> +      - description: USB wake event 0
> +      - description: USB wake event 1
> +      - description: USB wake event 2
> +      - description: USB wake event 3
> +      - description: USB wake event 4
> +      - description: USB wake event 5
> +      - description: USB wake event 6
> +    description: |
> +      The first two interrupts are required for the USB host controller. The remaining USB wake

Wrap lines at <80 chars.

> +      event interrupts are optional. Each USB wake event is independent; it is not necessary to use
> +      all of these events on a platform. The USB host controller can function even if no wake-up
> +      events are defined. The USB wake event interrupts are handled by the Tegra PMC; hence, the
> +      interrupt controller for these is the PMC and the interrupt IDs correspond to the PMC wake
> +      event IDs. A complete list of wake event IDs is provided below, and this information is also
> +      present in the Tegra TRM document.

blank line

> +      PMC wake-up 76 for USB3 port 0 wakeup
> +      PMC wake-up 77 for USB3 port 1 wakeup
> +      PMC wake-up 78 for USB3 port 2 and port 3 wakeup
> +      PMC wake-up 79 for USB2 port 0 wakeup
> +      PMC wake-up 80 for USB2 port 1 wakeup
> +      PMC wake-up 81 for USB2 port 2 wakeup
> +      PMC wake-up 82 for USB2 port 3 wakeup

indent lists.

>  
>    clocks:
>      items:
> @@ -127,8 +150,9 @@ examples:
>                <0x03650000 0x10000>;
>          reg-names = "hcd", "fpci", "bar2";
>  
> -        interrupts = <GIC_SPI 163 IRQ_TYPE_LEVEL_HIGH>,
> -                     <GIC_SPI 164 IRQ_TYPE_LEVEL_HIGH>;
> +        interrupts-extended = <&gic GIC_SPI 163 IRQ_TYPE_LEVEL_HIGH>,
> +                              <&gic GIC_SPI 164 IRQ_TYPE_LEVEL_HIGH>,
> +                              <&pmc 76 IRQ_TYPE_LEVEL_HIGH>;
>  
>          clocks = <&bpmp TEGRA234_CLK_XUSB_CORE_HOST>,
>                   <&bpmp TEGRA234_CLK_XUSB_FALCON>,
> -- 
> 2.34.1
> 

  reply	other threads:[~2025-08-08 16:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-08  6:57 [PATCH v2 0/4] Support USB wakeup function for Tegra234 Haotien Hsu
2025-08-08  6:57 ` [PATCH v2 1/4] dt-bindings: usb: Add wake-up support for Tegra234 XUSB host controller Haotien Hsu
2025-08-08 16:45   ` Rob Herring [this message]
2025-08-08  6:57 ` [PATCH v2 2/4] arm64: tegra: Add interrupts for Tegra234 USB wake events Haotien Hsu
2025-08-08  6:57 ` [PATCH v2 3/4] soc/tegra: pmc: Add USB wake events for Tegra234 Haotien Hsu
2025-08-08  6:57 ` [PATCH v2 4/4] usb: xhci: tegra: Support USB wakeup function " Haotien Hsu

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=20250808164511.GA340427-robh@kernel.org \
    --to=robh@kernel.org \
    --cc=akhilrajeev@nvidia.com \
    --cc=bgriffis@nvidia.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=haotienh@nvidia.com \
    --cc=henryl@nvidia.com \
    --cc=jckuo@nvidia.com \
    --cc=jonathanh@nvidia.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mathias.nyman@intel.com \
    --cc=ruanjinjie@huawei.com \
    --cc=sumitg@nvidia.com \
    --cc=thierry.reding@gmail.com \
    --cc=vedantd@nvidia.com \
    --cc=waynec@nvidia.com \
    --cc=wtsai@nvidia.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;
as well as URLs for NNTP newsgroup(s).