From: Mattijs Korpershoek <mkorpershoek@kernel.org>
To: Stephan Gerhold <stephan.gerhold@linaro.org>,
Lukasz Majewski <lukma@denx.de>,
Mattijs Korpershoek <mkorpershoek@kernel.org>
Cc: Marek Vasut <marex@denx.de>, Tom Rini <trini@konsulko.com>,
Loic Poulain <loic.poulain@oss.qualcomm.com>,
u-boot@lists.denx.de
Subject: Re: [PATCH 1/3] usb: gadget: f_acm: Claim requested USB endpoints
Date: Thu, 10 Apr 2025 11:58:43 +0200 [thread overview]
Message-ID: <871pu0gwx8.fsf@baylibre.com> (raw)
In-Reply-To: <20250407-acm-fixes-v1-1-e3dcb592d6d6@linaro.org>
Hi Stephan,
Thank you for the patch.
On lun., avril 07, 2025 at 16:59, Stephan Gerhold <stephan.gerhold@linaro.org> wrote:
> U-Boot has an older version of the Linux gadget API, where USB endpoints
> returned by usb_ep_autoconfig() are not automatically claimed. As written
> in the documentation comment:
>
> "To prevent the endpoint from being returned by a later autoconfig call,
> claim it by assigning ep->driver_data to some non-null value."
>
> Right now f_acm doesn't do that, which means that e.g. ep_in and ep_notify
> may end up being assigned the same endpoint. Surprisingly, the ACM console
> is still somehow working, but this is not the expected behavior. It will
> break with a later commit that disallows calling usb_ep_enable() multiple
> times.
>
> Fix this by assigning some data to ep->driver_data, similar to the other
> gadget drivers.
>
> Fixes: fc2b399ac03b ("usb: gadget: Add CDC ACM function")
> Signed-off-by: Stephan Gerhold <stephan.gerhold@linaro.org>
Reviewed-by: Mattijs Korpershoek <mkorpershoek@kernel.org>
> ---
> drivers/usb/gadget/f_acm.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/drivers/usb/gadget/f_acm.c b/drivers/usb/gadget/f_acm.c
> index f18c6a0a76110df62e925de1882316eed463b343..2665fa4168f99b35a8c595aa24cb3fc4e8ab8529 100644
> --- a/drivers/usb/gadget/f_acm.c
> +++ b/drivers/usb/gadget/f_acm.c
> @@ -238,18 +238,21 @@ static int acm_bind(struct usb_configuration *c, struct usb_function *f)
> return -ENODEV;
>
> f_acm->ep_in = ep;
> + ep->driver_data = c->cdev; /* claim */
>
> ep = usb_ep_autoconfig(gadget, &acm_fs_out_desc);
> if (!ep)
> return -ENODEV;
>
> f_acm->ep_out = ep;
> + ep->driver_data = c->cdev; /* claim */
>
> ep = usb_ep_autoconfig(gadget, &acm_fs_notify_desc);
> if (!ep)
> return -ENODEV;
>
> f_acm->ep_notify = ep;
> + ep->driver_data = c->cdev; /* claim */
>
> if (gadget_is_dualspeed(gadget)) {
> /* Assume endpoint addresses are the same for both speeds */
>
> --
> 2.47.2
next prev parent reply other threads:[~2025-04-10 9:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-07 14:59 [PATCH 0/3] usb: gadget: Fix issues when using f_acm with ci_udc Stephan Gerhold
2025-04-07 14:59 ` [PATCH 1/3] usb: gadget: f_acm: Claim requested USB endpoints Stephan Gerhold
2025-04-10 9:58 ` Mattijs Korpershoek [this message]
2025-04-07 14:59 ` [PATCH 2/3] usb: gadget: f_acm: Allow restarting ACM console after stopping it Stephan Gerhold
2025-04-10 12:16 ` Mattijs Korpershoek
2025-04-07 14:59 ` [PATCH 3/3] usb: gadget: introduce 'enabled' flag in struct usb_ep Stephan Gerhold
2025-04-10 12:19 ` Mattijs Korpershoek
2025-04-23 7:51 ` [PATCH 0/3] usb: gadget: Fix issues when using f_acm with ci_udc Mattijs Korpershoek
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=871pu0gwx8.fsf@baylibre.com \
--to=mkorpershoek@kernel.org \
--cc=loic.poulain@oss.qualcomm.com \
--cc=lukma@denx.de \
--cc=marex@denx.de \
--cc=stephan.gerhold@linaro.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.