From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: "Mehta, Piyush" <piyush.mehta@amd.com>,
"Simek, Michal" <michal.simek@amd.com>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"krzysztof.kozlowski+dt@linaro.org"
<krzysztof.kozlowski+dt@linaro.org>,
"balbi@kernel.org" <balbi@kernel.org>
Cc: "linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Paladugu,
Siva Durga Prasad" <siva.durga.prasad.paladugu@amd.com>,
Manish Narani <manish.narani@xilinx.com>
Subject: Re: [PATCH] dt-bindings: usb: dwc3: Add interrupt-names to include hibernation interrupt
Date: Fri, 23 Sep 2022 11:22:20 +0200 [thread overview]
Message-ID: <a127333d-cd25-4fa3-a12d-9c3cda05582f@linaro.org> (raw)
In-Reply-To: <MN2PR12MB4333EBFADEDD7DB623F4634188519@MN2PR12MB4333.namprd12.prod.outlook.com>
On 23/09/2022 06:38, Mehta, Piyush wrote:
>> Thanks,
>> Michal
>
> Enabling wakeup in zynqMp we need to put the core into hibernation, as versal don't have hibernation concept, but we require interrupt for wakeup.
> We have a versal platform where we are not using hibernation, but system wake up we need the interrupt. For this interrupt-name enum would be:
> - enum [host, peripheral, otg, usb-wakeup]
>
> zynqMp :
> - enum [host, peripheral, otg, hiber]
>
> Versal:
> - enum [host, peripheral, otg, usb-wakeup]
That's a different name you use now...
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-09-23 9:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-12 8:57 Piyush Mehta
2022-09-13 9:21 ` Krzysztof Kozlowski
2022-09-14 13:15 ` Mehta, Piyush
2022-09-15 8:44 ` Krzysztof Kozlowski
2022-09-15 9:04 ` Michal Simek
2022-09-16 10:10 ` Krzysztof Kozlowski
2022-09-22 11:34 ` Michal Simek
2022-09-23 4:28 ` Mehta, Piyush
2022-09-23 4:38 ` Mehta, Piyush
2022-09-23 9:22 ` Krzysztof Kozlowski [this message]
2022-09-23 9:34 ` Michal Simek
2022-09-23 12:43 ` Felipe Balbi
2022-09-23 13:25 ` Michal Simek
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=a127333d-cd25-4fa3-a12d-9c3cda05582f@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=balbi@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=manish.narani@xilinx.com \
--cc=michal.simek@amd.com \
--cc=piyush.mehta@amd.com \
--cc=robh+dt@kernel.org \
--cc=siva.durga.prasad.paladugu@amd.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
all inboxes | Powered by JetHome®