February 2012 - Alsa-devel - mailman.alsa-project.org

[alsa-devel] [PATCH] ASoC: core: Fix snd_soc_add_card_controls to pass correct data
by Stephen Warren 15 Feb '12

15 Feb '12

Commit 022658b "ASoC: core: Add support for DAI and machine kcontrols." created new functions to create controls for cards, codecs, platforms, and DAIs. The new snd_soc_add_card_controls() passed the wrong "data" to utility function snd_soc_add_controls(); it should be passing a codec, but instead ended up passing the soc_card. Fix this. Signed-off-by: Stephen Warren <swarren(a)nvidia.com> --- sound/soc/soc-core.c | 6 +++++- 1 files changed, 5 insertions(+), 1 deletions(-) diff --git a/sound/soc/soc-core.c b/sound/soc/soc-core.c index 8bd9995..e44b6f6 100644 --- a/sound/soc/soc-core.c +++ b/sound/soc/soc-core.c @@ -2095,9 +2095,13 @@ int snd_soc_add_card_controls(struct snd_soc_card *soc_card, const struct snd_kcontrol_new *controls, int num_controls) { struct snd_card *card = soc_card->snd_card; + struct snd_soc_codec *codec = + list_first_entry(&soc_card->codec_dev_list, + struct snd_soc_codec, + card_list); return snd_soc_add_controls(card, soc_card->dev, controls, num_controls, - NULL, soc_card); + NULL, codec); } EXPORT_SYMBOL_GPL(snd_soc_add_card_controls); -- 1.7.0.4

2 1

[alsa-devel] [PATCH 0/3] ASoC: Relocate the OMAP HDMI codec to sound
by Ricardo Neri 14 Feb '12

14 Feb '12

Hello, Currently, the ASoC HDMI codec is embedded in the DSS HDMI driver. In order to give the OMAP HDMI code a more logical arrangement, the audio part is moved to /sound. Deep color support has been removed until it is supported by DSS so that no ugly register readings are done. The rest of the functionality is still supported. The relocation of the code is split into two parts: Part 1 is for DSS. It removes the HDMI codec from DSS and exposes DSS functionality to ASoC. Part 2 is the actual relocation of the codec under /sound. The purpose of this is split is to ease the integration of these patches first to DSS and then to ASoC. The DSS part has been submitted and can be consulted here: http://www.spinics.net/lists/linux-omap/msg64477.html Please note that these patches will not apply without the aforementioned DSS part. This work is also based on the patches previously sent for HDMI audio MCLK support: http://www.spinics.net/lists/linux-omap/msg64302.html and was implemented on top of: git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git v3.3-rc3 Thanks, Ricardo Axel Castaneda Gonzalez (1): OMAPDSS/ASoC: Relocate ASoC HDMI codec. Part 2 Ricardo Neri (2): ASoC: OMAP: HDMI: Update codec name ASoC: OMAP: Update Kconfig and Makefile files for HDMI audio codec sound/soc/codecs/Kconfig | 4 + sound/soc/codecs/Makefile | 5 + sound/soc/codecs/omap-hdmi.c | 422 ++++++++++++++++++++++++++++++++++++++ sound/soc/omap/Kconfig | 1 + sound/soc/omap/omap4-hdmi-card.c | 2 +- 5 files changed, 433 insertions(+), 1 deletions(-) create mode 100644 sound/soc/codecs/omap-hdmi.c

2 6

[alsa-devel] ASoC update for 3.3
by Mark Brown 14 Feb '12

14 Feb '12

The following changes since commit a7c4183be2d6a7da8c97a9b671b5f3aed321127e: ASoC: wm8994: Disable line output discharge prior to ramping VMID (2012-02-08 19:52:00 +0000) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git asoc-3.3 for you to fetch changes up to 1987877d869027ab63dc9df515e11f19279a8091: ASoC: fsi: fixup fsi_pointer() calculation method (2012-02-09 10:50:53 +0000) ---------------------------------------------------------------- A simple fix from Morimoto-san for the pointer() operation in the FSI driver. ---------------------------------------------------------------- Kuninori Morimoto (1): ASoC: fsi: fixup fsi_pointer() calculation method sound/soc/sh/fsi.c | 6 +----- 1 files changed, 1 insertions(+), 5 deletions(-)

2 1

[alsa-devel] [PATCH] ALSA: intel8x0: Fix default inaudible sound on Gateway M520
by Dan Chen 14 Feb '12

14 Feb '12

Hi Takashi, Attached please find a patch against current sound.git head that resolves a user's default inaudible sound on the Gateway M520. It's applicable to stable kernel trees, too. Thanks for considering the patch. Cheers. -Dan

2 1

Re: [alsa-devel] TWL4030 low-latency
by Peter Ujfalusi 14 Feb '12

14 Feb '12

On 01/12/2012 02:09 AM, Jacinto Alvarez wrote: > Hi Peter, > > Thanks for your reply. > > Not sure what you mean under latency. For me the latency is the time > needed to play out the sample at the DMA pointer in main memory. > In case of McBSP2 (which has 1280 word long buffer) it is maximum of: > (1280/<number of channels>)/sampling frequency > In case of stereo sample it is 14.51ms with 44.1KHz, and 13.3ms with > 48KHz. > > > With latency I refer to the round-trip of the combined capture-playback > operation. The application I am using creates a couple of input/output > streams and bounds them together with snd_pcm_link(). The shortest time > I can get for this round-trip is 1024 frames (~23 ms) and I get that by > initializing the streams with 8 periods of 128 frames each. > > > In McBSP element mode the McBSP FIFO will be kept full all the time > (threshold is 0). This means that the McBSP will request one word from > the DMA if there's a single free slot in the FIFO. > > If you switch to threshold mode things will be different under the hood > (providing better power saving): > the McBSP threshold value will be calculated according to the period > size. In this mode the DMA will request for a chunk of data based on the > threshold value, so the FIFO will be filled with DMA bursts. You still > have the FIFO caused latency, but the system can rest between bursts. > I think if you use McBSP threshold mode with 3x 5ms periods you should > be fine (the ALSA buffer is going to be 15ms). > > > Is this threshold mode set by the application with the > snd_pcm_sw_params_set_start_threshold() command (e.g., passing a > non-zero parameter) or are you talking of some tweak INSIDE the driver's > code? It is McBSP driver specific. we do not have (yet) ALSA level control for it. The best fit would be some type of QoS, but I'm not sure of it. > Currently the application is initializing the streams with > snd_pcm_sw_params_set_start_threshold() and a value equal to the period > size (128 frames). Lets' try this (assuming you are using McBSP2): echo threshold > /sys/devices/platform/omap/omap-mcbsp.2/dma_op_mode Do you see difference in the round-trip? -- Péter

1 0

[alsa-devel] [PATCH] ASoC: wm8962: Fix sidetone enumeration texts
by Mark Brown 14 Feb '12

14 Feb '12

The sidetone enumeration texts have left and right swapped. Signed-off-by: Mark Brown <broonie(a)opensource.wolfsonmicro.com> --- sound/soc/codecs/wm8962.c | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/sound/soc/codecs/wm8962.c b/sound/soc/codecs/wm8962.c index 85f71a7..0fc7a56 100644 --- a/sound/soc/codecs/wm8962.c +++ b/sound/soc/codecs/wm8962.c @@ -2001,7 +2001,7 @@ static int dsp2_event(struct snd_soc_dapm_widget *w, return 0; } -static const char *st_text[] = { "None", "Right", "Left" }; +static const char *st_text[] = { "None", "Left", "Right" }; static const struct soc_enum str_enum = SOC_ENUM_SINGLE(WM8962_DAC_DSP_MIXING_1, 2, 3, st_text); -- 1.7.9.rc1

1 0

[alsa-devel] snd_dice: category ID
by Rolf Anderegg 13 Feb '12

13 Feb '12

Hi Clemens, I'd like to request the following patch to be applied on the firewire-kernel-streaming branch (current commit head 526795d69f5be6d058bdf89a65a303a1ee136aba). It involves handling Weiss DICE devices which use a dedicated category ID (other than TCAT's default Cat ID (0x04), which is not necessarily binding). Citing (one of many) TC's user guide: [...] The manufacturer is free to use the lower 5 bytes of the WWUID in any way. The DICE firmware, by default, uses the chip ID as follows: Upper 32 bits of WWUID +------------------------+--------+ | 24 bit OUI – 0x000166 | Cat | +------------------------+--------+ Category 8 bits: TCAT uses 0x04 for this field. Lower 32 bits of WWUID +----------------------------+----------------+ | 10 bit product identifier | 22 bit serial# | +----------------------------+----------------+ [...] Presumably, few of the other vendors have changed TCATs default Cat. ID. We have decided to change it to 0x00 since the beginning of our DICE product-line, alas this should be considered in snd-dice's dice_interface_check. Thanks in advance. Rolf Anderegg

2 1

[alsa-devel] snd-hda-intel: Power management not enabled until audio is played
by Paul Menzel 13 Feb '12

13 Feb '12

Dear ALSA folks, playing with PowerTOP 1.97 I notice that it lists 100 % usage for the Audio device on several systems [1]. I made sure that power management is enabled. $ grep snd /etc/modprobe.d/* …: options snd_hda_intel power_save=1 $ more /sys/module/snd_hda_intel/parameters/power_save_controller Y $ more /sys/module/snd_hda_intel/parameters/power_save 0 Since I was on AC power pm-utils seems to reset that parameter to not save power. :/ $ sudo su # echo "1" > /sys/module/snd_hda_intel/parameters/power_save # exit But enabling that does not change anything right away. Only after using the device by playing some audio – `speaker-test` in this case, the power management seems to kick in. $ more /sys/module/snd_hda_intel/parameters/power_save* :::::::::::::: /sys/module/snd_hda_intel/parameters/power_save :::::::::::::: 1 :::::::::::::: /sys/module/snd_hda_intel/parameters/power_save_controller :::::::::::::: Y $ more /sys/devices/pci0000\:00/0000\:00\:1b.0/sound/card0/hwC0D0/power_*_acct :::::::::::::: /sys/devices/pci0000:00/0000:00:1b.0/sound/card0/hwC0D0/power_off_acct :::::::::::::: 9640 :::::::::::::: /sys/devices/pci0000:00/0000:00:1b.0/sound/card0/hwC0D0/power_on_acct :::::::::::::: 405056 $ more /sys/devices/pci0000\:00/0000\:00\:1b.0/sound/card0/hwC0D0/power_*_acct :::::::::::::: /sys/devices/pci0000:00/0000:00:1b.0/sound/card0/hwC0D0/power_off_acct :::::::::::::: 9640 :::::::::::::: /sys/devices/pci0000:00/0000:00:1b.0/sound/card0/hwC0D0/power_on_acct :::::::::::::: 409664 $ more /sys/devices/pci0000\:00/0000\:00\:1b.0/sound/card0/hwC0D0/power_*_acct :::::::::::::: /sys/devices/pci0000:00/0000:00:1b.0/sound/card0/hwC0D0/power_off_acct :::::::::::::: 9640 :::::::::::::: /sys/devices/pci0000:00/0000:00:1b.0/sound/card0/hwC0D0/power_on_acct :::::::::::::: 413672 $ date && more /sys/devices/pci0000\:00/0000\:00\:1b.0/sound/card0/hwC0D0/power_*_acct Sa 11. Feb 10:08:46 CET 2012 :::::::::::::: /sys/devices/pci0000:00/0000:00:1b.0/sound/card0/hwC0D0/power_off_acct :::::::::::::: 9640 :::::::::::::: /sys/devices/pci0000:00/0000:00:1b.0/sound/card0/hwC0D0/power_on_acct :::::::::::::: 464644 $ date && more /sys/devices/pci0000\:00/0000\:00\:1b.0/sound/card0/hwC0D0/power_*_acct Sa 11. Feb 10:08:52 CET 2012 :::::::::::::: /sys/devices/pci0000:00/0000:00:1b.0/sound/card0/hwC0D0/power_off_acct :::::::::::::: 9640 :::::::::::::: /sys/devices/pci0000:00/0000:00:1b.0/sound/card0/hwC0D0/power_on_acct :::::::::::::: 470076 $ date && more /sys/devices/pci0000\:00/0000\:00\:1b.0/sound/card0/hwC0D0/power_*_acct Sa 11. Feb 10:09:04 CET 2012 :::::::::::::: /sys/devices/pci0000:00/0000:00:1b.0/sound/card0/hwC0D0/power_off_acct :::::::::::::: 9640 :::::::::::::: /sys/devices/pci0000:00/0000:00:1b.0/sound/card0/hwC0D0/power_on_acct :::::::::::::: 482604 $ date && more /sys/devices/pci0000\:00/0000\:00\:1b.0/sound/card0/hwC0D0/power_*_acct Sa 11. Feb 10:10:41 CET 2012 :::::::::::::: /sys/devices/pci0000:00/0000:00:1b.0/sound/card0/hwC0D0/power_off_acct :::::::::::::: 9640 :::::::::::::: /sys/devices/pci0000:00/0000:00:1b.0/sound/card0/hwC0D0/power_on_acct :::::::::::::: 578904 $ date && speaker-test Sa 11. Feb 10:12:58 CET 2012 speaker-test 1.0.24.2 Wiedergabe-Gerät ist default Stream-Parameter sind 48000 Hz, S16_LE, 1 Kanäle Verwende 16 Oktaven rosa Rauschen Rate ist 48000 Hz (angefordert: 48000 Hz) Puffergröße von 2048 bis 8192 Periodengröße von 1024 bis 1024 Verwende maximale Puffergröße 8192 Perioden = 4 gesetzt: period_size = 1024 gesetzt: buffer_size = 8192 0 - Vorne links Zeit pro Periode = 2,828717 0 - Vorne links Zeit pro Periode = 2,985785 0 - Vorne links Zeit pro Periode = 2,985784 0 - Vorne links Zeit pro Periode = 2,985806 0 - Vorne links Zeit pro Periode = 2,985834 0 - Vorne links Zeit pro Periode = 2,985798 0 - Vorne links Zeit pro Periode = 2,985838 0 - Vorne links ^C $ date && more /sys/devices/pci0000\:00/0000\:00\:1b.0/sound/card0/hwC0D0/power_*_acct Sa 11. Feb 10:13:24 CET 2012 :::::::::::::: /sys/devices/pci0000:00/0000:00:1b.0/sound/card0/hwC0D0/power_off_acct :::::::::::::: 100732 :::::::::::::: /sys/devices/pci0000:00/0000:00:1b.0/sound/card0/hwC0D0/power_on_acct :::::::::::::: 651372 $ date && more /sys/devices/pci0000\:00/0000\:00\:1b.0/sound/card0/hwC0D0/power_*_acct Sa 11. Feb 10:13:29 CET 2012 :::::::::::::: /sys/devices/pci0000:00/0000:00:1b.0/sound/card0/hwC0D0/power_off_acct :::::::::::::: 105384 :::::::::::::: /sys/devices/pci0000:00/0000:00:1b.0/sound/card0/hwC0D0/power_on_acct :::::::::::::: 651372 $ date && more /sys/devices/pci0000\:00/0000\:00\:1b.0/sound/card0/hwC0D0/power_*_acct Sa 11. Feb 10:24:18 CET 2012 :::::::::::::: /sys/devices/pci0000:00/0000:00:1b.0/sound/card0/hwC0D0/power_off_acct :::::::::::::: 753148 :::::::::::::: /sys/devices/pci0000:00/0000:00:1b.0/sound/card0/hwC0D0/power_on_acct :::::::::::::: 652876 Is that an error in the driver? I have seen that with Realtek and Conexant devices. Please also find the output of `alsa-info.sh` [2] attached. There is no difference before and after playing some audio. $ diff -u alsa-info.txt.beforeplayingaudio alsa-info.txt.afterplayingaudio --- alsa-info.txt.beforeplayingaudio 2012-02-11 10:11:31.000000000 +0100 +++ alsa-info.txt.afterplayingaudio 2012-02-11 10:13:52.000000000 +0100 @@ -3,7 +3,7 @@ !!ALSA Information Script v 0.4.60 !!################################ -!!Script ran on: Sat Feb 11 09:11:29 UTC 2012 +!!Script ran on: Sat Feb 11 09:13:51 UTC 2012 !!Linux Distribution @@ -379,7 +379,7 @@ crw-rw----+ 1 root audio 116, 5 Feb 11 10:00 /dev/snd/controlC0 crw-rw----+ 1 root audio 116, 4 Feb 11 10:00 /dev/snd/hwC0D0 crw-rw----+ 1 root audio 116, 3 Feb 11 10:00 /dev/snd/pcmC0D0c -crw-rw----+ 1 root audio 116, 2 Feb 11 10:00 /dev/snd/pcmC0D0p +crw-rw----+ 1 root audio 116, 2 Feb 11 10:12 /dev/snd/pcmC0D0p crw-rw----+ 1 root audio 116, 1 Feb 11 10:00 /dev/snd/seq crw-rw----+ 1 root audio 116, 33 Feb 11 10:00 /dev/snd/timer Thanks, Paul [1] http://lists.lesswatts.org/pipermail/discuss/2012-February/000687.html [2] http://alsa-project.org/main/index.php/Help_To_Debug

2 3

[alsa-devel] [PATCH 1/2] ASoC: tegra+alc5632: Added digital microphone DAPM widget.
by Leon Romanovsky 13 Feb '12

13 Feb '12

ALC5632 codec supports digital microphone. This patch adds DAPM widget. Signed-off-by: Leon Romanovsky <leon(a)leon.nu> --- sound/soc/tegra/tegra_alc5632.c | 1 + 1 files changed, 1 insertions(+), 0 deletions(-) diff --git a/sound/soc/tegra/tegra_alc5632.c b/sound/soc/tegra/tegra_alc5632.c index c000f51..2a27725 100644 --- a/sound/soc/tegra/tegra_alc5632.c +++ b/sound/soc/tegra/tegra_alc5632.c @@ -102,6 +102,7 @@ static const struct snd_soc_dapm_widget tegra_alc5632_dapm_widgets[] = { SND_SOC_DAPM_SPK("Int Spk", NULL), SND_SOC_DAPM_HP("Headset Stereophone", NULL), SND_SOC_DAPM_MIC("Headset Mic", NULL), + SND_SOC_DAPM_MIC("Digital Mic", NULL), }; static const struct snd_kcontrol_new tegra_alc5632_controls[] = { -- 1.7.3.4

2 1

Re: [alsa-devel] [PATCH v5 1/2] mxs-dma : move the mxs dma.h to a more common place
by Mark Brown 13 Feb '12

13 Feb '12

On Mon, Feb 13, 2012 at 01:25:55PM +0800, Huang Shijie wrote: > Move the header to a more common place. > The mxs dma engine is not only used in mx23/mx28, but also used > in mx50/mx6q. It will also be used in the future chips. Acked-by: Mark Brown <broonie(a)opensource.wolfsonmicro.com>

1 0