From: Thinh Nguyen <Thinh.Nguyen@synopsys.com>
To: Elson Serrao <quic_eserrao@quicinc.com>,
Thinh Nguyen <Thinh.Nguyen@synopsys.com>,
"balbi@kernel.org" <balbi@kernel.org>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"quic_wcheng@quicinc.com" <quic_wcheng@quicinc.com>,
"quic_jackp@quicinc.com" <quic_jackp@quicinc.com>,
"quic_mrana@quicinc.com" <quic_mrana@quicinc.com>
Subject: Re: [PATCH 2/5] usb: gadget: Add function wakeup support
Date: Fri, 12 Aug 2022 02:07:06 +0000 [thread overview]
Message-ID: <5a7d8e4c-2ef3-6cc2-133e-ff38e148648d@synopsys.com> (raw)
In-Reply-To: <19a7f8da-b655-b21d-8bcb-a60e30a8d5f8@quicinc.com>
On 8/11/2022, Elson Serrao wrote:
>
>>
>> 3) If the link transitions to U0 after the device triggering a remote
>> wakeup, the device will also send device notification function wake for
>> all the interfaces armed with remote wakeup.
>>
>
> I am not clear on why device notification function wake should be sent
> for ALL interfaces armed with remote wakeup. Since function
> suspend/wakeup of an interface is independent of other functions in a
> composite device only the interface in which a remote wakeup event
> occurred should send the wake notification right? The other functions
> will continue to remain
> in function suspend state.
>
hm... I think you're right here. I think I misread the spec.
We only need to send device notification of the function that triggers
remote wake.
You can ignore the comments related to this. Sorry for the confusion.
However, the other points still stand.
Thanks,
Thinh
next prev parent reply other threads:[~2022-08-12 2:07 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-02 19:18 [PATCH 0/5] Add function suspend/resume and remote wakeup support Elson Roy Serrao
2022-08-02 19:18 ` [PATCH 1/5] usb: dwc3: Add remote wakeup handling Elson Roy Serrao
2022-08-03 0:01 ` Thinh Nguyen
2022-08-02 19:18 ` [PATCH 2/5] usb: gadget: Add function wakeup support Elson Roy Serrao
2022-08-02 23:51 ` Thinh Nguyen
2022-08-04 21:42 ` Elson Serrao
2022-08-05 1:26 ` Thinh Nguyen
2022-08-09 19:42 ` Elson Serrao
2022-08-10 1:08 ` Thinh Nguyen
2022-08-11 20:31 ` Elson Serrao
2022-08-12 2:00 ` Thinh Nguyen
2022-08-12 2:19 ` Thinh Nguyen
2022-08-13 0:46 ` Thinh Nguyen
2022-08-16 19:57 ` Elson Serrao
2022-08-16 23:51 ` Thinh Nguyen
2022-08-18 18:17 ` Elson Serrao
2022-08-18 19:41 ` Elson Serrao
2022-08-23 1:01 ` Thinh Nguyen
2022-08-23 22:06 ` Elson Serrao
2022-08-26 1:30 ` Thinh Nguyen
2022-09-13 20:13 ` Elson Serrao
2022-09-15 2:06 ` Thinh Nguyen
2022-08-11 21:03 ` Elson Serrao
2022-08-12 2:07 ` Thinh Nguyen [this message]
2022-08-02 19:18 ` [PATCH 3/5] usb: dwc3: Add function suspend and " Elson Roy Serrao
2022-08-02 23:44 ` Thinh Nguyen
2022-08-02 19:18 ` [PATCH 4/5] usb: gadget: f_ecm: Add suspend/resume and remote " Elson Roy Serrao
2022-08-02 19:18 ` [PATCH 5/5] usb: gadget: f_ecm: Add function suspend and " Elson Roy Serrao
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=5a7d8e4c-2ef3-6cc2-133e-ff38e148648d@synopsys.com \
--to=thinh.nguyen@synopsys.com \
--cc=balbi@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=quic_eserrao@quicinc.com \
--cc=quic_jackp@quicinc.com \
--cc=quic_mrana@quicinc.com \
--cc=quic_wcheng@quicinc.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