Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Daniel Mack <daniel@zonque.org>
Cc: alsa-devel@alsa-project.org,
	Dr Nicholas J Bailey <nicholas.bailey@glasgow.ac.uk>
Subject: Re: usb-usx2y: playback fails with Tascam US122 on kernel 3.14
Date: Fri, 08 Aug 2014 08:13:38 +0200	[thread overview]
Message-ID: <s5hfvh7mru5.wl%tiwai@suse.de> (raw)
In-Reply-To: <53E2639A.4070506@zonque.org>

At Wed, 06 Aug 2014 19:19:22 +0200,
Daniel Mack wrote:
> 
> On 08/06/2014 06:43 PM, Dr Nicholas J Bailey wrote:
> > On Thursday 26 June 2014 15:51:54 Dr Nicholas J Bailey wrote:
> >> I am having trouble with the US122 in playback and duplex mode. In capture
> >> mode, it is working.
> >>
> >> This problem occurs on (at least)
> >> Linux arial 3.14-1-686-pae #1 SMP Debian 3.14.7-1 (2014-06-16) i686
> >> GNU/Linux
> >>
> > Further information:
> > 
> > Using this kernel:
> > 
> > Linux arial 3.14-2-686-pae #1 SMP Debian 3.14.13-2 (2014-07-24) i686 GNU/Linux
> > 
> > trying to use the US-122 Tascam box results in the following showing up in 
> > dmesg. I have unplugged and reconnected the box twice to get the LEDs to light 
> > up. This has been the normal behaviour for as long as I can remember. You can 
> > only use the Tascam as capture device on this kernel.
> > 
> > Using this kernel:
> > 
> > Linux arial 3.10.11 #1 SMP Wed Oct 2 19:26:59 BST 2013 i686 GNU/Linux
> > 
> > the US-122 works fine for simultaneous capture and playback.
> > 
> > I've looked at the difference in the source code between 3.10 and 4.14 and 
> > there is very little in the usb-usx2y alsa module. Is there some midi-related 
> > change I should know about?
> 
> This driver is unfortunately poorly supported by the community. Very few
> people have such a device, the driver has ample areas it needs cleanups
> in, and the original author is unfortunately unresponsive.
> 
> The best thing you can do is probably bisect the issue:
> 
>   https://wiki.ubuntu.com/Kernel/KernelBisection

Right.  My guess is rather the changes in USB driver side.
So, better to bisect in the full path, not limited to sound/*.


Takashi

> > I understand that the US-122 is a usb-1.1 device and I have the ehci module 
> > loaded, but it was there too with the older kernel and that worked fine.
> 
> Yes, that shouldn't be an issue. Let us know what the bisection tells you.
> 
> 
> Daniel
> 
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@alsa-project.org
> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
> 

  reply	other threads:[~2014-08-08  6:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-26 14:51 usb-usx2y: playback fails with Tascam US122 on kernel 3.14 Dr Nicholas J Bailey
2014-08-06 16:43 ` Dr Nicholas J Bailey
2014-08-06 16:45   ` Dr Nicholas J Bailey
2014-08-06 17:19   ` Daniel Mack
2014-08-08  6:13     ` Takashi Iwai [this message]
2014-08-20 17:50     ` Dr Nicholas J Bailey
2014-08-21  7:02       ` Takashi Iwai
2014-08-21 16:14         ` Dr Nicholas J Bailey
2014-08-21 16:16           ` Takashi Iwai

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=s5hfvh7mru5.wl%tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=daniel@zonque.org \
    --cc=nicholas.bailey@glasgow.ac.uk \
    /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