June 2016 - Alsa-devel - mailman.alsa-project.org

[alsa-devel] [RESEND PATCH v3 0/2] ASoC: da7219: Convert driver to use generic FW functions
by Adam Thomson 21 Jun '16

21 Jun '16

This patch set converts the da7219 codec driver to use device/fwnode functions to access properties, instead of the DT only of_* functions, allowing ACPI to be used as well. The DT bindings for da7219 have a device node for the main codec properties, and a named child node (da7219_aad), which contains all of the accessory detection related properties for the device. ACPI also supports this kind of FW hierarchy (data only sub-nodes), but some support in the kernel needs to be added to take make use of this in driver code. The first patch adds functions to allow searching for a named child node of a device, for both DT and ACPI, and the second patch updates the codec driver to use the standard device/fwnode calls, including this new function. These changes are based on the v4.7-rc3 kernel. Changes in v3: - Use of_node_cmp() in device_get_named_child_node() to match DT node. Changes in v2: - Rebase to v4.7-rc1 - Small updates to codec patch based on previous reviewer comments Adam Thomson (2): device property: Add function to search for named child of device ASoC: da7219: Convert driver to use generic device/fwnode functions drivers/base/property.c | 28 ++++++++++++ include/acpi/acpi_bus.h | 7 +++ include/linux/acpi.h | 6 +++ include/linux/of.h | 14 +++--- include/linux/property.h | 3 ++ sound/soc/codecs/da7219-aad.c | 103 +++++++++++++++++++++--------------------- sound/soc/codecs/da7219.c | 34 +++++++------- 7 files changed, 119 insertions(+), 76 deletions(-) -- 1.9.3

5 13

[alsa-devel] [PATCH] gcc6 reporting error building alsa-tools on PowerPC
by Michel Normand 21 Jun '16

21 Jun '16

Hello there, While trying to build alsa-tools with gcc6, many reported error that are solved by proposed patch. I do not know if sending to this mailing list is the correct way to provide it to you. Michel Normand (1): gcc6 narrowing error hdspmixer/src/channelmap.cxx | 158 +++++++++++++++++++++---------------------- us428control/Cus428Midi.cc | 30 ++++---- 2 files changed, 94 insertions(+), 94 deletions(-) -- 1.9.1

3 3

[alsa-devel] [PATCH] INSTALL: update text and drop reference to Hg
by Henrik Austad 21 Jun '16

21 Jun '16

This is really just nitpick, but it annoyed me for a few seconds, so I thought I'd just fix it. In d7534b2ceec7 (hgcompile -> gitcompile) the filename was updated but INSTALL was not, leaving outdated docs. Signed-off-by: Henrik Austad <henrik(a)austad.us> --- INSTALL | 15 ++++++++++----- 1 file changed, 10 insertions(+), 5 deletions(-) diff --git a/INSTALL b/INSTALL index 47086e3..64f3d09 100644 --- a/INSTALL +++ b/INSTALL @@ -11,13 +11,19 @@ For installation you can use these commands: make install -Compilation from HG sources +Compilation from Git-sources --------------------------- -You need also GNU packages automake and libtool installed in your system -to compile HG (Mercurial) sources of alsa-lib package. +Requirements: + * automake + * libtool -For compilation you can use these commands: +To compile alsa-lib from source: + + ./gitcompile + +If you do not want to use the supplied gitcompile-script, you can +compile alsa-lib manually by using these steps: libtoolize --force --copy --automake aclocal @@ -27,7 +33,6 @@ For compilation you can use these commands: ./configure make -The included hgcompile script does this job for you. Note: Some automake packages have missing aclocal program. Use newer version in the case. -- 2.1.4 -- To unsubscribe from this list: send the line "unsubscribe alsa-devel" in

2 1

Re: [alsa-devel] 答复: [PATCH 1/1] sound: Fix compile error of seq_device.c
by Takashi Iwai 21 Jun '16

21 Jun '16

On Tue, 21 Jun 2016 10:48:30 +0200, 高峰 wrote: > > The lastest CentOS7 platform, and the gcc version is gcc version 4.8.5 > 20150623 (Red Hat 4.8.5-4) (GCC). > It could pass compilation after append the lost semicolon. > > from sound/core/seq/seq_device.c:39: > include/linux/init.h:216:2: error: expected ‘,’ or ‘;’ before ‘static’ > static exitcall_t __exitcall_##fn __exit_call = fn > ^ > include/linux/init.h:279:24: note: in expansion of macro ‘__exitcall’ > #define module_exit(x) __exitcall(x); > ^ > sound/core/seq/seq_device.c:315:1: note: in expansion of macro > ‘module_exit’ > module_exit(alsa_seq_device_exit) > ^ > make[3]: *** [sound/core/seq/seq_device.o] Error 1 > make[2]: *** [sound/core/seq] Error 2 > make[1]: *** [sound/core] Error 2 > make: *** [sound] Error 2 It's a RH specific issue. The upstream code has a different definition of module_init(), thus no such an error would occur. Note that I'm fine to apply the patch, it's a trivial change. But you need to give the clear reason why to apply it. In this case, it's no fault of the upstream code. But if it would make someone's life a bit easier, it's OK to apply such a change. That being said, please resubmit the patch with a more explanation. thanks, Takashi > > -----邮件原件----- > 发件人: Takashi Iwai [mailto:tiwai@suse.de] > 发送时间: 2016年6月21日 16:45 > 收件人: fgao(a)ikuai8.com > 抄送: alsa-devel(a)alsa-project.org; perex(a)perex.cz; linux-kernel(a)vger.kernel. > org; gfree.wind(a)gmail.com > 主题: Re: [PATCH 1/1] sound: Fix compile error of seq_device.c > > On Tue, 21 Jun 2016 10:34:25 +0200, > <fgao(a)ikuai8.com> wrote: > > > > From: Gao Feng <fgao(a)ikuai8.com> > > > > Signed-off-by: Gao Feng <fgao(a)ikuai8.com> > > What compile error did you get? > > > Takashi > > > --- > > sound/core/seq/seq_device.c | 4 ++-- > > 1 file changed, 2 insertions(+), 2 deletions(-) > > > > diff --git a/sound/core/seq/seq_device.c b/sound/core/seq/seq_device.c > > index c4acf17..4e859e4 100644 > > --- a/sound/core/seq/seq_device.c > > +++ b/sound/core/seq/seq_device.c > > @@ -311,5 +311,5 @@ static void __exit alsa_seq_device_exit(void) > > bus_unregister(&snd_seq_bus_type); > > } > > > > -subsys_initcall(alsa_seq_device_init) > > -module_exit(alsa_seq_device_exit) > > +subsys_initcall(alsa_seq_device_init); > > +module_exit(alsa_seq_device_exit); > > -- > > 1.9.1 > > > > > > > > > > > > >

2 5

[alsa-devel] [PATCH RFC 0/6] Sound support for Exynos5433 TM2(E) boards
by Sylwester Nawrocki 21 Jun '16

21 Jun '16

This patch series adds sound supoort for the Exynos 5433 based TM2(E) boards. It includes minimal drivers for the Low Power Audio Subsystem (LPASS) and the MAX98504 class D speaker amplifier as well as the actual asoc machine driver. Inha Song (2): ASoC: samsung: Add Samsung Low Power Audio Subsystem driver ASoC: samsung: Add machine driver for Exynos5433 based TM2 board Sylwester Nawrocki (4): ASoC: samsung: Add DT bindings documentation for LPASS ASoC: max98504: Add max98504 speaker amplifier driver ASoC: Add DT bindings documentation for max98504 amplifier ASoC: samsung: Add DT bindings documentation for TM2 sound subsystem .../devicetree/bindings/sound/max98504.txt | 44 ++ .../bindings/sound/samsung,exynos5433-lpass.txt | 8 + .../bindings/sound/samsung,tm2-wm5110.txt | 39 ++ sound/soc/codecs/Kconfig | 4 + sound/soc/codecs/Makefile | 2 + sound/soc/codecs/max98504.c | 241 +++++++++ sound/soc/codecs/max98504.h | 94 ++++ sound/soc/samsung/Kconfig | 13 + sound/soc/samsung/Makefile | 4 + sound/soc/samsung/lpass.c | 162 ++++++ sound/soc/samsung/lpass.h | 47 ++ sound/soc/samsung/tm2_wm5110.c | 553 +++++++++++++++++++++ 12 files changed, 1211 insertions(+) create mode 100644 Documentation/devicetree/bindings/sound/max98504.txt create mode 100644 Documentation/devicetree/bindings/sound/samsung,exynos5433-lpass.txt create mode 100644 Documentation/devicetree/bindings/sound/samsung,tm2-wm5110.txt create mode 100644 sound/soc/codecs/max98504.c create mode 100644 sound/soc/codecs/max98504.h create mode 100644 sound/soc/samsung/lpass.c create mode 100644 sound/soc/samsung/lpass.h create mode 100644 sound/soc/samsung/tm2_wm5110.c -- 1.9.1

5 27

[alsa-devel] [PATCH 1/1] sound: Fix one compile error of seq_device.c
by fgao＠ikuai8.com 21 Jun '16

21 Jun '16

From: Gao Feng <fgao(a)ikuai8.com> The gcc reports the following compile error on CentOS7. include/linux/init.h:216:2: error: expected ',' or ';' before 'static' static exitcall_t __exitcall_##fn __exit_call = fn ^ include/linux/init.h:279:24: note: in expansion of macro '__exitcall' #define module_exit(x) __exitcall(x); ^ sound/core/seq/seq_device.c:315:1: note: in expansion of macro 'module_exit' module_exit(alsa_seq_device_exit) ^ make[3]: *** [sound/core/seq/seq_device.o] Error 1 make[2]: *** [sound/core/seq] Error 2 make[1]: *** [sound/core] Error 2 make: *** [sound] Error 2 Signed-off-by: Gao Feng <fgao(a)ikuai8.com> --- sound/core/seq/seq_device.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/sound/core/seq/seq_device.c b/sound/core/seq/seq_device.c index c4acf17..4e859e4 100644 --- a/sound/core/seq/seq_device.c +++ b/sound/core/seq/seq_device.c @@ -311,5 +311,5 @@ static void __exit alsa_seq_device_exit(void) bus_unregister(&snd_seq_bus_type); } -subsys_initcall(alsa_seq_device_init) -module_exit(alsa_seq_device_exit) +subsys_initcall(alsa_seq_device_init); +module_exit(alsa_seq_device_exit); -- 1.9.1

1 0

[alsa-devel] [PATCH 1/1] sound: Fix compile error of seq_device.c
by fgao＠ikuai8.com 21 Jun '16

21 Jun '16

From: Gao Feng <fgao(a)ikuai8.com> Signed-off-by: Gao Feng <fgao(a)ikuai8.com> --- sound/core/seq/seq_device.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/sound/core/seq/seq_device.c b/sound/core/seq/seq_device.c index c4acf17..4e859e4 100644 --- a/sound/core/seq/seq_device.c +++ b/sound/core/seq/seq_device.c @@ -311,5 +311,5 @@ static void __exit alsa_seq_device_exit(void) bus_unregister(&snd_seq_bus_type); } -subsys_initcall(alsa_seq_device_init) -module_exit(alsa_seq_device_exit) +subsys_initcall(alsa_seq_device_init); +module_exit(alsa_seq_device_exit); -- 1.9.1

2 1

[alsa-devel] [PATCH] ALSA: hda - Remove compilation warning
by Helen Koike 21 Jun '16

21 Jun '16

Remove the warning: warning: ‘err’ may be used uninitialized in this function [-Wmaybe-uninitialized] Signed-off-by: Helen Koike <helen.koike(a)collabora.co.uk> --- sound/hda/hdac_regmap.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sound/hda/hdac_regmap.c b/sound/hda/hdac_regmap.c index 87041dd..7be6ca1 100644 --- a/sound/hda/hdac_regmap.c +++ b/sound/hda/hdac_regmap.c @@ -279,7 +279,7 @@ static int hda_reg_write(void *context, unsigned int reg, unsigned int val) { struct hdac_device *codec = context; unsigned int verb; - int i, bytes, err; + int i, bytes, err = 0; int pm_lock = 0; if (codec->caps_overwriting) -- 1.9.1

2 1

[alsa-devel] [PATCH] ASoC: intel: fix build when ACPI is not enabled
by Randy Dunlap 21 Jun '16

21 Jun '16

From: Randy Dunlap <rdunlap(a)infradead.org> kconfig tools generate the following warning when CONFIG_ACPI is not enabled: warning: (SND_SOC_INTEL_BYTCR_RT5640_MACH && SND_SOC_INTEL_BYTCR_RT5651_MACH && SND_SOC_INTEL_CHT_BSW_RT5672_MACH && SND_SOC_INTEL_CHT_BSW_RT5645_MACH && SND_SOC_INTEL_CHT_BSW_MAX98090_TI_MACH) selects SND_SST_IPC_ACPI which has unmet direct dependencies (SOUND && !M68K && !UML && SND && SND_SOC && ACPI) causing these build errors: In file included from ../sound/soc/intel/atom/sst/sst_acpi.c:40:0: ../include/acpi/acpi_bus.h:65:20: error: conflicting types for 'acpi_evaluate_dsm' union acpi_object *acpi_evaluate_dsm(acpi_handle handle, const u8 *uuid, In file included from ../sound/soc/intel/atom/sst/sst_acpi.c:31:0: ../include/linux/acpi.h:676:34: note: previous definition of 'acpi_evaluate_dsm' was here static inline union acpi_object *acpi_evaluate_dsm(acpi_handle handle, I am told that ACPI is a requirement for these drivers, so make that explicit. Also end help text sentences with a period. Signed-off-by: Randy Dunlap <rdunlap(a)infradead.org> Cc: Jie Yang <yang.jie(a)linux.intel.com> Cc: Pierre-Louis Bossart <pierre-louis.bossart(a)linux.intel.com> Cc: alsa-devel(a)alsa-project.org --- sound/soc/intel/Kconfig | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) Should SND_SOC_INTEL_SST and possibly other similar drivers get this same change? --- linux-next-20160607.orig/sound/soc/intel/Kconfig +++ linux-next-20160607/sound/soc/intel/Kconfig @@ -128,28 +128,28 @@ config SND_SOC_INTEL_BROADWELL_MACH config SND_SOC_INTEL_BYTCR_RT5640_MACH tristate "ASoC Audio driver for Intel Baytrail and Baytrail-CR with RT5640 codec" - depends on X86 && I2C + depends on X86 && I2C && ACPI select SND_SOC_RT5640 select SND_SST_MFLD_PLATFORM select SND_SST_IPC_ACPI - select SND_SOC_INTEL_SST_MATCH if ACPI + select SND_SOC_INTEL_SST_MATCH help This adds support for ASoC machine driver for Intel(R) Baytrail and Baytrail-CR platforms with RT5640 audio codec. - Say Y if you have such a device + Say Y if you have such a device. If unsure select "N". config SND_SOC_INTEL_BYTCR_RT5651_MACH tristate "ASoC Audio driver for Intel Baytrail and Baytrail-CR with RT5651 codec" - depends on X86 && I2C + depends on X86 && I2C && ACPI select SND_SOC_RT5651 select SND_SST_MFLD_PLATFORM select SND_SST_IPC_ACPI - select SND_SOC_INTEL_SST_MATCH if ACPI + select SND_SOC_INTEL_SST_MATCH help This adds support for ASoC machine driver for Intel(R) Baytrail and Baytrail-CR platforms with RT5651 audio codec. - Say Y if you have such a device + Say Y if you have such a device. If unsure select "N". config SND_SOC_INTEL_CHT_BSW_RT5672_MACH

2 3

[alsa-devel] How does ALSALIB commuciates with low level kernel API
by Chemsi Mehdi 20 Jun '16

20 Jun '16

Dear experts, I am too new in ALSA, trying to read a little bit and understand. I want to underatnd how ALSA userspace API calls kernel space code ? for example when I call snd_pcm_open() which code is called in kernel sound code ? and how the link is made ? via IOCTL/write ? Please clarify Thanks a lot in advance. Mehdi

3 2