Re: [linux-usb-devel] Composite device driver binding

2007-05-11 Thread [EMAIL PROTECTED]
Hi Alan, thanks a lot for your reply. Alan Stern wrote: > Your log annotations illustrate this misunderstanding. The "going down" > and "coming back" parts have nothing to do with Setup vs. Data stages. > Rather "going down" (or just S) means the message was Submitted to > usbcore, and "comin

Re: [linux-usb-devel] Composite device driver binding

2007-05-06 Thread Alan Stern
On Sat, 5 May 2007, [EMAIL PROTECTED] wrote: > Hi, > I am using a telephony device, too, and seem to have similar issues. It > is a Yealink P1K for which there is a kernel driver available. As long > as this driver is not loaded the ALSA mixer controls (volume and mute) > work fine. But as soon

Re: [linux-usb-devel] Composite device driver binding

2007-05-05 Thread [EMAIL PROTECTED]
Hi, I am using a telephony device, too, and seem to have similar issues. It is a Yealink P1K for which there is a kernel driver available. As long as this driver is not loaded the ALSA mixer controls (volume and mute) work fine. But as soon as the kernel driver (or my own userspace driver) star

Re: [linux-usb-devel] Composite device driver binding

2007-02-19 Thread David Brownell
On Friday 01 December 2006 1:58 pm, Chris Ostler wrote: > I'm writing a driver for a composite (telephony) device which has three > interfaces. Due to the design of the device, the interfaces will never be > used in isolation - you have to use all three to get any useful > functionality. When you

Re: [linux-usb-devel] Composite device driver binding

2006-12-01 Thread Alan
On Fri, 1 Dec 2006 14:58:29 -0700 Chris Ostler <[EMAIL PROTECTED]> wrote: > 2) How should the audio device nodes be created? > 3) Is there an easy way for defining the audio channels to be 'cards', and > use ALSA to do the rest of the lifting? Take a look at the existing USB audio class driver. Yo

Re: [linux-usb-devel] Composite device driver binding

2006-12-01 Thread Alan Stern
On Fri, 1 Dec 2006, Chris Ostler wrote: > I'm writing a driver for a composite (telephony) device which has three > interfaces. Due to the design of the device, the interfaces will never be > used in isolation - you have to use all three to get any useful > functionality. > > That said, there ar

[linux-usb-devel] Composite device driver binding

2006-12-01 Thread Chris Ostler
I'm writing a driver for a composite (telephony) device which has three interfaces. Due to the design of the device, the interfaces will never be used in isolation - you have to use all three to get any useful functionality. That said, there are essentially three 'channels' of communication: a bi