tiomap-dev team mailing list archive

[Tobin Davis <880929@xxxxxxxxxxxxxxxxxx>]

I'm seeing this now on PandaES as well.  The above workaround is only a
workaround.  The real fix involves fixing alsaucm to only parse the
correct set of config files.  Ultimately, there could be dozens of UCM
configurations.  alsaucm needs to pick the right one, not the first one
(which seems to be the case here).

** Changed in: alsa-utils (Ubuntu)
       Status: New => Confirmed

** Changed in: alsa-utils (Ubuntu)
   Importance: Undecided => Medium

** Changed in: alsa-utils (Ubuntu)
    Milestone: None => ubuntu-12.04-beta-1

** Changed in: alsa-utils (Ubuntu)
     Assignee: (unassigned) => Tobin Davis (gruemaster)

-- 
You received this bug notification because you are a member of TI OMAP
Developers, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/880929

Title:
  alsa ucm udev rules not working on SDP4430

Status in “alsa-utils” package in Ubuntu:
  Confirmed

Bug description:
  Release:  ubuntu-11.10-preinstalled-desktop-armel+omap4 image
  alsa-utils version: 1.0.24.2-0ubuntu8.1

  I am using the ARM Oneiric image for OMAP4 on Panda and Blaze.
  On Panda the Audioo is correctly configured, not on SDP4430.
  My understanding is that /usr/bin/alsaucm shall set the card in the udev rules.
  Indeed, by running "alsaucm listcards" on Panda or SDP4430 boards, we have following output:
    0: Panda
    1: SDP4430

  I suppose that when alsaucm is used without a card precised, the first
  one is considered.

  In file /lib/udev/rules.d/90-alsa-ucm.rules, replacing the following lines :
  ATTRS{id}=="SDP4430|Panda", RUN+="/usr/bin/alsaucm set _verb HiFi"
  ATTRS{id}=="SDP4430|Panda", RUN+="/usr/bin/alsaucm set _verb Record"

  With:
  ATTRS{id}=="SDP4430", RUN+="/usr/bin/alsaucm -c SDP4430 set _verb HiFi"
  ATTRS{id}=="SDP4430", RUN+="/usr/bin/alsaucm -c SDP4430 set _verb Record"
  ATTRS{id}=="Panda", RUN+="/usr/bin/alsaucm -c Panda set _verb HiFi"
  ATTRS{id}=="Panda", RUN+="/usr/bin/alsaucm -c Panda set _verb Record"

  ... fixes the issue.
  With that rules audio is OK on both Panda and SDP4430.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-utils/+bug/880929/+subscriptions