January 2011 - Alsa-devel - mailman.alsa-project.org

[alsa-devel] hda : computer using EAPD as external amplifier controller
by Anisse Astier 06 Mar '11

06 Mar '11

Hi, I have this computer, with an integrated speaker. It's using an ALC662, see attached alsa-info output. By default, speaker doesn't work. Now, after playing a bit with hda-analyzer, I figured that output PIN 0x14 has EAPD enabled, which is the default way of doing things in auto configure mode. But disabling EAPD on this PIN makes speaker work. See second alsa-info attached. Is it necessary to write a full blown quirk just to modify this parameter? From what I've seen in patch_realtek, it seems we need to write the whole config for the device when adding a quirk: we can't rely on auto configuration and then put a small quirk on top of that. Am I right ? Regards, Anisse

4 6

[alsa-devel] idt STAC927x adat supported (sigmatel HDA codec) ?
by Eric 03 Mar '11

03 Mar '11

Is the ADAT output of the IDT (sigmatel) STAC927x HDA codec supported in alsa ? If not could someone please try to add this incredibly nice feature in the existing alsa driver ? Thank you very much

4 13

[alsa-devel] [PATCH v2 00/13] OMAP: McBSP: hwmod adaptation and runtime conversion
by Kishon Vijay Abraham I 18 Feb '11

18 Feb '11

Modify OMAP McBSP driver to use omap hwmod framework and pm runtime APIs. Created on top of linux OMAP master (linux-omap-2.6 :master) Did digital loopback testing on OMAP4430, OMAP3430 and OMAP2430 SDP boards. Verified that this patch series does not break the OMAP1 build. Patch series modifies audio layer and hence would appreciate the help of some audio guy to test this series. Patch series requires the following patch to be present http://permalink.gmane.org/gmane.linux.ports.arm.omap/51132 http://permalink.gmane.org/gmane.linux.ports.arm.omap/51133 http://permalink.gmane.org/gmane.linux.ports.arm.omap/51134 V2: * Added omap_hwmod_lookup() in the callback to omap_hwmod_for_each_by_class() to obtain hwmod data for sidetone. Previously this nesting of hwmod APIs was prevented by the use of mutex. * Added a revision member in hwmod database inorder to facilitate the driver to differentiate between different OMAP. * Created APIs to pass DMA params from McBSP driver to client drivers * Cleaned up sound soc by removing the use of macros to obtain base address and DMA channel number and instead use APIs exposed by the driver. * Removed macros defined in mcbsp driver for data that is obtained from hwmod database V1: * McBSP is designed to use multiple hwmods for a single device when the McBSP device has sidetone feature. * To avoid funcionality break of OMAP1 McBSP in between the series and to keep the patches readable, implementation was done in two steps: - First modify mcbsp driver to use platform_get* APIs - then convert it to use hwmod framework for OMAP2+. * API's like omap_device_noidle() and omap_device_default_idle() is used to change the SYCONFIG register bits. This change is done to align with the discussion on [2] * Use '.rev' of omap_hwmod class to identify OMAP3 specific settings * Use *ST_* macros for idlest_idle bit * Incorporate other general review comments provided for hwmod adpatation of other OMAP driver's (eg., do pdata free after a omap_device_build()) * Retain fclk even after pm_runtime adaptation to facilitate switching of functional clock from one source to another * Add member 'name' to omap_hwmod_addr_space struct so that the driver need not rely on the order to get the proper resource [3]. Discussions related to the first RFC patch can be found at [1] [1]: http://www.mail-archive.com/linux-omap@vger.kernel.org/msg36743.html [2]: http://www.mail-archive.com/linux-omap@vger.kernel.org/msg39615.html [3]: https://patchwork.kernel.org/patch/233211/ Benoit Cousson (1): OMAP4: hwmod data: Add McBSP Charulatha V (3): OMAP2420: hwmod data: Add McBSP OMAP2430: hwmod data: Add McBSP OMAP3: hwmod data: Add McBSP Kishon Vijay Abraham I (9): OMAP: hwmod: Add member 'name' to omap_hwmod_addr_space struct OMAP: McBSP: Convert McBSP to platform device model OMAP3: hwmod: add dev_attr for McBSP sidetone OMAP2+: McBSP: hwmod adaptation for McBSP OMAP: McBSP: use omap_device APIs to modify SYSCONFIG OMAP: McBSP: Add pm runtime support OMAP: McBSP: APIs to pass DMA params from McBSP driver to client drivers ASoC: McBSP: get hw params from McBSP driver OMAP: hwmod: Removal of macros for data that is obtained from hwmod database arch/arm/mach-omap1/mcbsp.c | 383 +++++++++++++++---- arch/arm/mach-omap2/mcbsp.c | 228 +++--------- arch/arm/mach-omap2/omap_hwmod.c | 1 + arch/arm/mach-omap2/omap_hwmod_2420_data.c | 167 ++++++++ arch/arm/mach-omap2/omap_hwmod_2430_data.c | 417 ++++++++++++++++++++ arch/arm/mach-omap2/omap_hwmod_3xxx_data.c | 544 ++++++++++++++++++++++++++ arch/arm/mach-omap2/omap_hwmod_44xx_data.c | 321 +++++++++++++++ arch/arm/mach-omap2/prcm-common.h | 4 + arch/arm/plat-omap/devices.c | 10 +- arch/arm/plat-omap/include/plat/mcbsp.h | 69 +--- arch/arm/plat-omap/include/plat/omap_hwmod.h | 4 +- arch/arm/plat-omap/mcbsp.c | 207 +++++++--- sound/soc/omap/omap-mcbsp.c | 126 +------ 13 files changed, 2006 insertions(+), 475 deletions(-)

9 38

[alsa-devel] Channel swapping problem on Atmel SSC audio
by Ryan Mallon 18 Feb '11

18 Feb '11

Hi all, I'm working on a custom board using the AT91SAM9G45 processor and a TLV320AIC26 SPI attached audio codec using I2S format audio. When doing audio playback on the board the left and right channels are occasionally flipped. I have verified this by generating a custom wav file which has constant data on one channel and an incrementing counter on the other channel. The digitial out from the CPU shows that no data is being lost, but around 1/5 times the audio channels will be flipped. The problem appears to be that the DMA is starting on the wrong edge of the LRCLK. I have using both SND_SOC_DAIFMT_CBM_CFM (Codec provides clocks) and SND_SOC_DAIFMT_CBS_CFS (CPU provides clocks) but the problem occurs in both situations. I have also tried changing TCMR:CKO to SSC_CKO_TRANSFER and TCMR:START to SSC_START_LOW_RF, but the problem still occurs. I have looked through the PCM/SSC DMA code and cannot find any obvious bugs. I have checked the errata for the At91SAM9G45 processor (our chip marking is CU-1004-A), but can't find anything which relates directly to the problem we are seeing. Has anybody else had this problem, or does anybody have any AT91/Atmel hardware that they could test to see if it occurs on other hardware also? Thanks, ~Ryan -- Bluewater Systems Ltd - ARM Technology Solution Centre Ryan Mallon 5 Amuri Park, 404 Barbadoes St ryan(a)bluewatersys.com PO Box 13 889, Christchurch 8013 http://www.bluewatersys.com New Zealand Phone: +64 3 3779127 Freecall: Australia 1800 148 751 Fax: +64 3 3779135 USA 1800 261 2934

6 6

[alsa-devel] [PATCH v3 0/4] Adding OMAP DMIC driver to kernel
by David Lambert 14 Feb '11

14 Feb '11

This is a patch series to add the OMAP Digital Microphone driver for OMAP4. It includes the driver, a generic DMIC codec, platform devices, as well as HWMOD entries for OMAP44xx chipsets. Note: The DMIC codec driver was removed from this series as it was accepted for and merged for the 2.6.38 kernel. Benoit Cousson (1): OMAP4: hwmod: add entries for DMIC driver David Lambert (3): ASoC: DMIC: Adding the OMAP DMIC driver OMAP4: DMIC: initializes the DMIC driver OMAP4: DMIC: Add DMIC codec platform devices arch/arm/mach-omap2/board-4430sdp.c | 11 + arch/arm/mach-omap2/omap_hwmod_44xx_data.c | 91 +++++ arch/arm/plat-omap/devices.c | 35 ++ arch/arm/plat-omap/include/plat/dmic.h | 82 +++++ sound/soc/omap/Kconfig | 3 + sound/soc/omap/Makefile | 2 + sound/soc/omap/omap-dmic.c | 534 ++++++++++++++++++++++++++++ 7 files changed, 758 insertions(+), 0 deletions(-) create mode 100644 arch/arm/plat-omap/include/plat/dmic.h create mode 100644 sound/soc/omap/omap-dmic.c

6 12

[alsa-devel] [PATCH - snd-usb-audio 1/1] Support for Power/Status LED on Creative USB X-Fi S51
by emailmandar＠gmail.com 13 Feb '11

13 Feb '11

From: Mandar Joshi <emailmandar(a)gmail.com> This patch adds support for Power/Status LED on Creative USB X-Fi S51. There is just one LED on the device. The LED can either be On or it can be set to Blink. There doesn't seem to be a way to switch it off. The control message to change LED status is similar to that of audigy2nx except that the index is to be set to 0 and value is 1 for Blink and 0 for On. The 'Power LED' control in alsamixer when muted will cause the LED to Blink continuously. When unmuted the LED will stay On. The Creative driver under Windows sets the LED to blink whenever audio is muted. This LED can be treated as the CMSS LED but I figured since there is just one LED, it should be treated as the Power LED. Is that alright? I've also changed the comment "Usb X-Fi" to "Usb X-Fi S51" as there are other external X-Fi devices from Creative like Usb X-Fi Go and Xmod. The volume knob and LED support patch doesn't apply to them. Signed-off-by: Mandar Joshi <emailmandar(a)gmail.com> diff --git a/sound/usb/mixer_quirks.c b/sound/usb/mixer_quirks.c index e7df1e5..aea92d6 100644 --- a/sound/usb/mixer_quirks.c +++ b/sound/usb/mixer_quirks.c @@ -60,6 +60,7 @@ static const struct rc_config { { USB_ID(0x041e, 0x3000), 0, 1, 2, 1, 18, 0x0013 }, /* Extigy */ { USB_ID(0x041e, 0x3020), 2, 1, 6, 6, 18, 0x0013 }, /* Audigy 2 NX */ { USB_ID(0x041e, 0x3040), 2, 2, 6, 6, 2, 0x6e91 }, /* Live! 24-bit */ + { USB_ID(0x041e, 0x3042), 0, 1, 1, 1, 1, 0x000d }, /* Usb X-Fi S51 */ { USB_ID(0x041e, 0x3048), 2, 2, 6, 6, 2, 0x6e91 }, /* Toshiba SB0500 */ }; @@ -182,10 +183,16 @@ static int snd_audigy2nx_led_put(struct snd_kcontrol *kcontrol, struct snd_ctl_e if (value > 1) return -EINVAL; changed = value != mixer->audigy2nx_leds[index]; - err = snd_usb_ctl_msg(mixer->chip->dev, - usb_sndctrlpipe(mixer->chip->dev, 0), 0x24, - USB_DIR_OUT | USB_TYPE_VENDOR | USB_RECIP_OTHER, - value, index + 2, NULL, 0, 100); + if (mixer->chip->usb_id == USB_ID(0x041e, 0x3042)) + err = snd_usb_ctl_msg(mixer->chip->dev, + usb_sndctrlpipe(mixer->chip->dev, 0), 0x24, + USB_DIR_OUT | USB_TYPE_VENDOR | USB_RECIP_OTHER, + !value, 0, NULL, 0, 100); + else + err = snd_usb_ctl_msg(mixer->chip->dev, + usb_sndctrlpipe(mixer->chip->dev, 0), 0x24, + USB_DIR_OUT | USB_TYPE_VENDOR | USB_RECIP_OTHER, + value, index + 2, NULL, 0, 100); if (err < 0) return err; mixer->audigy2nx_leds[index] = value; @@ -224,8 +231,12 @@ static int snd_audigy2nx_controls_create(struct usb_mixer_interface *mixer) int i, err; for (i = 0; i < ARRAY_SIZE(snd_audigy2nx_controls); ++i) { + /* USB X-Fi S51 doesn't have a CMSS LED */ + if ((mixer->chip->usb_id == USB_ID(0x041e, 0x3042)) && i == 0) + continue; if (i > 1 && /* Live24ext has 2 LEDs only */ (mixer->chip->usb_id == USB_ID(0x041e, 0x3040) || + mixer->chip->usb_id == USB_ID(0x041e, 0x3042) || mixer->chip->usb_id == USB_ID(0x041e, 0x3048))) break; err = snd_ctl_add(mixer->chip->card, @@ -364,6 +375,7 @@ int snd_usb_mixer_apply_create_quirk(struct usb_mixer_interface *mixer) if (mixer->chip->usb_id == USB_ID(0x041e, 0x3020) || mixer->chip->usb_id == USB_ID(0x041e, 0x3040) || + mixer->chip->usb_id == USB_ID(0x041e, 0x3042) || mixer->chip->usb_id == USB_ID(0x041e, 0x3048)) { if ((err = snd_audigy2nx_controls_create(mixer)) < 0) return err; -- 1.7.1

4 5

[alsa-devel] finally, ALSA 1.0.24 is out
by Jaroslav Kysela 11 Feb '11

11 Feb '11

Hello all, after very intensive testing, I released all ALSA packages with version number 1.0.24(+) : * alsa-driver-1.0.24 * alsa-lib-1.0.24.1 * alsa-utils-1.0.24.2 * alsa-tools-1.0.24 * alsa-firmware-1.0.24 * alsa-plugins-1.0.24 * pyalsa-1.0.24 The full list of changes is here: http://www.alsa-project.org/main/index.php/Changes_v1.0.23_v1.0.24 There is a ton of work in these parts (among others): * alsa-driver - HDA driver - ASoC tree - USB driver * alsa-library - Use Case Manager * alsa-utils - alsaloop and alsaucm introduction - alsactl improvements * alsa-tools - updated hdspmixer Please, report compilation problems directly to me or to the alsa-devel mailing list. Enjoy this release, Jaroslav ----- Jaroslav Kysela <perex(a)perex.cz> Linux Kernel Sound Maintainer ALSA Project, Red Hat, Inc.

6 7

[alsa-devel] [PATCH v8 00/12] Media controller (core and V4L2)
by Laurent Pinchart 08 Feb '11

08 Feb '11

Hi everybody, Here is the eighth version of the media controller core and V4L2 patches. Quick reminder for those who missed the previous version. let me quote the documentation (Documentation/DocBook/v4l/media-controller.xml). "Discovering a [media] device internal topology, and configuring it at runtime, is one of the goals of the media controller API. To achieve this, hardware devices are modelled as an oriented graph of building blocks called entities connected through pads." The code has been extensively reviewed by the V4L community, and this version is the first one to incorporate comments from the ALSA community (big thanks to Mark Brown and Clemens Ladisch). Two issues are not fully addressed yet, namely power management (I need to discuss this some more with the ALSA developers to really understand their requirements) and entities type names. I'm still posting this for review, as other developers have showed interest in commenting on the code. I want to emphasize once again that the media controller API does not replace the V4L, DVB or ALSA APIs. It complements them. The first user of the media controller API is the OMAP3 ISP driver. You can find it (as well as these patches and other V4L-specific patches) in a git tree at http://git.linuxtv.org/pinchartl/media.git (media-0005-omap3isp branch). The OMAP3 ISP driver patches are regularly posted for review on the linux-media list. Laurent Pinchart (11): media: Media device node support media: Media device media: Entities, pads and links media: Entity use count media: Media device information query media: Entities, pads and links enumeration media: Links setup media: Pipelines and media streams v4l: Add a media_device pointer to the v4l2_device structure v4l: Make video_device inherit from media_entity v4l: Make v4l2_subdev inherit from media_entity Sakari Ailus (1): media: Entity graph traversal Documentation/ABI/testing/sysfs-bus-media | 6 + Documentation/DocBook/media-entities.tmpl | 24 + Documentation/DocBook/media.tmpl | 3 + Documentation/DocBook/v4l/media-controller.xml | 89 ++++ Documentation/DocBook/v4l/media-func-close.xml | 59 +++ Documentation/DocBook/v4l/media-func-ioctl.xml | 116 +++++ Documentation/DocBook/v4l/media-func-open.xml | 94 ++++ .../DocBook/v4l/media-ioc-device-info.xml | 133 +++++ .../DocBook/v4l/media-ioc-enum-entities.xml | 308 +++++++++++ Documentation/DocBook/v4l/media-ioc-enum-links.xml | 207 ++++++++ Documentation/DocBook/v4l/media-ioc-setup-link.xml | 93 ++++ Documentation/media-framework.txt | 353 +++++++++++++ Documentation/video4linux/v4l2-framework.txt | 72 +++- drivers/media/Kconfig | 13 + drivers/media/Makefile | 10 +- drivers/media/media-device.c | 382 ++++++++++++++ drivers/media/media-devnode.c | 321 ++++++++++++ drivers/media/media-entity.c | 536 ++++++++++++++++++++ drivers/media/video/v4l2-dev.c | 49 ++- drivers/media/video/v4l2-device.c | 52 ++- drivers/media/video/v4l2-subdev.c | 41 ++- include/linux/Kbuild | 1 + include/linux/media.h | 132 +++++ include/media/media-device.h | 95 ++++ include/media/media-devnode.h | 97 ++++ include/media/media-entity.h | 147 ++++++ include/media/v4l2-dev.h | 7 + include/media/v4l2-device.h | 4 + include/media/v4l2-subdev.h | 10 + 29 files changed, 3428 insertions(+), 26 deletions(-) create mode 100644 Documentation/ABI/testing/sysfs-bus-media create mode 100644 Documentation/DocBook/v4l/media-controller.xml create mode 100644 Documentation/DocBook/v4l/media-func-close.xml create mode 100644 Documentation/DocBook/v4l/media-func-ioctl.xml create mode 100644 Documentation/DocBook/v4l/media-func-open.xml create mode 100644 Documentation/DocBook/v4l/media-ioc-device-info.xml create mode 100644 Documentation/DocBook/v4l/media-ioc-enum-entities.xml create mode 100644 Documentation/DocBook/v4l/media-ioc-enum-links.xml create mode 100644 Documentation/DocBook/v4l/media-ioc-setup-link.xml create mode 100644 Documentation/media-framework.txt create mode 100644 drivers/media/media-device.c create mode 100644 drivers/media/media-devnode.c create mode 100644 drivers/media/media-entity.c create mode 100644 include/linux/media.h create mode 100644 include/media/media-device.h create mode 100644 include/media/media-devnode.h create mode 100644 include/media/media-entity.h -- Regards, Laurent Pinchart

4 18

[alsa-devel] Conexant 5069: internal speakers are not muted when headphones are plugged in
by Paul Menzel 07 Feb '11

07 Feb '11

Dear ALSA folks, I encounter a problem with a Lenovo G555 where the internal speakers are not muted when headphones are plugged in. Ubuntu 10.10 with Linux 2.6.35 [1] runs the Lenovo, but this seems to be a common problem [2][3]. I tried to load the module with `model=lenovo`, but the only result was, that the external speakers did not work at all. Do you have another idea what to use for the `model`? The system has to rebooted every time, since I cannot unload the module using sudo modprobe -r snd-hda-intel or sudo rmmod snd-hda-intel since it seems to be in use by the system. Seems like I missed `model=thinkpad` in [3]. But I do not have access to the system right now, so I am sending this report anyway. Please find attached the output of `alsa-info.sh` with the default behavior (headphones work, but internal ones are not muted) and with `model=lenovo` (headphones do not work). David, do you know if your recent patches sent to this list [PATCH 2/2] ALSA: HDA: Add a new model "asus" for Conexant 5066/205xx [5] [PATCH] ALSA: HDA: Add Lenovo vendor quirk for Conexant 205xx [6] will also address this issue¹? They are for 5066 and I have 5069 according to [2]. If yes, is there a package repository with a package having this patches applied I can install using the package management system? Thanks, Paul ¹ Maybe you could add »5066« also to the commit message of the second patch. Since the data sheets seem to use this name.? But this string is not shown in `alsa-info.sh` so it seems it is not important. [1] http://packages.ubuntu.com/maverick-updates/linux-image-2.6.35-25-generic [2] http://www.insidesocal.com/click/2011/01/living-on-the-edge-with-the-li.html [3] http://www.insidesocal.com/click/2010/10/fedora-13-fixing-sound-and-vid.html [4] http://monespaceperso.org/blog-en/2010/05/02/upgrade-alsa-1-0-23-on-ubuntu-… [5] http://mailman.alsa-project.org/pipermail/alsa-devel/2011-January/035954.ht… [6] http://mailman.alsa-project.org/pipermail/alsa-devel/2011-January/035400.ht…

3 3

[alsa-devel] Jack sense fails on Fujitsu p7120
by Robin Neatherway 06 Feb '11

06 Feb '11

I posted regarding this issue to alsa-users, but haven't had any response. I've come to the conclusion that I will have to modify the driver myself to rectify this problem, so I would appreciate some pointers as to how to get started with that. Running Xubuntu 10.10 with Alsa 1.0.23 The sound chip is Intel HDA, ALC260. I have tried setting options snd-hda-intel model=fujitsu in /etc/modprobe.d/alsa-base.conf, but this hasn't made any difference. There is no "Jack Sense" option in alsamixer. I've also tried a couple of values for fix_position. I've tried following the ubuntu wiki pages for Intel HDA and sound debugging in general, to no avail. When doing the jack sense test recommended on https://wiki.ubuntu.com/ALSA/JackSense the two files generated with and without the headphones plugged in were identical. This makes me think it is a driver problem. I pasted the output of `cat /proc/asound/card*/codec*` at http://pastebin.com/4NyvdsXf in case this is of any help.

3 15