Re: mixer settings for voice recording?
I've created a wiki-account and put the alsa setting, which allow voice recording/capturing from e.g. /dev/dsp, into my accounts page: http://wiki.openmoko.org/wiki/User:Herp oops, I just noticed that 'ADC Capture Volume', control #2, was set to a too low value (195). To get some result instantly (without shouting at the neo), it's best to set it to 255, like: control.2 { comment.access 'read write' comment.type INTEGER comment.count 2 comment.range '0 - 255' iface MIXER name 'ADC Capture Volume' value.0 255 value.1 255 } kind regrads, H. Rosmanith ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: mixer settings for voice recording?
e. I was going to tabulate the controls, but haven't got to grips with the mediawiki table markup yet. I'm open to suggestions! I was unaware of the cool ALSA mapping, but tried to start a mapping here: http://wiki.openmoko.org/wiki/Neo_alsamixer Change it or nuke it as you please. I've created a wiki-account and put the alsa setting, which allow voice recording/capturing from e.g. /dev/dsp, into my accounts page: http://wiki.openmoko.org/wiki/User:Herp use as you like. kind regrads, H. Rosmanith ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: mixer settings for voice recording?
Hello Andy, Somebody in the thread at some point said: | So, what is required to make the dsp-device delive audio-data? | | Q: The hardware does support this, right? Yeah. | Q: Is it a audio-driver problem, e.g. the alsa-device-driver for the chip |doesnt support audio capturing? | | Q: Is it a problem with my mixer settings? If so, which are the correct |mixer settings? I can't give you a straight answer on what to do, but here is the situation around it. The normal audio routing for the microphone inside the WM8753 codec is to bring it in on MIC2 port and then send it via an analogue path around some scalers and mixers and switches and send it back out again on MONO1 / MONO2 to the GSM chip. In short it doesn't get delivered to the ADC in the Wolfson where you can pull it as normal PCM. okay, this means normally the wm8753 is not configured to do this, but you can configure it to make it work, right? and if configured correctly, which is: If the PGA and mux are configured, it should work OK. then /dev/dsp will output PCM data? One last consideration, the Mic is OFF unless you enabled MICBIAS signal to power it. hm ... I dunno how to do this. In alsamixer, in the capture view, I see several controls, like e.g. PCM, Mic1, Mic2, Capture. I've put them all to 100% and unmuted them. Still there's no activity on /dev/dsp. On the other hand, I don't see a MICBIAS control. If it helps, I could copy the contents of /etc/asound.state into an email. kind regards, H. Rosmanith ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: mixer settings for voice recording?
and if configured correctly, which is: If the PGA and mux are configured, it should work OK. then /dev/dsp will output PCM data? woah, I finally got it to work. I change DAI Mode from DAI 0 to DAI 1 - and suddenly the dsp-device spits out tons o' data. that was quite some trial and error, a real DAI hard. kind regards, H. Rosmanith ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: mixer settings for voice recording?
by the way, when reading from dsp with od and changing the settings (DAI 0 - DAI 1), od would zombie and never release the device. a dmesg shows why: Unable to handle kernel NULL pointer dereference at virtual address pgd = c0004000 [] *pgd= Internal error: Oops: 0 [#1] PREEMPT Modules linked in: snd_soc_neo1973_gta02_wm8753 snd_soc_s3c24xx_i2s snd_soc_s3c24xx snd_soc_wm8753 snd_soc_core snd_pcm_oss snd_pcm snd_timer snd_page_alloc snd_mixer_oss snd rfcomm ohci_hcd hidp l2cap hci_usb bluetooth CPU: 0Not tainted (2.6.24 #1) PC is at __init_begin+0x3fff8000/0x34 LR is at neo1973_gta02_hifi_hw_free+0x30/0x34 [snd_soc_neo1973_gta02_wm8753] pc : []lr : [bf080030]psr: a013 sp : c6527d28 ip : bf079080 fp : c6527d34 r10: bf07ece0 r9 : c6527fb0 r8 : bf07bfb8 r7 : c6f9d880 r6 : bf079080 r5 : bf081c88 r4 : c6fb5740 r3 : r2 : r1 : r0 : bf079080 Flags: NzCv IRQs on FIQs on Mode SVC_32 ISA ARM Segment user Control: c000717f Table: 36cb8000 DAC: 0015 Process od (pid: 1438, stack limit = 0xc6526268) Stack: (0xc6527d28 to 0xc6528000) 7d20: c6527d5c c6527d38 bf06a6e4 bf080010 c6f9d880 c7e02c80 7d40: c7fa7b08 c65599a0 c7c0dd20 c6527f50 c6527d74 c6527d60 bf04f4d4 bf06a67c 7d60: c0076864 0008 c6527d8c c6527d78 bf061ef4 bf04f494 c7e02c80 c7fa7a00 7d80: c6527dac c6527d90 bf061f58 bf061ee0 0010 c65599a0 c6f0557c c787a41c 7da0: c6527ddc c6527db0 c00964cc bf061f1c c64e59b0 c65599a0 7dc0: c64a49c0 c64a49c8 c6527dec c6527de0 c00968c0 c009642c 7de0: c6527e0c c6527df0 c00932cc c009689c 0047 c64a49c0 0027 7e00: c6527e34 c6527e10 c0048538 c0093260 c0043e18 c6d639e0 c64a49c0 0002 7e20: c6526000 c6527ed0 c6527e4c c6527e38 c00485dc c00484c0 0001 c6d639e0 7e40: c6527e64 c6527e50 c0049a7c c004859c c6527e60 c6527e84 c6527e68 7e60: c004a080 c004989c c6526000 c64c2114 4001d000 0009 c6527ebc c6527e88 7e80: c0053cb8 c0049fe0 c02bd088 c6d63be0 c64bdc00 c00290e8 4001d000 c6527fb0 7ea0: 0004 c00290e8 c6526000 c6527f9c c6527ec0 c002bca8 c00538c0 7ec0: c6527ee0 c6d63be0 c64e040c 0009 7ee0: c6527ef0 c0188ff4 c00413c0 002b c6527f18 c6527f4c c6527f08 7f00: c01894fc c0188f98 0001 c018c864 c64e040c c795c1cc 7f20: 0002 c795b704 c795c0d0 002b c00290e8 c6526000 7f40: c6527f74 c6527f50 c0095a18 c00c3cc4 c6559da0 7f60: 0004 c6527fa4 c6527f78 c0095fd0 004a 4001d000 401ee600 7f80: 0004 c00290e8 c6526000 c6527fac c6527fa0 c002c1ac c002bc54 7fa0: c6527fb0 c0028f8c c002c190 002b 4001d000 004a 7fc0: 004a 4001d000 401ee600 0004 004a 000890e9 401ee000 bec77a7c 7fe0: 0004 bec77460 401343f0 40181b5c 6010 0001 Backtrace: [bf08] (neo1973_gta02_hifi_hw_free+0x0/0x34 [snd_soc_neo1973_gta02_wm8753]) from [bf06a6e4] (soc_pcm_hw_free+0x78/0xcc [snd_soc_core]) [bf06a66c] (soc_pcm_hw_free+0x0/0xcc [snd_soc_core]) from [bf04f4d4] (snd_pcm_release_substream+0x50/0x98 [snd_pcm]) [bf04f484] (snd_pcm_release_substream+0x0/0x98 [snd_pcm]) from [bf061ef4] (snd_pcm_oss_release_file+0x24/0x3c [snd_pcm_oss]) r4:0008 [bf061ed0] (snd_pcm_oss_release_file+0x0/0x3c [snd_pcm_oss]) from [bf061f58] (snd_pcm_oss_release+0x4c/0x88 [snd_pcm_oss]) r5:c7fa7a00 r4:c7e02c80 [bf061f0c] (snd_pcm_oss_release+0x0/0x88 [snd_pcm_oss]) from [c00964cc] (__fput+0xb0/0x194) r7:c787a41c r6:c6f0557c r5:c65599a0 r4:0010 [c009641c] (__fput+0x0/0x194) from [c00968c0] (fput+0x34/0x38) r8: r7:c64a49c8 r6: r5:c64a49c0 r4:c65599a0 [c009688c] (fput+0x0/0x38) from [c00932cc] (filp_close+0x7c/0x88) [c0093250] (filp_close+0x0/0x88) from [c0048538] (put_files_struct+0x88/0xdc) r6: r5:0027 r4:c64a49c0 [c00484b0] (put_files_struct+0x0/0xdc) from [c00485dc] (__exit_files+0x50/0x54) r8:c6527ed0 r7:c6526000 r6:0002 r5:c64a49c0 r4:c6d639e0 [c004858c] (__exit_files+0x0/0x54) from [c0049a7c] (do_exit+0x1f0/0x744) r5:c6d639e0 r4:0001 [c004988c] (do_exit+0x0/0x744) from [c004a080] (do_group_exit+0xb0/0xb8) [c0049fd0] (do_group_exit+0x0/0xb8) from [c0053cb8] (get_signal_to_deliver+0x408/0x454) r6:0009 r5:4001d000 r4:c64c2114 [c00538b0] (get_signal_to_deliver+0x0/0x454) from [c002bca8] (do_signal+0x64/0x53c) [c002bc44] (do_signal+0x0/0x53c) from [c002c1ac] (do_notify_resume+0x2c/0x30) [c002c180] (do_notify_resume+0x0/0x30) from [c0028f8c] (work_pending+0x1c/0x20) Code: bad PC value. ---[ end trace 0d13bca5737a7c62 ]--- Fixing recursive fault but reboot is needed! [EMAIL PROTECTED]:~# kernel is uImage-2.6.24+git25+8533927964761f4e2078ccd8607b90f5acc60b93-r0-om-gta02.bin kind regards, H. Rosmanith ob-Wishlist: a RESET button, just like in a PC. ___ support
Re: mixer settings for voice recording?
and if configured correctly, which is: If the PGA and mux are configured, it should work OK. then /dev/dsp will output PCM data? woah, I finally got it to work. I change DAI Mode from DAI 0 to DAI 1 - and suddenly the dsp-device spits out tons o' data. sweet! ; -- Jay Vaughan ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: mixer settings for voice recording?
On Tuesday 29 July 2008, H. Rosmanith wrote: and if configured correctly, which is: If the PGA and mux are configured, it should work OK. then /dev/dsp will output PCM data? woah, I finally got it to work. I change DAI Mode from DAI 0 to DAI 1 - and suddenly the dsp-device spits out tons o' data. sweet! hm, hm ... well, according to alsa.state, DAI Mode is control #50, which is not drawn in WM8753 to ALSA mappings (http://wiki.openmoko.org/images/a/af/WM8753_ALSA_Mapping.png) There are 2 reasons for that. First it's work in progress - I haven't worked out where everything is yet. Second there is some difficulty adding controls that are logical entities in the digital blocks to the picture. I was going to tabulate the controls, but haven't got to grips with the mediawiki table markup yet. I'm open to suggestions! ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: mixer settings for voice recording?
e. I was going to tabulate the controls, but haven't got to grips with the mediawiki table markup yet. I'm open to suggestions! I was unaware of the cool ALSA mapping, but tried to start a mapping here: http://wiki.openmoko.org/wiki/Neo_alsamixer Change it or nuke it as you please. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support