May 2015 - Alsa-devel - mailman.alsa-project.org

[alsa-devel] [PATCH] ASoC: codecs-ac97: make selectable in config
by Maciej S. Szmigiero 22 May '15

22 May '15

Make generic ASoC AC'97 CODEC selectable in config. This way this driver can be used for platforms which don't need specialized AC'97 CODEC drivers but which are not directly selectable in config themselves (for example DT based ones). Signed-off-by: Maciej Szmigiero <mail(a)maciej.szmigiero.name> --- a/sound/soc/codecs/Kconfig +++ b/sound/soc/codecs/Kconfig @@ -16,7 +16,7 @@ config SND_SOC_ALL_CODECS select SND_SOC_88PM860X if MFD_88PM860X select SND_SOC_L3 select SND_SOC_AB8500_CODEC if ABX500_CORE - select SND_SOC_AC97_CODEC if SND_SOC_AC97_BUS + select SND_SOC_AC97_CODEC select SND_SOC_AD1836 if SPI_MASTER select SND_SOC_AD193X_SPI if SPI_MASTER select SND_SOC_AD193X_I2C if I2C @@ -212,8 +212,9 @@ config SND_SOC_AB8500_CODEC tristate config SND_SOC_AC97_CODEC - tristate + tristate "Build generic ASoC AC97 CODEC driver" select SND_AC97_CODEC + select SND_SOC_AC97_BUS config SND_SOC_AD1836 tristate

3 10

Re: [alsa-devel] [PATCH v2 2/3] ASoC: zx: Add zx296702 SPDIF support
by Mark Brown 22 May '15

22 May '15

On Wed, May 06, 2015 at 08:38:04PM +0800, Jun Nie wrote: > Add driver for zx296702 SPDIF controller This all seems fine apart from the fact that you're adding a new DT binding with no binding documentation - all new DT binndings require binnding documentation.

1 0

Re: [alsa-devel] [PATCH v2 1/3] ASoC: zx: Add ZTE zx296702 pcm support
by Mark Brown 22 May '15

22 May '15

On Wed, May 06, 2015 at 08:38:03PM +0800, Jun Nie wrote: > +static const struct snd_pcm_hardware snd_zx_hardware = { > + .info = SNDRV_PCM_INFO_MMAP | > + SNDRV_PCM_INFO_MMAP_VALID | > + SNDRV_PCM_INFO_INTERLEAVED | > + SNDRV_PCM_INFO_PAUSE | > + SNDRV_PCM_INFO_RESUME | > + SNDRV_PCM_INFO_NO_PERIOD_WAKEUP, > + .period_bytes_min = 32, > + .period_bytes_max = 16 * 1024, > + .periods_min = 2, > + .periods_max = 32, > + .buffer_bytes_max = 64 * 1024, > +}; As I said last time I'm not sure why you are manually defining these - the capabilities of the DMA controller should be being enumerated from the DMA controller driver. See dmaengine_pcm_set_runtime_hwparams().

1 0

[alsa-devel] how to ask you to write a new ALSA driver
by jean-noël chardron 22 May '15

22 May '15

hello, Last week I got a Komplet Audio 6 from Native intruments. The driver exist in ALSA driver for this king of interface audio (snd-usb-audio) (thanks for the team who write this) but for the model where Id Vendor is 0x17cc and Id product is 0x1000. The KA6 that I got has not the same ID product (0x1001) therefore I don't have any device capture even with the driver snd-usb-audio. The challenge is to write the modification for this new model. Who could do that ? If necessary I could send log, compile kernel source and so on. thanks, Jean-noel

2 3

[alsa-devel] [PATCH] ASoC: qcom: remove incorrect dependencies
by Arnd Bergmann 22 May '15

22 May '15

Compile-tests show a warning for the newly added SND_SOC_STORM symbol: warning: (SND_SOC_STORM) selects SND_SOC_LPASS_CPU which has unmet direct dependencies (SOUND && !M68K && !UML && SND && SND_SOC && SND_SOC_QCOM) The problem is that it can be selected for COMPILE_TEST on non-QCOM builds, but the symbols it selects have a dependency. Dropping the dependencies makes it work without warnings and no other side-effects, because these are not user-visible. Signed-off-by: Arnd Bergmann <arnd(a)arndb.de> Fixes: f380dd3f3cd ("ASoC: qcom: Add ability to build QCOM drivers") diff --git a/sound/soc/qcom/Kconfig b/sound/soc/qcom/Kconfig index 5f58e4f1bca9..b07f183fc47f 100644 --- a/sound/soc/qcom/Kconfig +++ b/sound/soc/qcom/Kconfig @@ -6,12 +6,10 @@ config SND_SOC_QCOM config SND_SOC_LPASS_CPU tristate - depends on SND_SOC_QCOM select REGMAP_MMIO config SND_SOC_LPASS_PLATFORM tristate - depends on SND_SOC_QCOM select REGMAP_MMIO config SND_SOC_STORM

3 3

[alsa-devel] [PATCH] ASoC: skip legacy dai naming if dai driver has all the information
by Srinivas Kandagatla 22 May '15

22 May '15

Original issue is that the id field in the dai is not same as the id in dai_driver when dai driver count == 1. This is due to the legacy dai naming check, which could possibly cause issues if the audio drivers written in assumption that dai->id would be always equal to dai_driver->id. This assumption is true only if the dai driver count is greater than 1, and false if dai driver count is 1. On Qcom Lpass driver we hit such issue while adding support to apq8016. The code path which falls back to legacy naming for cases where num_dai == 1 does not check if there is any valid information in the dai_driver. This patch fixes that by checking if the dai_driver has valid id and name before falling back to legacy dai naming Although the drivers can work around this issue by only using dai->driver->id, but this patch attempts to fix the actual issue. Suggested-by: Lars-Peter Clausen <lars(a)metafoo.de> Signed-off-by: Srinivas Kandagatla <srinivas.kandagatla(a)linaro.org> --- sound/soc/soc-core.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/sound/soc/soc-core.c b/sound/soc/soc-core.c index 2373252..7d028e8 100644 --- a/sound/soc/soc-core.c +++ b/sound/soc/soc-core.c @@ -2599,7 +2599,8 @@ static int snd_soc_register_dais(struct snd_soc_component *component, * the same naming style even though those DAIs are not * component-less anymore. */ - if (count == 1 && legacy_dai_naming) { + if (count == 1 && legacy_dai_naming && + (dai_drv[i].id == 0 || dai_drv[i].name == NULL)) { dai->name = fmt_single_name(dev, &dai->id); } else { dai->name = fmt_multiple_name(dev, &dai_drv[i]); -- 1.9.1

3 2

[alsa-devel] Assert in pcm_params.c
by Alan Horstmann 21 May '15

21 May '15

Hi, The following assert is being hit in pcm_params.c: "pcm_params.c:2249: snd1_pcm_hw_params_slave: Assertion `err >= 0' failed." This is from a developer using Portaudio in his own application; I have yet to ascertain full details, but it is trying successive sample rates to see which are valid. Does this point to a flaw in the configuration or possibly a bug in Alsa-lib or can it occur just as a result of misuse of the Alsa API? Regards Alan

3 21

[alsa-devel] [RFC PATCH 00/14] ASoC: qcom: add support to apq8016 audio
by Srinivas Kandagatla 21 May '15

21 May '15

Hi All, This patchset adds apq8016 audio support into lpass driver. Existing Lpass driver can not be used as-it-is for apq8016 as it contains code specific to ipq806x. Also the driver only supports single i2s port, single dma channel and single bitclk control. APQ8016 has 4 MI2S( Primary, Secondary, Tertiary, Quaternary) which can be routed to internal wcd codec or external codecs. This routing is controlled by 2 mux registers. This patch series firstly re-organizes the lpass driver such that the SOC specific bits are moved away from the driver. And secondly the SOC specifics are now passed as lpass variant data which would include various register offsets, dma channel allocations and SOC specific clock handling. Finally the patchset add apq8016 lpass and machine driver. This patchset also has two trivial cleanup patches which are to do with redundant checks and removing unnecessary header files. All these patches are tested for HDMI audio via adv7533 bridge and Analog audio on APQ8016-SBC and msm8916-mtp boards. I dont have access to ipq806x boards to test these patches. This is very first version of the patches which was developed with very mimimal/no access to IP documentation. I would like to get your opinon on the over all approch. Kenneth/Patrick, Could you please try these patches on storm board? Thanks, srini Srinivas Kandagatla (14): ASoC: qcom: Remove redundant error check. ASoC: qcom: remove unnecessary header files ASoC: qcom: move ipq806x specific bits out of lpass driver. ASoC: qcom: remove hardcoded i2s port number ASoC: qcom: remove hardcoded dma channel ASoC: qcom: support bitclk and osrclk per i2s port ASoC: qcom: add no osr clk flag to lpass variant ASoC: qcom: add dma channel control offset to variant data ASoC: qcom: Add ability to handle interrupts per dma channel ASoC: qcom: add bit map to track static dma channel allocations ASoC: qcom: Add apq8016 lpass driver support ASoC: qcom: add apq8016 sound card support ASoC: qcom: Document apq8016 bindings. ASoC: qcom: document apq8016 machine driver bindings .../bindings/sound/qcom,apq8016-machine.txt | 61 ++++++ .../devicetree/bindings/sound/qcom,lpass-cpu.txt | 13 +- sound/soc/qcom/Kconfig | 25 ++- sound/soc/qcom/Makefile | 5 + sound/soc/qcom/apq8016.c | 214 ++++++++++++++++++ sound/soc/qcom/lpass-apq8016.c | 243 +++++++++++++++++++++ sound/soc/qcom/lpass-cpu.c | 234 ++++++++++---------- sound/soc/qcom/lpass-ipq806x.c | 95 ++++++++ sound/soc/qcom/lpass-lpaif-ipq806x.h | 172 --------------- sound/soc/qcom/lpass-lpaif-reg.h | 167 ++++++++++++++ sound/soc/qcom/lpass-platform.c | 197 +++++++++++------ sound/soc/qcom/lpass.h | 54 ++++- 12 files changed, 1121 insertions(+), 359 deletions(-) create mode 100644 Documentation/devicetree/bindings/sound/qcom,apq8016-machine.txt create mode 100644 sound/soc/qcom/apq8016.c create mode 100644 sound/soc/qcom/lpass-apq8016.c create mode 100644 sound/soc/qcom/lpass-ipq806x.c delete mode 100644 sound/soc/qcom/lpass-lpaif-ipq806x.h create mode 100644 sound/soc/qcom/lpass-lpaif-reg.h -- 1.9.1

4 87

[alsa-devel] prealloc_buffer_size and buffer_bytes_max
by Peter Rosin 21 May '15

21 May '15

Hi! I got my hopes up when I read the commit message for c14e2591bf54 ASoC: atmel-pcm-dma: increase buffer_bytes_max. Quoting it: atmel-pcm-dma is not limited to a buffer size of 64kB like atmel-pcm-pdc. Increase buffer_bytes_max to 512kB to allow for higher bit rates (i.e. 32bps at 192kHz) to work correctly. By default, keep the prealloc at 64kB. However, as I (think I) request a bigger buffer it still caps out at 64kB. I'm using the latency argument of snd_pcm_set_params to control the buffer: snd_pcm_set_params(pcm, SND_PCM_FORMAT_S32_LE, SND_PCM_ACCESS_RW_INTERLEAVED, 2, /* channels */ 250000, /* rate */ 0, /* do not resample */ 90000); /* latency in us */ But snd_pcm_hw_params_get_buffer_size "only" returns 8192 frames (64kB) even if I request 9us * 250kHz * 2 * 4 = 180kB. If I change the prealloc from 64kB to 256kB I get a bigger buffer (and it works better too!). Admittedly I backported this patch on top of the linux-3.18-at91 branch from the Atmel git repo, so there might be some support missing that has gone in after 3.18? Or have I completely misunderstood, and these are unrelated buffers? Any insight in how I can get a big enough buffer without hacking the prealloc is appreciated! Cheers, Peter

2 3

[alsa-devel] snd-hda-intel : issues with mic boost on ALC3236
by Simon Derr 21 May '15

21 May '15

Hello, I'm having issues with the internal microphone on an Asus R553 (or S551) laptop. With the boost set to zero the microphone works but the level of the recording is very low. If I try another boost setting I don't get any signal anymore. I have uploaded alsa-info data here : http://www.alsa-project.org/db/?f=55b7fb0b4998757d099addae0a411e6a7cebc079 This is on a Linux 4.0 kernel. Any help is welcome, Regards, Simon

4 13