From: Mattijs Korpershoek <mkorpershoek@baylibre.com>
To: Francesco Dolcini <francesco@dolcini.it>
Cc: Marek Vasut <marex@denx.de>,
u-boot@lists.denx.de,
Alexander Sverdlin <alexander.sverdlin@siemens.com>,
Felipe Balbi <felipe.balbi@linux.intel.com>,
Lukasz Majewski <lukma@denx.de>,
Neil Armstrong <neil.armstrong@linaro.org>,
Thinh Nguyen <Thinh.Nguyen@synopsys.com>,
Tom Rini <trini@konsulko.com>
Subject: Re: [PATCH] usb: dwc3: gadget: Fix match_ep callback for NXP UUU tool
Date: Mon, 24 Mar 2025 09:26:03 +0100 [thread overview]
Message-ID: <87pli6esx0.fsf@baylibre.com> (raw)
In-Reply-To: <20250324080315.GA6932@francesco-nb>
Hi Francesco,
On lun., mars 24, 2025 at 09:03, Francesco Dolcini <francesco@dolcini.it> wrote:
> Hello Mattijs, Marek
>
> On Thu, Mar 20, 2025 at 10:47:02AM +0100, Mattijs Korpershoek wrote:
>> On mer., mars 19, 2025 at 23:07, Marek Vasut <marex@denx.de> wrote:
>>
>> > The UUU tool excepts the interrupt-in endpoint to be ep1in, otherwise
>> > it crashes. This is a result of the previous hard-coded EP setup in
>> > drivers/usb/gadget/epautoconf.c which did special-case EP allocation
>> > for SPL builds, and which was since converted to this callback, but
>> > without the special-case EP allocation in SPL part.
>> >
>> > This reinstates the SPL part in an isolated manner, only for NXP iMX
>> > SoCs, only for SPL builds, and only for the ep1in interrupt-in endpoint.
>
> UUU can (and in our case is) used also on non-NXP i.MX platforms.
> What should we do?
Do reproduce the problem (UUU tool crashes) on those platforms with
recent U-Boot versions (v2024.10+) ?
>
> Francesco
next prev parent reply other threads:[~2025-03-24 8:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-19 22:07 [PATCH] usb: dwc3: gadget: Fix match_ep callback for NXP UUU tool Marek Vasut
2025-03-20 9:47 ` Mattijs Korpershoek
2025-03-24 8:03 ` Francesco Dolcini
2025-03-24 8:26 ` Mattijs Korpershoek [this message]
2025-03-24 12:30 ` Francesco Dolcini
2025-03-24 13:53 ` Marek Vasut
2025-03-24 14:16 ` Francesco Dolcini
2025-03-24 14:36 ` Marek Vasut
2025-04-08 9:06 ` Francesco Dolcini
2025-04-08 14:51 ` Marek Vasut
2025-04-11 14:21 ` Francesco Dolcini
2025-04-13 9:14 ` Marek Vasut
2025-04-14 8:52 ` Francesco Dolcini
2025-03-24 9:20 ` Neil Armstrong
2025-03-24 13:36 ` 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=87pli6esx0.fsf@baylibre.com \
--to=mkorpershoek@baylibre.com \
--cc=Thinh.Nguyen@synopsys.com \
--cc=alexander.sverdlin@siemens.com \
--cc=felipe.balbi@linux.intel.com \
--cc=francesco@dolcini.it \
--cc=lukma@denx.de \
--cc=marex@denx.de \
--cc=neil.armstrong@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox