Ticket #2095 (closed defect: fixed)

Opened 8 years ago

Last modified 8 years ago

Sound not found with qi bootloader

Reported by: newkirk Owned by: openmoko-devel
Priority: normal Milestone:
Component: unknown Version:
Severity: major Keywords:
Cc: Blocked By:
Blocking: Estimated Completion (week):
HasPatchForReview: no PatchReviewResult:
Reproducible: always

Description

I've finally seen the pattern to a bug I've been having for weeks - If I'm using the qi bootloader (Thanks Andy, so far it's damned promising) then sound doesn't work. I try aplay from terminal and get errors that sound device doesn't exist. Reflash just bootloader back to uboot and sound returns. Reflash to qi and sound fails.

Both aplay amd mplayer report the following (this is mplayer's formatting, same messages from aplay):

[AO_ALSA] alsa-lib: confmisc.c:768:(parse_card) cannot find card '0'
[AO_ALSA] alsa-lib: conf.c:3510:(_snd_config_evaluate) function snd_func_card_driver returned error: No such device
[AO_ALSA] alsa-lib: confmisc.c:392:(snd_func_concat) error evaluating strings
[AO_ALSA] alsa-lib: conf.c:3510:(_snd_config_evaluate) function snd_func_concat returned error: No such device
[AO_ALSA] alsa-lib: confmisc.c:1251:(snd_func_refer) error evaluating name
[AO_ALSA] alsa-lib: conf.c:3510:(_snd_config_evaluate) function snd_func_refer returned error: No such device
[AO_ALSA] alsa-lib: conf.c:3982:(snd_config_expand) Evaluate error: No such device
[AO_ALSA] alsa-lib: pcm.c:2145:(snd_pcm_open_noupdate) Unknown PCM dmix
[AO_ALSA] Playback open error: No such device

dmesg under qi includes:

Advanced Linux Sound Architecture Driver Version 1.0.15 (Tue Nov 20 19:16:42 2007 UTC).
ASoC version 0.13.1
ALSA device list:

No soundcards found.

and:

snd: exports duplicate symbol snd_add_device_sysfs_file (owned by kernel)
wm8753: WM8753 Audio Codec 0.16
Alignment trap: hald-probe-volu (1197) PC=0x0000ce78 Instr=0xe59b300c Address=0xbed225aa FSR 0x013
Alignment trap: hald-probe-volu (1197) PC=0x0000ce94 Instr=0xe59b1008 Address=0xbed225a6 FSR 0x013
Alignment trap: hald-probe-volu (1197) PC=0x0000ce78 Instr=0xe59b300c Address=0xbed225ba FSR 0x013
Alignment trap: hald-probe-volu (1197) PC=0x0000ce94 Instr=0xe59b1008 Address=0xbed225b6 FSR 0x013
Alignment trap: hald-probe-volu (1197) PC=0x0000ce78 Instr=0xe59b300c Address=0xbed225ca FSR 0x013
Alignment trap: hald-probe-volu (1197) PC=0x0000ce94 Instr=0xe59b1008 Address=0xbed225c6 FSR 0x013
Alignment trap: hald-probe-volu (1197) PC=0x0000ce78 Instr=0xe59b300c Address=0xbed225da FSR 0x013
Alignment trap: hald-probe-volu (1197) PC=0x0000ce94 Instr=0xe59b1008 Address=0xbed225d6 FSR 0x013

While under uboot there's a slight difference with:

Advanced Linux Sound Architecture Driver Version 1.0.15 (Tue Nov 20 19:16:42 2007 UTC).
ASoC version 0.13.1
ALSA device list:

No soundcards found.

and:

snd: exports duplicate symbol snd_add_device_sysfs_file (owned by kernel)
wm8753: WM8753 Audio Codec 0.16
asoc: WM8753 HiFi? <-> s3c24xx-i2s mapping ok
asoc: WM8753 Voice <-> Bluetooth mapping ok
Alignment trap: hald-probe-volu (1230) PC=0x0000ce78 Instr=0xe59b300c Address=0xbea845aa FSR 0x013
Alignment trap: hald-probe-volu (1230) PC=0x0000ce94 Instr=0xe59b1008 Address=0xbea845a6 FSR 0x013
Alignment trap: hald-probe-volu (1230) PC=0x0000ce78 Instr=0xe59b300c Address=0xbea845ba FSR 0x013
Alignment trap: hald-probe-volu (1230) PC=0x0000ce94 Instr=0xe59b1008 Address=0xbea845b6 FSR 0x013
Alignment trap: hald-probe-volu (1230) PC=0x0000ce78 Instr=0xe59b300c Address=0xbea845ca FSR 0x013
Alignment trap: hald-probe-volu (1230) PC=0x0000ce94 Instr=0xe59b1008 Address=0xbea845c6 FSR 0x013
Alignment trap: hald-probe-volu (1230) PC=0x0000ce78 Instr=0xe59b300c Address=0xbea845da FSR 0x013
Alignment trap: hald-probe-volu (1230) PC=0x0000ce94 Instr=0xe59b1008 Address=0xbea845d6 FSR 0x013

j

Change History

comment:1 Changed 8 years ago by newkirk

Sorry, meant to include that this affects SHR, FSO, Raster, and 2008.x. Everything I've tried.

j

comment:2 Changed 8 years ago by andy

The way that the alsa SoC stuff registers i2c things changed recently, stable-tracking uses the new way. I have seen it work and not work with qi on the 2.6.24 stuff. As soon as we fix the last few problems on stable-tracking we will transition to it as the new stable and hopefully this will be gone away.

comment:3 Changed 8 years ago by gromgull

(no comment - I just want to be cc'd)

comment:4 Changed 8 years ago by Leonti

I'm using 2.6.24 kernel with SHR and I have sound.
Is it me who is lucky or the problem is solved?
If so please confirm, so I(or anyone else) can edit wiki page.

Leonti

comment:5 Changed 8 years ago by andy

  • Status changed from new to closed
  • Resolution set to fixed

Yes it's solved... Qi did not bring up the regulator used to power the codec.

comment:6 Changed 8 years ago by werner

Considering the 100mA envelope, shouldn't we leave regulators not
essential for booting off until the kernel decides it's safe to
turn them on ?

In the u-boot current-reduction work, keeping unused regulators off
made a significant difference, 40mA in total for LDO1, 2, 5, and 6.

See also u-boot commit 77ef5a9f920092fcebfe592607b7866ac36e3c8e

comment:7 Changed 8 years ago by andy

It's a good point, but since other things needed for Linux boot at < 100mA don't exist ye it's a job for another day... in the meanwhile "sound works with Qi".

Note: See TracTickets for help on using tickets.