From: "Anže Lešnik" <anze.lesnik@norik.com>
To: barebox@lists.infradead.org
Subject: Re: [RFC PATCH] usb: gadget: dfu: Rework dfu command to use usbgadget
Date: Fri, 10 Sep 2021 20:27:44 +0200 [thread overview]
Message-ID: <60a490a8-b03a-f7d3-57b3-3e9eb9300225@norik.com> (raw)
In-Reply-To: <b5415eea-946a-0e30-bb91-efd5f40fcebd@pengutronix.de>
On 10. 09. 21 10:44, Ahmad Fatoum wrote:
> Hi,
>
> On 08.09.21 14:45, Anže Lešnik wrote:
>> We have tested this patch on a PHYTEC phyCORE-i.MX6 ULL SOM running barebox 2021.04 (using the imx-usb driver) and it seems to resolve the issue. DFU transfer now works as intended.
> Great. So it's ok for Sascha to add
>
> Tested-by: Anže Lešnik <anze.lesnik@norik.com>
>
> to the commit log?
Yes. We have also tested the V2 of this patch, submitted earlier today,
and it functions correctly.
>> If one receives timeouts on the host computer, try setting usbcore.autosuspend=-1.
> Did you need this kernel parameter with the old dfu command as well?
> If only new dfu command makes this parameter necessary, we might need to look
> why the timing behavior changed.
Yes, it was also required before this patch. We have tested it with a
couple of hosts and this issue was only present on one machine.
> Cheers,
> Ahmad
>
>>
>> Anže
>>
>>
>> _______________________________________________
>> barebox mailing list
>> barebox@lists.infradead.org
>> http://lists.infradead.org/mailman/listinfo/barebox
>
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2021-09-10 18:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-30 14:48 Jules Maselbas
2021-09-08 12:45 ` Anže Lešnik
2021-09-10 8:44 ` Ahmad Fatoum
2021-09-10 18:27 ` Anže Lešnik [this message]
2021-09-10 8:46 ` Ahmad Fatoum
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=60a490a8-b03a-f7d3-57b3-3e9eb9300225@norik.com \
--to=anze.lesnik@norik.com \
--cc=barebox@lists.infradead.org \
/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