From: Thinh Nguyen <Thinh.Nguyen@synopsys.com>
To: Elson Roy Serrao <quic_eserrao@quicinc.com>
Cc: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
Thinh Nguyen <Thinh.Nguyen@synopsys.com>,
"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>
Subject: Re: [PATCH v12 6/6] usb: gadget: f_ecm: Add suspend/resume and remote wakeup support
Date: Fri, 17 Mar 2023 00:11:56 +0000 [thread overview]
Message-ID: <20230317001149.nlvcj2y3fuvq32qt@synopsys.com> (raw)
In-Reply-To: <1679009888-8239-7-git-send-email-quic_eserrao@quicinc.com>
On Thu, Mar 16, 2023, Elson Roy Serrao wrote:
> When host sends a suspend notification to the device, handle
> the suspend callbacks in the function driver. Enhanced super
> speed devices can support function suspend feature to put the
> function in suspend state. Handle function suspend callback.
>
> Depending on the remote wakeup capability the device can either
> trigger a remote wakeup or wait for the host initiated resume to
> start data transfer again.
>
> Signed-off-by: Elson Roy Serrao <quic_eserrao@quicinc.com>
> ---
> drivers/usb/gadget/function/f_ecm.c | 71 +++++++++++++++++++++++++++++++++++
> drivers/usb/gadget/function/u_ether.c | 63 +++++++++++++++++++++++++++++++
> drivers/usb/gadget/function/u_ether.h | 4 ++
> 3 files changed, 138 insertions(+)
>
> diff --git a/drivers/usb/gadget/function/f_ecm.c b/drivers/usb/gadget/function/f_ecm.c
> index a7ab30e..c43cd557 100644
> --- a/drivers/usb/gadget/function/f_ecm.c
> +++ b/drivers/usb/gadget/function/f_ecm.c
> @@ -633,6 +633,8 @@ static void ecm_disable(struct usb_function *f)
>
> usb_ep_disable(ecm->notify);
> ecm->notify->desc = NULL;
> + f->func_suspended = false;
> + f->func_wakeup_armed = false;
> }
>
> /*-------------------------------------------------------------------------*/
> @@ -885,6 +887,71 @@ static struct usb_function_instance *ecm_alloc_inst(void)
> return &opts->func_inst;
> }
>
> +static void ecm_suspend(struct usb_function *f)
> +{
> + struct f_ecm *ecm = func_to_ecm(f);
> + struct usb_composite_dev *cdev = ecm->port.func.config->cdev;
> +
> + if (f->func_suspended) {
> + DBG(cdev, "Function already suspended\n");
> + return;
> + }
> +
> + DBG(cdev, "ECM Suspend\n");
> +
> + gether_suspend(&ecm->port);
> +}
> +
> +static void ecm_resume(struct usb_function *f)
> +{
> + struct f_ecm *ecm = func_to_ecm(f);
> + struct usb_composite_dev *cdev = ecm->port.func.config->cdev;
> +
> + /*
> + * If the function is in USB3 Function Suspend state, resume is
> + * canceled. In this case resume is done by a Function Resume request.
> + */
> + if (f->func_suspended)
> + return;
> +
> + DBG(cdev, "ECM Resume\n");
> +
> + gether_resume(&ecm->port);
> +}
> +
> +static int ecm_get_status(struct usb_function *f)
> +{
> + struct usb_configuration *c = f->config;
> +
> + /* D0 and D1 bit set to 0 if device is not wakeup capable */
> + if (!(USB_CONFIG_ATT_WAKEUP & c->bmAttributes))
> + return 0;
> +
> + return (f->func_wakeup_armed ? USB_INTRF_STAT_FUNC_RW : 0) |
> + USB_INTRF_STAT_FUNC_RW_CAP;
> +}
Why do we need to implement ecm_get_status if it's already handled in
composite.c now?
> +
> +static int ecm_func_suspend(struct usb_function *f, u8 options)
> +{
> + struct usb_composite_dev *cdev = f->config->cdev;
> +
> + DBG(cdev, "func susp %u cmd\n", options);
> +
> + if (options & (USB_INTRF_FUNC_SUSPEND_LP >> 8)) {
This feature selector doesn't indicate whether it's SetFeature or
ClearFeature request. ecm_func_suspend is supposed to be for
SetFeature(suspend) only. Perhaps we may have to define func_resume()
for ClearFeature(suspend)?
Thanks,
Thinh
> + if (!f->func_suspended) {
> + ecm_suspend(f);
> + f->func_suspended = true;
> + }
> + } else {
> + if (f->func_suspended) {
> + f->func_suspended = false;
> + ecm_resume(f);
> + }
> + }
> +
> + return 0;
> +}
> +
next prev parent reply other threads:[~2023-03-17 0:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-16 23:38 [PATCH v12 0/6] Add function suspend/resume and remote wakeup support Elson Roy Serrao
2023-03-16 23:38 ` [PATCH v12 1/6] usb: gadget: Properly configure the device for remote wakeup Elson Roy Serrao
2023-03-16 23:38 ` [PATCH v12 2/6] usb: dwc3: Add remote wakeup handling Elson Roy Serrao
2023-03-16 23:38 ` [PATCH v12 3/6] usb: gadget: Add function wakeup support Elson Roy Serrao
2023-03-16 23:38 ` [PATCH v12 4/6] usb: dwc3: Add function suspend and " Elson Roy Serrao
2023-03-16 23:38 ` [PATCH v12 5/6] usb: gadget: arm the function for triggering remote wakeup Elson Roy Serrao
2023-03-16 23:38 ` [PATCH v12 6/6] usb: gadget: f_ecm: Add suspend/resume and remote wakeup support Elson Roy Serrao
2023-03-17 0:11 ` Thinh Nguyen [this message]
2023-03-17 17:59 ` Elson Serrao
2023-03-17 21:28 ` Thinh Nguyen
2023-03-17 23:20 ` Thinh Nguyen
2023-03-18 0:23 ` Elson Serrao
2023-03-18 2:26 ` Thinh Nguyen
2023-03-20 17:42 ` Elson Serrao
2023-03-24 0:12 ` Elson Serrao
2023-03-24 0:59 ` Thinh Nguyen
2023-03-24 1:14 ` Thinh Nguyen
2023-03-21 8:12 ` Dan Carpenter
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=20230317001149.nlvcj2y3fuvq32qt@synopsys.com \
--to=thinh.nguyen@synopsys.com \
--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_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;
as well as URLs for NNTP newsgroup(s).