On 13.11.22 18:38, Thorsten Leemhuis wrote: > [Note: this mail is primarily send for documentation purposes and/or for > regzbot, my Linux kernel regression tracking bot. That's why I removed > most or all folks from the list of recipients, but left any that looked > like a mailing lists. These mails usually contain '#forregzbot' in the > subject, to make them easy to spot and filter out.] >> I'm very sad to report that this patch has caused a severe >> regression for our devices. They can no longer be powered by simply >> sticking a USB cable into their USB ports (they keep resetting >> when the tusb320 driver probes), and they reset (and keep resetting) >> if a USB cable is connected while the device is powered by other >> means. >> >> We have no connector node nor any typec-power-opmode property >> in the device tree, so the mere touching of the new registers >> happening in this patch is enough to cause the resets. >> >> The devices were fine before this patch, and reverting on top >> of a recent linus master (4bbf3422df78, from 11/11) makes the >> problem go away. > >> regzbot: introduced bf7571c00dca > > Peter, many thx for getting regzbot in the loop, there was a small typo, > let me take care of that: > > #regzbot ^introduced bf7571c00dca > #regzbot title usb: devices are not powered anymore and sometimes reset #regzbot fixed-by 341fd15e2e18c24d5c738496cfc3d7a272241201
