linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 217089] xone23c mixer
Date: Tue, 28 Feb 2023 16:25:54 +0000	[thread overview]
Message-ID: <bug-217089-208809-6m6DnY55fd@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-217089-208809@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=217089

--- Comment #15 from Alan Stern (stern@rowland.harvard.edu) ---
The two usbmon traces show a big difference right near the start.  You can
check my analysis by doing:

   cat /sys/module/usbcore/parameters/old_scheme_first

under each of the kernels.  My guess is that the file contains Y in the -33
kernel and N in the -37 kernel.

That setting should not make any difference to a reasonable device.  But
apparently the Xone isn't reasonable, and it changes its behavior based on this
parameter setting.  Technically, it removes the second configuration when it is
reset a second time after being plugged in.  The -37 usbmon trace shows that
the xone reports two configs after the first reset and only one after the
second reset.  The relevant lines from the trace, right after the first reset,
are:

ffff8bfede5c8900 121253611 S Ci:1:000:0 s 80 06 0100 0000 0040 64 <
ffff8bfede5c8900 121253721 C Ci:1:000:0 0 18 = 12010002 ef020140 f0220800
00020102 0302

The 02 at the end is the number of configurations.

ffff8bfede5c8900 121253739 S Co:1:001:0 s 23 03 0004 0001 0000 0
ffff8bfede5c8900 121253750 C Co:1:001:0 0 0
ffff8bfede5c8900 121321750 S Ci:1:001:0 s a3 00 0000 0001 0004 4 <
ffff8bfede5c8900 121321766 C Ci:1:001:0 0 4 = 03051000
ffff8bfede5c8900 121321771 S Co:1:001:0 s 23 01 0014 0001 0000 0
ffff8bfede5c8900 121321786 C Co:1:001:0 0 0

Those lines are the second reset.

ffff8bfede5c8900 121401578 S Ci:1:007:0 s 80 06 0100 0000 0012 18 <
ffff8bfede5c8900 121401685 C Ci:1:007:0 0 18 = 12010002 ef020140 f0220800
00020102 0301

Here the 02 at the end has changed to 01.  The -33 trace shows only one reset,
and the number of configs doesn't change from 2 to 1.

Assuming this is true, the good news is that the parameter is something you can
easily change.  Just do (as root):

   echo Y >/sys/module/usbcore/parameters/old_scheme_first

under the -37 kernel and then see what happens when you plug in the device.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2023-02-28 16:26 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-26  9:36 [Bug 217089] New: xone23c mixer bugzilla-daemon
2023-02-26 19:15 ` [Bug 217089] " bugzilla-daemon
2023-02-26 21:33 ` bugzilla-daemon
2023-02-26 22:33 ` bugzilla-daemon
2023-02-27 10:02 ` bugzilla-daemon
2023-02-27 21:22 ` bugzilla-daemon
2023-02-27 21:23 ` bugzilla-daemon
2023-02-27 21:24 ` bugzilla-daemon
2023-02-27 21:25 ` bugzilla-daemon
2023-02-27 21:33 ` bugzilla-daemon
2023-02-28  2:13 ` bugzilla-daemon
2023-02-28 11:06 ` bugzilla-daemon
2023-02-28 11:07 ` bugzilla-daemon
2023-02-28 11:09 ` bugzilla-daemon
2023-02-28 11:13 ` bugzilla-daemon
2023-02-28 16:25 ` bugzilla-daemon [this message]
2023-02-28 16:52 ` bugzilla-daemon
2023-02-28 16:55 ` bugzilla-daemon
2023-02-28 19:35 ` bugzilla-daemon
2023-03-01  9:20 ` bugzilla-daemon
2023-03-01 15:26 ` bugzilla-daemon
2023-03-01 15:39 ` bugzilla-daemon
2023-03-01 15:55 ` bugzilla-daemon
2023-03-01 16:07 ` bugzilla-daemon
2023-03-01 20:27 ` bugzilla-daemon

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=bug-217089-208809-6m6DnY55fd@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@kernel.org \
    --cc=linux-usb@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).