From: Thorsten Leemhuis <regressions@leemhuis.info>
To: linux-usb@vger.kernel.org
Cc: regressions@lists.linux.dev, Peter Rosin <peda@axentia.se>
Subject: Re: [PATCH 2/2] extcon: usbc-tusb320: Add USB TYPE-C support #forregzbot
Date: Sun, 13 Nov 2022 18:38:34 +0100 [thread overview]
Message-ID: <0d7b7d44-e2b9-9ea8-86b2-cf0f4b53eedd@leemhuis.info> (raw)
In-Reply-To: <fd0f2d56-495e-6fdd-d1e8-ff40b558101e@axentia.se>
[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.]
[reduced set or recipients, as this is only for regzbot]
On 13.11.22 17:59, Peter Rosin wrote:
> On Sat, Jul 30, 2022 at 08:05:00PM +0200, Marek Vasut wrote:
>> The TI TUSB320 seems like a better fit for USB TYPE-C subsystem,
>> which can expose details collected by the TUSB320 in a far more
>> precise way than extcon. Since there are existing users in the
>> kernel and in DT which depend on the extcon interface, keep it
>> for now.
>>
>> Add TYPE-C interface and expose the supported supply current,
>> direction and connector polarity via the TYPE-C interface.
>>
>> Signed-off-by: Marek Vasut <marex@denx.de>
>
> Hi!
>
> 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.
>
> Any suggestions?
>
> Cheers,
> Peter
>
> 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
Ciao, Thorsten
next prev parent reply other threads:[~2022-11-13 17:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-13 16:59 [PATCH 2/2] extcon: usbc-tusb320: Add USB TYPE-C support Peter Rosin
2022-11-13 17:38 ` Thorsten Leemhuis [this message]
2022-11-14 5:56 ` [PATCH 2/2] extcon: usbc-tusb320: Add USB TYPE-C support #forregzbot Thorsten Leemhuis
2022-11-13 18:48 ` [PATCH 2/2] extcon: usbc-tusb320: Add USB TYPE-C support Marek Vasut
2022-11-13 19:41 ` Peter Rosin
2022-11-13 20:47 ` Marek Vasut
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=0d7b7d44-e2b9-9ea8-86b2-cf0f4b53eedd@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=linux-usb@vger.kernel.org \
--cc=peda@axentia.se \
--cc=regressions@lists.linux.dev \
/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;
as well as URLs for NNTP newsgroup(s).