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>,
"balbi@kernel.org" <balbi@kernel.org>,
"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 v4 3/5] usb: gadget: Add function wakeup support
Date: Wed, 15 Feb 2023 00:55:25 +0000 [thread overview]
Message-ID: <20230215005520.7pw7xmlyi7oqgl4p@synopsys.com> (raw)
In-Reply-To: <1676316676-28377-4-git-send-email-quic_eserrao@quicinc.com>
On Mon, Feb 13, 2023, Elson Roy Serrao wrote:
> A function which is in function suspend state has to send a
> function wake notification to the host in case it needs to
> exit from this state and resume data transfer. Add support to
> handle such requests by exposing a new gadget op.
>
> Signed-off-by: Elson Roy Serrao <quic_eserrao@quicinc.com>
> ---
> drivers/usb/gadget/composite.c | 24 ++++++++++++++++++++++++
> drivers/usb/gadget/udc/core.c | 21 +++++++++++++++++++++
> include/linux/usb/composite.h | 6 ++++++
> include/linux/usb/gadget.h | 4 ++++
> 4 files changed, 55 insertions(+)
>
> diff --git a/drivers/usb/gadget/composite.c b/drivers/usb/gadget/composite.c
> index a37a8f4..51d6ee9 100644
> --- a/drivers/usb/gadget/composite.c
> +++ b/drivers/usb/gadget/composite.c
> @@ -492,6 +492,30 @@ int usb_interface_id(struct usb_configuration *config,
> }
> EXPORT_SYMBOL_GPL(usb_interface_id);
>
> +int usb_func_wakeup(struct usb_function *func)
> +{
> + int ret, id;
> +
> + if (!func->func_wakeup_armed) {
> + ERROR(func->config->cdev, "not armed for func remote wakeup\n");
> + return -EINVAL;
> + }
> +
> + for (id = 0; id < MAX_CONFIG_INTERFACES; id++)
> + if (func->config->interface[id] == func)
> + break;
> +
> + if (id == MAX_CONFIG_INTERFACES) {
> + ERROR(func->config->cdev, "Invalid function id:%d\n", id);
The print of id here is always MAX_CONFIG_INTERFACES right?
Thanks,
Thinh
> + return -EINVAL;
> + }
> +
> + ret = usb_gadget_func_wakeup(func->config->cdev->gadget, id);
> +
> + return ret;
> +}
> +EXPORT_SYMBOL_GPL(usb_func_wakeup);
> +
next prev parent reply other threads:[~2023-02-15 0:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-13 19:31 [PATCH v4 0/5] Add function suspend/resume and remote wakeup support Elson Roy Serrao
2023-02-13 19:31 ` [PATCH v4 1/5] usb: gadget: Properly configure the device for remote wakeup Elson Roy Serrao
2023-02-15 0:57 ` Thinh Nguyen
2023-02-13 19:31 ` [PATCH v4 2/5] usb: dwc3: Add remote wakeup handling Elson Roy Serrao
2023-02-15 1:09 ` Thinh Nguyen
2023-02-15 2:08 ` Elson Serrao
2023-02-13 19:31 ` [PATCH v4 3/5] usb: gadget: Add function wakeup support Elson Roy Serrao
2023-02-15 0:55 ` Thinh Nguyen [this message]
2023-02-15 2:10 ` Elson Serrao
2023-02-13 19:31 ` [PATCH v4 4/5] usb: dwc3: Add function suspend and " Elson Roy Serrao
2023-02-15 1:19 ` Thinh Nguyen
2023-02-13 19:31 ` [PATCH v4 5/5] usb: gadget: f_ecm: Add suspend/resume and remote " 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=20230215005520.7pw7xmlyi7oqgl4p@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_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