From: Warren Togami <wtogami@gmail.com>
To: "Oliver Neukum" <oneukum@suse.com>,
"Michael Laß" <bevan@bi-co.net>,
linux-usb@vger.kernel.org
Subject: Re: Cypress CDC ACM serial port not working correctly with autosuspend
Date: Wed, 7 Jun 2023 19:48:56 -0500 [thread overview]
Message-ID: <76fadf60-86cd-91d7-1594-bbbaf75bc96e@gmail.com> (raw)
In-Reply-To: <3d485cd9-e31c-20ac-e595-3000ada983fb@suse.com>
On 6/7/23 08:10, Oliver Neukum wrote:
>
>> * udev rule: ATTRS{idProduct}=="55d4", ATTRS{idVendor}=="1a86",
>> SUBSYSTEM=="usb", TEST=="power/control" ATTR{power/control}="on"
>> * usbcore.quirks=1a86:55d4:b
> [..]
>>
>> During the pandemic supply chain constraints led to some switching to
>> the CH9102F which is described here as *almost* a drop-in
>> replacement. Unfortunately the pinout differences might have
>> mattered. I am uncertain if the board design could have been better
>> but that is now in the past. Too many were mass produced so I am
>> hoping for a USB quirk to stabilize this going forward.
>>
>> I have confirmed USB_QUIRK_RESET_RESUME allows this device to
>> function for the same reason it works for the Cypress. I am uncertain
>> if a narrower new quirk "ignore the remote wakeup bit" would work
>> here. How can I test that?
>
> Please test the attached patch by giving the new 'p' quirk
> as usbcore.quirks
>
> Regards
> Oliver
Thanks! Tested your patch against 6.4.0-rc5. Both
usbcore.quirks=1a86:55d4:b and usbcore.quirks=1a86:55d4:p allow the
device to be fully functional. It even works through suspend+resume of
the host. Without the quirk the only other way for this device to
function at all is to turn off autosuspend.
How should we proceed? "p" would be the narrower quirk. Would this be
appropriate for drivers/usb/core/quirks.c?
Warren Togami
next prev parent reply other threads:[~2023-06-08 0:49 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-29 11:44 Cypress CDC ACM serial port not working correctly with autosuspend Michael Laß
2023-01-30 13:03 ` Oliver Neukum
2023-01-30 13:08 ` Oliver Neukum
2023-01-30 15:44 ` Michael Laß
2023-02-07 19:35 ` Michael Laß
2023-03-14 13:16 ` Oliver Neukum
2023-03-18 12:09 ` Michael Laß
2023-03-23 9:51 ` Oliver Neukum
2023-03-23 12:52 ` Michael Laß
2023-03-23 13:53 ` Oliver Neukum
2023-03-23 21:32 ` Michael Laß
2023-03-27 8:05 ` Oliver Neukum
2023-06-03 23:59 ` Warren Togami
2023-06-07 13:10 ` Oliver Neukum
2023-06-08 0:48 ` Warren Togami [this message]
2023-06-13 8:36 ` Oliver Neukum
2023-06-12 18:39 ` Michael Laß
2023-06-07 14:33 ` Michael Laß
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=76fadf60-86cd-91d7-1594-bbbaf75bc96e@gmail.com \
--to=wtogami@gmail.com \
--cc=bevan@bi-co.net \
--cc=linux-usb@vger.kernel.org \
--cc=oneukum@suse.com \
/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).