public inbox for linux-sound@vger.kernel.org
 help / color / mirror / Atom feed
From: Lubomir Rintel <lkundrak@v3.sk>
To: Takashi Iwai <tiwai@suse.de>
Cc: Clemens Ladisch <clemens@ladisch.de>,
	alsa-devel@alsa-project.org, linux-sound@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] [snd-usb-audio] Add match for JMTek USB sound	card
Date: Sun, 18 Oct 2009 16:37:28 +0000	[thread overview]
Message-ID: <1255883848.2313.4.camel@localhost.localdomain> (raw)
In-Reply-To: <s5hocoddofb.wl%tiwai@suse.de>

On Mon, 2009-10-12 at 10:08 +0200, Takashi Iwai wrote:
> At Mon, 12 Oct 2009 10:03:53 +0200,
> Lubomir Rintel wrote:
> > 
> > On Mon, 2009-10-12 at 09:18 +0200, Takashi Iwai wrote:
> > > At Mon, 12 Oct 2009 08:46:26 +0200,
> > > Clemens Ladisch wrote:
> > > > 
> > > > Lubomir Rintel wrote:
> > > > > Entry for JMTek LLC., SSS USB Headphone Set in the quirk table.
> > > > 
> > > > Please add an explaination why this entry is needed.  At first glance,
> > > > this entry seems to describe a class-compliant device that should not
> > > > need a quirk.
> > > 
> > > Ah right.  It'd really helpful if Lubomir can give more details...
> > 
> > A 2.6.31.1-based kernel on my Fedora 12 workstation at hone seemed to
> > require that, only the input driver attached to the device when plugged
> > in, the snd-usb-audio didn't seem to load and did not care about the
> > device when loaded manually. I did not have an idea why, since "alias:
> > usb:v*p*d*dc*dsc*dp*ic01isc01ip*" really seemed to match my device.
> > Nevertheless, after finding out that adding an entry to the quirk table
> > solves my problem I concluded that my understanding (or lack of thereof)
> > was wrong and that alias is really not meant to match my device.
> > 
> > Now I plugged the adapter into my work lappy with 2.6.30.8-based Fedora
> > 11 and the audio interfaces on my adapter got instantly recognized and
> > claimed by snd-usb-audio (and the input interface by the input
> > subsystem), without modifying anything.
> > 
> > Any clues what could have gone wrong then?
> 
> Hm, I don't see any affecting changes between 2.6.30 and 31.
> Just as a test, could you copy sound/usb/*.[ch] from 2.6.30 tree to
> 2.6.31 or 32-rc and check whether the same problem appears?

I did not try that, but updated to a newer snapshot and it works as it
used to again, so I don't thing there's much point in finding out what
went wrong now. I'm very sorry for the noise.

Regards,
Lubo

-- 
"Excuse all the blood" -- Dead


  reply	other threads:[~2009-10-18 16:37 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-10 11:15 [PATCH] [snd-usb-audio] Add match for JMTek USB sound card Lubomir Rintel
2009-10-12  6:32 ` [alsa-devel] " Takashi Iwai
2009-10-12  6:42   ` [PATCH] " Lubomir Rintel
2009-10-12  6:46     ` Takashi Iwai
2009-10-12  6:46 ` [PATCH] [snd-usb-audio] " Clemens Ladisch
2009-10-12  7:18   ` Takashi Iwai
2009-10-12  8:03     ` Lubomir Rintel
2009-10-12  8:08       ` Takashi Iwai
2009-10-18 16:37         ` Lubomir Rintel [this message]
2009-10-30 10:29           ` 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=1255883848.2313.4.camel@localhost.localdomain \
    --to=lkundrak@v3.sk \
    --cc=alsa-devel@alsa-project.org \
    --cc=clemens@ladisch.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=tiwai@suse.de \
    /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