From: Rob Herring <robh@kernel.org>
To: Peter Chen <peter.chen@nxp.com>
Cc: devicetree@vger.kernel.org, linux-usb@vger.kernel.org,
linux-imx@nxp.com, pawell@cadence.com, rogerq@ti.com,
jun.li@nxp.com
Subject: Re: [PATCH 6/6] doc: dt-binding: cdns,usb3: add wakeup-irq
Date: Fri, 30 Oct 2020 10:22:17 -0500 [thread overview]
Message-ID: <20201030152217.GA3866290@bogus> (raw)
In-Reply-To: <20201022014411.2343-1-peter.chen@nxp.com>
On Thu, Oct 22, 2020 at 09:44:11AM +0800, Peter Chen wrote:
> To support low power mode for controller, the driver needs wakeup-irq
> to reflect the signal changing after controller is stopped, and waking
> the controller up accordingly.
>
> Signed-off-by: Peter Chen <peter.chen@nxp.com>
> ---
> Documentation/devicetree/bindings/usb/cdns,usb3.yaml | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/usb/cdns,usb3.yaml b/Documentation/devicetree/bindings/usb/cdns,usb3.yaml
> index ac20b98e9910..0171e64ef95e 100644
> --- a/Documentation/devicetree/bindings/usb/cdns,usb3.yaml
> +++ b/Documentation/devicetree/bindings/usb/cdns,usb3.yaml
> @@ -30,12 +30,15 @@ properties:
> - description: OTG/DRD controller interrupt
> - description: XHCI host controller interrupt
> - description: Device controller interrupt
> + - description: interrupt used to wake up core, eg: when usbcmd.rs is
> + cleared by xhci core, this interrupt is optional.
You need 'minItems: 3' here and below to make this optional. I guess we
don't have an example for this binding or it would fail.
>
> interrupt-names:
> items:
> - const: host
> - const: peripheral
> - const: otg
> + - const: wakeup
>
> dr_mode:
> enum: [host, otg, peripheral]
> --
> 2.17.1
>
next prev parent reply other threads:[~2020-10-30 15:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-22 1:44 [PATCH 6/6] doc: dt-binding: cdns,usb3: add wakeup-irq Peter Chen
2020-10-30 15:22 ` Rob Herring [this message]
2020-10-30 23:10 ` Peter Chen
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=20201030152217.GA3866290@bogus \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jun.li@nxp.com \
--cc=linux-imx@nxp.com \
--cc=linux-usb@vger.kernel.org \
--cc=pawell@cadence.com \
--cc=peter.chen@nxp.com \
--cc=rogerq@ti.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).