- 20 Jan, 2015 17 commits
-
-
Takashi Iwai authored
Both functions are used nowhere. Tested-by:
Chris Rorvick <chris@rorvick.com> Signed-off-by:
Takashi Iwai <tiwai@suse.de>
-
Takashi Iwai authored
It's used only locally. Tested-by:
-
Takashi Iwai authored
Call line6_pcm_disconnect() at disconnect to make sure that all URBs are cleared. Also reduce the superfluous snd_pcm_stop() calls from the function (and remove the unused function) since the streams are guaranteed to be stopped at this point via snd_card_disconnect(). Tested-by:
-
Takashi Iwai authored
Calling line6_pcm_disconnect() at suspend callback is superfluous and rather confusing. Let's get rid of it. Tested-by:
-
Takashi Iwai authored
Such a macro doesn't improve readability. Tested-by:
-
Takashi Iwai authored
Such a debug is needed in the core code, not in each lowlevel driver. Tested-by:
-
Takashi Iwai authored
This is rather useless for a driver that has been already merged into the official tree. Tested-by:
-
Takashi Iwai authored
This is a fairly big rewrite regarding the card resource management in line6 drivers: - The card creation is moved into line6_probe(). This adds the global destructor to private_free, so that each driver doesn't have to call it any longer. - The USB disconnect callback handles the card release, thus each driver needs to concentrate on only its own resources. No need to snd_card_*() call in the destructor. - Fix the potential stall in disconnection by removing snd_card_free(). It's replaced with snd_card_free_when_closed() for asynchronous release. - The only remaining operation for the card in each driver is the call of snd_card_register(). All the rest are dealt in the common module by itself. - These ended up with removal of audio.[ch] as a result of a reduction of one layer. Each driver just needs to call line6_probe(). Tested-by:
-
Takashi Iwai authored
The PCM trigger callback is guaranteed to be called already in spinlock / irq-disabled context. Tested-by:
-
Takashi Iwai authored
Otherwise it oopses. Tested-by:
-
Takashi Iwai authored
Kernel already shows the error in the common path. Tested-by:
-
Takashi Iwai authored
It's non-standard and rather superfluous. Tested-by:
-
Takashi Iwai authored
The line6 drivers don't support the full resume although they set SNDRV_PCM_INFO_RESUME. These flags have to be dropped to inform properly to the user-space. Also, drop the CONFIG_PM in trigger callbacks, too, which are rather superfluous. Tested-by:
-
Takashi Iwai authored
Like the previous fix for PCM, attach the card-specific resource into rawmidi->private_data instead of handling in a snd_device object. This simplifies the code and structure. Tested-by:
-
Takashi Iwai authored
Instead of handling the card-specific resource in snd_device, attach it into pcm->private_data and release it directly in private_free. This simplifies the code and structure. Tested-by:
-
Takashi Iwai authored
Instead of sysfs and the conditional build with Kconfig, implement the handling of the impulse response controls via control API, and always enable the build. Two new controls, "Impulse Response Volume" and "Impulse Response Period" are added as a replacement for the former sysfs files. Tested-by:
-
Takashi Iwai authored
Split to each individual driver for POD, PODHD, TonePort and Variax with a core LINE6 helper module. The new modules follow the standard ALSA naming rule with snd prefix: snd-usb-pod, snd-usb-podhd, snd-usb-toneport and snd-usb-variax, together with the corresponding CONFIG_SND_USB_* Kconfig items. Tested-by:
-
- 19 Jan, 2015 1 commit
-
-
Takashi Iwai authored
No functional change, refactoring with the standard helpers. Signed-off-by:
-
- 12 Jan, 2015 22 commits
-
-
Takashi Iwai authored
Promote line6 driver from staging to sound/usb/line6 directory, and maintain through sound subsystem tree. This commit just moves the code and adapts Makefile / Kconfig. The further renames and misc cleanups will follow. Signed-off-by: -
Chris Rorvick authored
Remove declarations from the header and move the definitions up in the source so they need not be forward declared. Signed-off-by:
Stefan Hajnoczi <stefanha@gmail.com> Signed-off-by:
Greg Kroah-Hartman <gregkh@linuxfoundation.org> Signed-off-by:
-
Chris Rorvick authored
Which *_disconnect() to call on disconnect is known at initialization. Add a function pointer to the `usb_line6' struct and use to call into the appropriate logic instead of evaluating the conditional logic. Signed-off-by:
-
Chris Rorvick authored
Which *_process_message() function (if any) to call when data is received is known at initialization. Add a function pointer to the `usb_line6' struct and use to call into the appropriate logic instead of evaluating the conditional logic for each message. Signed-off-by:
-
Chris Rorvick authored
Casting the `struct usb_line6' pointer at the call point makes the code difficult to read. This is substantially cleaned up by moving the cast into the callees. Signed-off-by:
-
Chris Rorvick authored
Casting the `struct usb_line6' pointer at the call point makes the code difficult to read. This is substantially cleaned up by moving the cast into the callees. Signed-off-by:
-
Chris Rorvick authored
The device type can now be used to determine the addresses of the audio endpoints for the interface. Drop the conditional logic and make these values properties. Signed-off-by:
-
Chris Rorvick authored
Commit 1027f476 (staging: line6: sync with upstream) removed PCM from the Pocket POD capabilities but left the endpoint configuration. Signed-off-by:
-
Chris Rorvick authored
The device type can now be used to determine the addresses of the control endpoints for the interface. Drop the conditional logic and make these values properties. Signed-off-by:
-
Chris Rorvick authored
The device type can now be used to determine the altsetting for the interface. Drop the conditional logic and make this value a property. Signed-off-by:
-
Chris Rorvick authored
The driver only supports interface 0 of the TonePort UX2 and POD Studio UX2 devices. Use the device table to filter on this. Signed-off-by:
-
Chris Rorvick authored
The driver only supports interface 1 of the Pocket POD. Use the device table to filter on this. Signed-off-by:
-
Chris Rorvick authored
The driver uses a different altsetting depending on the interface. Add device type entries for each of these. Signed-off-by:
-
Chris Rorvick authored
The PODxt Live device has both a POD and a Variax interface. Add device type entries for each of these. Signed-off-by:
-
Chris Rorvick authored
The `LINE6_CAP_CTRL_PCM_HW' macro combines three capabilities to save horizontal space when defining the properties entries. Now that these are no longer limited to single lines this is not such a concern. Specify capabilities individually when defining each property for better clarity. Signed-off-by:
-
Chris Rorvick authored
Specify the index of the properties entry explicitly to define this structure more robustly. Also, drop the `L6PROP' macro in favor of initializing each member explicitly on its own line since horizontal space is limited and more attributes will be added later. Signed-off-by:
-
Chris Rorvick authored
Including "BIT" in the macro name is pointless. Replace with "CAP" to provide some context for what its value represents. Signed-off-by:
-
Chris Rorvick authored
Signed-off-by:
-
Chris Rorvick authored
These are now only used to build the device table. Each entry in this table is already clearly documented as to what device it maps to so the macros become unnecessary indirection. Signed-off-by:
-
Chris Rorvick authored
The driver currently uses the device's idProduct as input to several switch statements. In some cases this is not sufficiently granular and the interface number must be taken into account. Store the device type in `usb_line6' and key off of it instead. New types can then be added that map to specific interfaces on the device so that this conditional logic can be flattened out. Signed-off-by:
-
Chris Rorvick authored
The current logic uses the index of the matched entry from the device table as an offset to the corresponding properties entry. The values of the new `line6_device_type' enum are ordered such that they can be used as an index into either of these arrays. Drop the device entry lookup logic and use the device type (via the .driver_info member) instead. Signed-off-by:
-
Chris Rorvick authored
Define an enum containing the supported devices and associate each entry in the device table to the respective value. Signed-off-by:
-
