All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: Thomas Glanzmann <thomas@glanzmann.de>
Cc: Janne Grunau <j@jannau.net>, u-boot@lists.denx.de
Subject: Re: [PATCH 1/1] usb: request only 8 bytes for USB_SPEED_FULL bMaxPacketSize0 discovery
Date: Fri, 30 Sep 2022 04:54:12 +0200	[thread overview]
Message-ID: <531c5770-a4cc-1eed-f3ce-6fb7187ab406@denx.de> (raw)
In-Reply-To: <20220926073405.GC79583@glanzmann.de>

On 9/26/22 09:34, Thomas Glanzmann wrote:
> Hallo Marek,

Hi,

>> Can you be more specific about those logitech receivers ? I might have one
>> of those devices, and I have DWC3 in i.MX8MP and i.MX8MQ, as well as ZynqMP,
>> so I should be able to try and trigger the problem. Can you share the
>> reproducer test case for this problem ?
> 
> I can reproduce the issue with Keychron K1 and Realforce keyboards on the
> usb-c port of my mac mini 2020 model running u-boot. The two keyboards
> don't work without Jannes patch. With Jannes patch, they work. Other
> keyboards like my Thinkpad compact keyboard work with and without the
> patch.
> 
> https://www.keychron.com/products/keychron-k1-wireless-mechanical-keyboard
> https://www.realforcekeyboards.com
> https://www.lenovo.com/de/de/accessories-and-monitors/keyboards-and-mice/keyboards/KEYBOARD-German/p/0B47202
> 

I can also reproduce it with the logitech unifying receiver on iMX8MP 
DWC3 controller, likely close to what Russell has (046d:c52b Version 18.16).

The same device does work on iMX8MM ChipIdea USB 2.0 controller.

I wonder if this might be specific to the DWC3 controller (driver?) 
somehow ?

      reply	other threads:[~2022-09-30  2:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-29  6:31 [PATCH 1/1] usb: request only 8 bytes for USB_SPEED_FULL bMaxPacketSize0 discovery Janne Grunau
2022-08-29  7:07 ` Mark Kettenis
2022-09-25 23:52 ` Marek Vasut
2022-09-26  5:42   ` Janne Grunau
2022-09-26  7:34   ` Thomas Glanzmann
2022-09-30  2:54     ` Marek Vasut [this message]

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=531c5770-a4cc-1eed-f3ce-6fb7187ab406@denx.de \
    --to=marex@denx.de \
    --cc=j@jannau.net \
    --cc=thomas@glanzmann.de \
    --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.