[alsa-devel] [PATCH 1/1] Added functionality for E-mu 0404USB/0202USB/TrackerPre

[James Courtier-Dutton]

2009/12/22 Zerg Cannibal <cnb_zerg at yahoo.com>:
> Added functionality:
> 1) Extension Units support (all XU settings now available at alsamixer, kmix, etc):
>  - "AnalogueIn soft limiter" switch;
>  - "Sample rate" selector (values 0,1,2,3,4,5 corresponds to 44.1 48 ... 192 kHz);
>  - "DigitalIn CLK source" selector (internal/external) (**);
>  - "DigitalOut format SPDIF/AC3" switch (**);
> (**)E-mu-0404usb only.
>
> 2) Automatic device sample rate adjustment depending on substream samplerate for both capture and playback substream.
>
> Patch is based on Mac OS-X driver (http://sourceforge.net/projects/zaudiodrivermac/) and successfully tested by Ubuntu community users for 0404usb and 0202usb.

Further info for set_format_emu_quirk()

The values of XU_CR_SELECTOR_CONTROL can be:
0 = 44100
1 = 48000
2 = 88200
3 = 96000
4 = 176400
5 = 192000


USB_XU_CLOCK_RATE has a number of controls
00: Does nothing.
01: Does nothing
02: Query supported sample rates: Bitmap
03: XU_CR_SELECTOR_CONTROL: as above.

USB_XU_CLOCK_SOURCE has a number of controls:
00: Does nothing
01: Does nothing
02: USB_XU_CLOCK_SOURCE_SELECTOR_CONTROL: = 1 for External from
SPDIF-IN, 0 = Internal.

USB_XU_DIGITAL_IO has a number of controls:
00: Does nothing
01: Does nothing
02: XU_DIGITAL_IO_SAMPLE_RATE_CONTROL: spdif input sample rate. GET
only. 32bit value.
03: XU_DIGITAL_IO_SYNC_SOURCE_LOCK_STATUS: "Lock indicator". GET only
1=Locked. 0=no-lock.
04: Does nothing
05: XU_DIGITAL_IO_OUTPUT_FRAME_FORMAT: 0 = undefined, 1 = Consumer,
Copyright OFF, 2 = Consumer, Copyright ON, 3 = Professional.

USB_XU_DEVICE_OPTIONS has a number of controls:
00: Does nothing
01: Does nothing
02: Does nothing
03: XU_DO_SOFT_LIMIT_CONTROL: GET/SET: 1 = Soft limit ON, 0 = Soft limit OFF.

I have no info regarding 0xe305 or 0xe306.
I have firmware upgrade details and firmware version querying details
and usb speed query details, if one needs them.

The above info might only apply to an older version of the firmware,
so the driver might have to behave differently depending on the
installed firmware version.

Kind Regards

James