ASoC: neo1973_wm8753: Remove scenario management code.
Subsystems (4)
PATCH 1/7 ASoC: neo1973_wm8753: Remove scenario management code.
It has been proven to be inflexible to do scenario management in kernel space.
Since actual neo1973 board support has not been merged in mainline and this patch has been in the neo1973 tree for some time now it should be safe to remove this functionality without breaking existing userspace.
--- sound/soc/samsung/neo1973_wm8753.c | 142 +---------------------------------- 1 files changed, 5 insertions(+), 137 deletions(-)
sound/soc/samsung/neo1973_wm8753.c +5 -137
@@ -37,17 +37,6 @@#include "dma.h" #include "s3c24xx-i2s.h" -/* define the scenarios */ -#define NEO_AUDIO_OFF 0 -#define NEO_GSM_CALL_AUDIO_HANDSET 1 -#define NEO_GSM_CALL_AUDIO_HEADSET 2 -#define NEO_GSM_CALL_AUDIO_BLUETOOTH 3 -#define NEO_STEREO_TO_SPEAKERS 4 -#define NEO_STEREO_TO_HEADPHONES 5 -#define NEO_CAPTURE_HANDSET 6 -#define NEO_CAPTURE_HEADSET 7 -#define NEO_CAPTURE_BLUETOOTH 8 -static struct snd_soc_card neo1973;static struct i2c_client *i2c;
@@ -224,113 +213,6 @@ static struct snd_soc_ops neo1973_voice_ops = { .hw_free = neo1973_voice_hw_free, }; -static int neo1973_scenario; - -static int neo1973_get_scenario (struct snd_kcontrol *kcontrol, -struct snd_ctl_elem_value *ucontrol) -{ - ucontrol->value.integer.value[0 ] = neo1973_scenario; -return 0 ; -} - -static int set_scenario_endpoints (struct snd_soc_codec *codec,int scenario) -{ -struct snd_soc_dapm_context *dapm = &codec->dapm; - -pr_debug ("Entered %s\n" , __func__); - -switch (neo1973_scenario) { -case NEO_AUDIO_OFF : -snd_soc_dapm_disable_pin (dapm,"Audio Out" ); -snd_soc_dapm_disable_pin (dapm,"GSM Line Out" ); -snd_soc_dapm_disable_pin (dapm,"GSM Line In" ); -snd_soc_dapm_disable_pin (dapm,"Headset Mic" ); -snd_soc_dapm_disable_pin (dapm,"Call Mic" ); -break ; -case NEO_GSM_CALL_AUDIO_HANDSET : -snd_soc_dapm_enable_pin (dapm,"Audio Out" ); -snd_soc_dapm_enable_pin (dapm,"GSM Line Out" ); -snd_soc_dapm_enable_pin (dapm,"GSM Line In" ); -snd_soc_dapm_disable_pin (dapm,"Headset Mic" ); -snd_soc_dapm_enable_pin (dapm,"Call Mic" ); -break ; -case NEO_GSM_CALL_AUDIO_HEADSET : -snd_soc_dapm_enable_pin (dapm,"Audio Out" ); -snd_soc_dapm_enable_pin (dapm,"GSM Line Out" ); -snd_soc_dapm_enable_pin (dapm,"GSM Line In" ); -snd_soc_dapm_enable_pin (dapm,"Headset Mic" ); -snd_soc_dapm_disable_pin (dapm,"Call Mic" ); -break ; -case NEO_GSM_CALL_AUDIO_BLUETOOTH : -snd_soc_dapm_disable_pin (dapm,"Audio Out" ); -snd_soc_dapm_enable_pin (dapm,"GSM Line Out" ); -snd_soc_dapm_enable_pin (dapm,"GSM Line In" ); -snd_soc_dapm_disable_pin (dapm,"Headset Mic" ); -snd_soc_dapm_disable_pin (dapm,"Call Mic" ); -break ; -case NEO_STEREO_TO_SPEAKERS : -snd_soc_dapm_enable_pin (dapm,"Audio Out" ); -snd_soc_dapm_disable_pin (dapm,"GSM Line Out" ); -snd_soc_dapm_disable_pin (dapm,"GSM Line In" ); -snd_soc_dapm_disable_pin (dapm,"Headset Mic" ); -snd_soc_dapm_disable_pin (dapm,"Call Mic" ); -break ; -case NEO_STEREO_TO_HEADPHONES : -snd_soc_dapm_enable_pin (dapm,"Audio Out" ); -snd_soc_dapm_disable_pin (dapm,"GSM Line Out" ); -snd_soc_dapm_disable_pin (dapm,"GSM Line In" ); -snd_soc_dapm_disable_pin (dapm,"Headset Mic" ); -snd_soc_dapm_disable_pin (dapm,"Call Mic" ); -break ; -case NEO_CAPTURE_HANDSET : -snd_soc_dapm_disable_pin (dapm,"Audio Out" ); -snd_soc_dapm_disable_pin (dapm,"GSM Line Out" ); -snd_soc_dapm_disable_pin (dapm,"GSM Line In" ); -snd_soc_dapm_disable_pin (dapm,"Headset Mic" ); -snd_soc_dapm_enable_pin (dapm,"Call Mic" ); -break ; -case NEO_CAPTURE_HEADSET : -snd_soc_dapm_disable_pin (dapm,"Audio Out" ); -snd_soc_dapm_disable_pin (dapm,"GSM Line Out" ); -snd_soc_dapm_disable_pin (dapm,"GSM Line In" ); -snd_soc_dapm_enable_pin (dapm,"Headset Mic" ); -snd_soc_dapm_disable_pin (dapm,"Call Mic" ); -break ; -case NEO_CAPTURE_BLUETOOTH : -snd_soc_dapm_disable_pin (dapm,"Audio Out" ); -snd_soc_dapm_disable_pin (dapm,"GSM Line Out" ); -snd_soc_dapm_disable_pin (dapm,"GSM Line In" ); -snd_soc_dapm_disable_pin (dapm,"Headset Mic" ); -snd_soc_dapm_disable_pin (dapm,"Call Mic" ); -break ; -default : -snd_soc_dapm_disable_pin (dapm,"Audio Out" ); -snd_soc_dapm_disable_pin (dapm,"GSM Line Out" ); -snd_soc_dapm_disable_pin (dapm,"GSM Line In" ); -snd_soc_dapm_disable_pin (dapm,"Headset Mic" ); -snd_soc_dapm_disable_pin (dapm,"Call Mic" ); - } - -snd_soc_dapm_sync (dapm); - -return 0 ; -} - -static int neo1973_set_scenario (struct snd_kcontrol *kcontrol, -struct snd_ctl_elem_value *ucontrol) -{ -struct snd_soc_codec *codec =snd_kcontrol_chip (kcontrol); - -pr_debug ("Entered %s\n" , __func__); - -if (neo1973_scenario == ucontrol->value.integer.value[0 ]) -return 0 ; - - neo1973_scenario = ucontrol->value.integer.value[0 ]; -set_scenario_endpoints (codec, neo1973_scenario); -return 1 ; -} -static u8 lm4857_regs[4 ] = {0x00 ,0x40 ,0x80 ,0xC0 };static void lm4857_write_regs (void )
@@ -454,22 +336,6 @@ static const struct soc_enum lm4857_mode_enum[] = { SOC_ENUM_SINGLE_EXT(ARRAY_SIZE(lm4857_mode), lm4857_mode), }; -static const char *neo_scenarios[] = { -"Off" , -"GSM Handset" , -"GSM Headset" , -"GSM Bluetooth" , -"Speakers" , -"Headphones" , -"Capture Handset" , -"Capture Headset" , -"Capture Bluetooth" -}; - -static const struct soc_enum neo_scenario_enum[] = { -SOC_ENUM_SINGLE_EXT (ARRAY_SIZE (neo_scenarios), neo_scenarios), -}; - static const DECLARE_TLV_DB_SCALE(stereo_tlv, -4050, 150, 0); static const DECLARE_TLV_DB_SCALE(mono_tlv, -3450, 150, 0);
@@ -482,8 +348,6 @@ static const struct snd_kcontrol_new wm8753_neo1973_controls[] = { lm4857_get_reg, lm4857_set_reg, mono_tlv),SOC_ENUM_EXT ("Amp Mode" , lm4857_mode_enum[0 ], lm4857_get_mode, lm4857_set_mode), -SOC_ENUM_EXT ("Neo Mode" , neo_scenario_enum[0 ], - neo1973_get_scenario, neo1973_set_scenario),SOC_SINGLE_EXT ("Amp Spk 3D Playback Switch" ,LM4857_LVOL ,5 ,1 ,0 , lm4857_get_reg, lm4857_set_reg), SOC_SINGLE_EXT("Amp HP 3d Playback Switch", LM4857_RVOL, 5, 1, 0,
@@ -520,7 +384,11 @@ static int neo1973_wm8753_init(struct snd_soc_pcm_runtime *rtd) ARRAY_SIZE(wm8753_dapm_widgets));/* set endpoints to default mode */ -set_scenario_endpoints (codec,NEO_AUDIO_OFF ); +snd_soc_dapm_disable_pin (codec,"Audio Out" ); +snd_soc_dapm_disable_pin (codec,"GSM Line Out" ); +snd_soc_dapm_disable_pin (codec,"GSM Line In" ); +snd_soc_dapm_disable_pin (codec,"Headset Mic" ); +snd_soc_dapm_disable_pin (codec,"Call Mic" );/* add neo1973 specific controls */ err = snd_soc_add_controls(codec, wm8753_neo1973_controls,
Signature · 1 line
1.7.2.3
PATCH 2/7 ASoC: neo1973_wm8753: Move lm4857 specefic code to its own module
This patch moves the code for the lm4857 AMP from the neo1973_wm8753 sound board driver to its own module.
The lm4857 is a generic AMP IC and not specific to the neo1973.
--- sound/soc/codecs/Kconfig | 3 + sound/soc/codecs/Makefile | 2 + sound/soc/codecs/lm4857.c | 236 ++++++++++++++++++++++++++++++++++++ sound/soc/codecs/lm4857.h | 23 ++++ sound/soc/samsung/Kconfig | 1 + sound/soc/samsung/lm4857.h | 32 ----- sound/soc/samsung/neo1973_wm8753.c | 195 +----------------------------- 7 files changed, 267 insertions(+), 225 deletions(-) create mode 100644 sound/soc/codecs/lm4857.c create mode 100644 sound/soc/codecs/lm4857.h delete mode 100644 sound/soc/samsung/lm4857.h
sound/soc/codecs/Kconfig +3 -0
@@ -338,6 +338,9 @@ config SND_SOC_WM9713 tristate # Amp +config SND_SOC_LM4857 + tristate + config SND_SOC_MAX9877 tristate
sound/soc/codecs/Makefile +2 -0
@@ -75,6 +75,7 @@ snd-soc-wm-hubs-objs := wm_hubs.o snd-soc-jz4740-codec-objs := jz4740.o # Amp +snd-soc-lm4857-objs := lm4857.o snd-soc-max9877-objs := max9877.o snd-soc-tpa6130a2-objs := tpa6130a2.o snd-soc-wm2000-objs := wm2000.o
@@ -157,6 +158,7 @@ obj-$(CONFIG_SND_SOC_WM9713) += snd-soc-wm9713.o obj-$(CONFIG_SND_SOC_WM_HUBS) += snd-soc-wm-hubs.o # Amp +obj-$(CONFIG_SND_SOC_LM4857) += snd-soc-lm4857.o obj-$(CONFIG_SND_SOC_MAX9877) += snd-soc-max9877.o obj-$(CONFIG_SND_SOC_TPA6130A2) += snd-soc-tpa6130a2.o obj-$(CONFIG_SND_SOC_WM2000) += snd-soc-wm2000.o
sound/soc/codecs/lm4857.c new file +236 -0
236 lines not on this page · raw message
sound/soc/codecs/lm4857.h new file +23 -0
@@ -0,0 +1,23 @@ +/* +* lm4857.h -- ALSA Soc Audio Layer +* +* Copyright 2007 Wolfson Microelectronics PLC. +* Author: Graeme Gregory +* [email protected] or [email protected] +* +* This program is free software; you can redistribute it and/or modify it +* under the terms of the GNU General Public License as published by the +* Free Software Foundation; either version 2 of the License, or (at your +* option) any later version. +* +* Revision history +* 18th Jun 2007 Initial version. +*/ + +#ifndef LM4857_H_ +#define LM4857_H_ + +int lm4857_add_controls (struct snd_soc_codec *codec); + +#endif /*LM4857_H_*/ +
sound/soc/samsung/Kconfig +1 -0
@@ -39,6 +39,7 @@ config SND_SOC_SAMSUNG_NEO1973_WM8753 depends on SND_SOC_SAMSUNG && MACH_NEO1973_GTA01 select SND_S3C24XX_I2S select SND_SOC_WM8753 + select SND_SOC_LM4857 help Say Y if you want to add support for SoC audio on smdk2440 with the WM8753.
sound/soc/samsung/lm4857.h deleted +0 -32
@@ -1,32 +0,0 @@ -/* -* lm4857.h -- ALSA Soc Audio Layer -* -* Copyright 2007 Wolfson Microelectronics PLC. -* Author: Graeme Gregory -* [email protected] or [email protected] -* -* This program is free software; you can redistribute it and/or modify it -* under the terms of the GNU General Public License as published by the -* Free Software Foundation; either version 2 of the License, or (at your -* option) any later version. -* -* Revision history -* 18th Jun 2007 Initial version. -*/ - -#ifndef LM4857_H_ -#define LM4857_H_ - -/* The register offsets in the cache array */ -#define LM4857_MVOL 0 -#define LM4857_LVOL 1 -#define LM4857_RVOL 2 -#define LM4857_CTRL 3 - -/* the shifts required to set these bits */ -#define LM4857_3D 5 -#define LM4857_WAKEUP 5 -#define LM4857_EPGAIN 4 - -#endif /*LM4857_H_*/ -
sound/soc/samsung/neo1973_wm8753.c +2 -193
250 lines not on this page · raw message
Signature · 1 line
1.7.2.3
Re: [PATCH 2/7] ASoC: neo1973_wm8753: Move lm4857 specefic code to its own module
sound/soc/codecs/lm4857.c line 156
Quoted 6 lines · Lars-Peter Clausen
sound/soc/codecs/lm4857.c new file +6
-0+int lm4857_add_controls (struct snd_soc_codec *codec) +{ +return snd_soc_add_controls (codec, lm4857_controls, +ARRAY_SIZE (lm4857_controls)); +} +EXPORT_SYMBOL_GPL (lm4857_add_controls);
If you're moving this into a standalone driver it should be updated to register as a CODEC.
PATCH 3/7 ASoC: codecs: lm4857: Use dev_pm_ops
In reply to Lars-Peter ClausenUse dev_pm_ops instead of legacy I2C power management hooks.
--- sound/soc/codecs/lm4857.c | 15 ++++++++------- 1 files changed, 8 insertions(+), 7 deletions(-)
sound/soc/codecs/lm4857.c +8 -7
@@ -175,9 +175,9 @@ static void lm4857_shutdown(struct i2c_client *client)lm4857_write_regs (); } -#ifdef CONFIG_PM +#ifdef CONFIG_PM_SLEEP -static int lm4857_suspend (struct i2c_client *client,pm_message_t state) +static int lm4857_suspend (struct device *dev) { lm4857.state = lm4857.regs[LM4857_CTRL ] &0xF ;
@@ -187,7 +187,7 @@ static int lm4857_suspend(struct i2c_client *client, pm_message_t state)return 0 ; } -static int lm4857_resume (struct i2c_client *dev) +static int lm4857_resume (struct device *dev) {if (lm4857.state) { lm4857.regs[LM4857_CTRL ] |= (lm4857.state &0x0F );
@@ -196,9 +196,11 @@ static int lm4857_resume(struct i2c_client *dev)return 0 ; } +static SIMPLE_DEV_PM_OPS(lm4857_pm_ops, lm4857_suspend, lm4857_resume); +#define LM4857_PM_OPS (&lm4857_pm_ops) +#else -#define lm4857_suspend NULL -#define lm4857_resume NULL +#define LM4857_PM_OPS NULL#endif static const struct i2c_device_id lm4857_i2c_id[] = {
@@ -210,11 +212,10 @@ static struct i2c_driver lm4857_i2c_driver = { .driver = { .name = "LM4857 I2C Amp", .owner = THIS_MODULE, + .pm = LM4857_PM_OPS, }, .probe = lm4857_probe, .remove = __devexit_p(lm4857_remove), - .suspend = lm4857_suspend, - .resume = lm4857_resume, .shutdown = lm4857_shutdown, .id_table = lm4857_i2c_id, };
Signature · 1 line
1.7.2.3
PATCH 4/7 ASoC: neo1973_gta02_wm8753: Remove lm4853_{set,get}_state
In reply to Lars-Peter ClausenThis patch drops the lm4853_{set,get}_state functions and the "Amp State Switch" control.
Those were noops which existed to maintain alsa state file compatibility. Since the control names have changed due to internal changes in the ASoC core and state file compatibility was broken anyway it makes sense to drop them.
--- sound/soc/samsung/neo1973_gta02_wm8753.c | 55 ++++-------------------------- 1 files changed, 7 insertions(+), 48 deletions(-)
sound/soc/samsung/neo1973_gta02_wm8753.c +7 -48
@@ -194,47 +194,14 @@ static struct snd_soc_ops neo1973_gta02_voice_ops = { .hw_free = neo1973_gta02_voice_hw_free, }; -#define LM4853_AMP 1 -#define LM4853_SPK 2 - -static u8 lm4853_state; - -/* This has no effect, it exists only to maintain compatibility with -* existing ALSA state files. -*/ -static int lm4853_set_state (struct snd_kcontrol *kcontrol, -struct snd_ctl_elem_value *ucontrol) -{ -int val = ucontrol->value.integer.value[0 ]; - -if (val) - lm4853_state |=LM4853_AMP ; -else - lm4853_state &= ~LM4853_AMP ; - -return 0 ; -} - -static int lm4853_get_state (struct snd_kcontrol *kcontrol, -struct snd_ctl_elem_value *ucontrol) -{ - ucontrol->value.integer.value[0 ] = lm4853_state &LM4853_AMP ; - -return 0 ; -} +static int gta02_speaker_enabled;static int lm4853_set_spk (struct snd_kcontrol *kcontrol,struct snd_ctl_elem_value *ucontrol) { -int val = ucontrol->value.integer.value[0 ]; - -if (val) { - lm4853_state |=LM4853_SPK ; -gpio_set_value (GTA02_GPIO_HP_IN ,0 ); - }else { - lm4853_state &= ~LM4853_SPK ; -gpio_set_value (GTA02_GPIO_HP_IN ,1 ); - } + gta02_speaker_enabled = ucontrol->value.integer.value[0 ]; + +gpio_set_value (GTA02_GPIO_HP_IN , !gta02_speaker_enabled);return 0 ; }
@@ -242,14 +209,12 @@ static int lm4853_set_spk(struct snd_kcontrol *kcontrol,static int lm4853_get_spk (struct snd_kcontrol *kcontrol,struct snd_ctl_elem_value *ucontrol) { - ucontrol->value.integer.value[0 ] = (lm4853_state &LM4853_SPK ) >>1 ; - + ucontrol->value.integer.value[0 ] = gta02_speaker_enabled;return 0 ; }static int lm4853_event (struct snd_soc_dapm_widget *w, -struct snd_kcontrol *k, -int event) +struct snd_kcontrol *k,int event) {gpio_set_value (GTA02_GPIO_AMP_SHUT ,SND_SOC_DAPM_EVENT_OFF (event));
@@ -304,13 +269,7 @@ static const struct snd_kcontrol_new wm8753_neo1973_gta02_controls[] = {SOC_DAPM_PIN_SWITCH ("Handset Mic" ),SOC_DAPM_PIN_SWITCH ("Handset Spk" ), -/* This has no effect, it exists only to maintain compatibility with -* existing ALSA state files. -*/ -SOC_SINGLE_EXT ("Amp State Switch" ,6 ,0 ,1 ,0 , - lm4853_get_state, - lm4853_set_state), -SOC_SINGLE_EXT ("Amp Spk Switch" ,7 ,0 ,1 ,0 , +SOC_SINGLE_BOOL_EXT ("Amp Spk Switch" ,0 , lm4853_get_spk, lm4853_set_spk), };
Signature · 1 line
1.7.2.3
PATCH 5/7 ASoC: Samsung: neo1973: Use gpio_request_array to request gpios
In reply to Lars-Peter ClausenUsing gpio_request_array instead of requesting and setting up each gpio by hand makes the code more readable and more compact.
--- sound/soc/samsung/neo1973_gta02_wm8753.c | 36 +++++++---------------------- 1 files changed, 9 insertions(+), 27 deletions(-)
sound/soc/samsung/neo1973_gta02_wm8753.c +9 -27
@@ -370,6 +370,11 @@ static struct snd_soc_card neo1973_gta02 = { .num_links = ARRAY_SIZE(neo1973_gta02_dai), }; +static const struct gpio neo1973_gta02_gpios[] = { + {GTA02_GPIO_HP_IN ,GPIOF_OUT_INIT_HIGH ,"GTA02_HP_IN" }, + {GTA02_GPIO_AMP_SHUT ,GPIOF_OUT_INIT_HIGH ,"GTA02_AMP_SHUT" }, +}; +static struct platform_device *neo1973_gta02_snd_device;static int __init neo1973_gta02_init (void )
@@ -397,37 +402,15 @@ static int __init neo1973_gta02_init(void)if (ret) goto err_unregister_dai; -/* Initialise GPIOs used by amp */ - ret =gpio_request (GTA02_GPIO_HP_IN ,"GTA02_HP_IN" ); + ret =gpio_request_array (neo1973_gta02_gpios, +ARRAY_SIZE (neo1973_gta02_gpios));if (ret) { -pr_err ("gta02_wm8753: Failed to register GPIO %d\n" ,GTA02_GPIO_HP_IN ); +pr_err ("gta02_wm8753: Failed to request gpio\n" ); goto err_del_device; } - ret =gpio_direction_output (GTA02_GPIO_HP_IN ,1 ); -if (ret) { -pr_err ("gta02_wm8753: Failed to configure GPIO %d\n" ,GTA02_GPIO_HP_IN ); - goto err_free_gpio_hp_in; - } - - ret =gpio_request (GTA02_GPIO_AMP_SHUT ,"GTA02_AMP_SHUT" ); -if (ret) { -pr_err ("gta02_wm8753: Failed to register GPIO %d\n" ,GTA02_GPIO_AMP_SHUT ); - goto err_free_gpio_hp_in; - } - - ret =gpio_direction_output (GTA02_GPIO_AMP_SHUT ,1 ); -if (ret) { -pr_err ("gta02_wm8753: Failed to configure GPIO %d\n" ,GTA02_GPIO_AMP_SHUT ); - goto err_free_gpio_amp_shut; - } -return 0 ; -err_free_gpio_amp_shut: -gpio_free (GTA02_GPIO_AMP_SHUT ); -err_free_gpio_hp_in: -gpio_free (GTA02_GPIO_HP_IN ); err_del_device:platform_device_del (neo1973_gta02_snd_device); err_unregister_dai:
@@ -440,10 +423,9 @@ module_init(neo1973_gta02_init); static void __exit neo1973_gta02_exit(void) { +gpio_free_array (neo1973_gta02_gpios,ARRAY_SIZE (neo1973_gta02_gpios));snd_soc_unregister_dai (&neo1973_gta02_snd_device->dev);platform_device_unregister (neo1973_gta02_snd_device); -gpio_free (GTA02_GPIO_HP_IN ); -gpio_free (GTA02_GPIO_AMP_SHUT ); }module_exit (neo1973_gta02_exit);
Signature · 1 line
1.7.2.3
PATCH 6/7 ASoC: Samsung: neo1973_gta02: Fix bluetooth DAI registration
In reply to Lars-Peter ClausenThis patch fixes two issues with the bluethooth DAI registration:
* The DAI has to be registered only after the sound device has been added.
* Currently the DAI is registered with snd_soc_register_dai which causes it to be named after the device it was registered for. Which is in this case the "soc-audio" device. (Ab)use snd_soc_register_dais which causes the DAI to be named after the DAI driver, which is what we want in this case.
--- sound/soc/samsung/neo1973_gta02_wm8753.c | 23 +++++++++++------------ 1 files changed, 11 insertions(+), 12 deletions(-)
sound/soc/samsung/neo1973_gta02_wm8753.c +11 -12
@@ -391,32 +391,31 @@ static int __init neo1973_gta02_init(void)if (!neo1973_gta02_snd_device)return -ENOMEM ; -/* register bluetooth DAI here */ - ret =snd_soc_register_dai (&neo1973_gta02_snd_device->dev, &bt_dai); -if (ret) - goto err_put_device; -platform_set_drvdata (neo1973_gta02_snd_device, &neo1973_gta02); ret =platform_device_add (neo1973_gta02_snd_device); +if (ret) { +platform_device_del (neo1973_gta02_snd_device); +return ret; + } +/* register bluetooth DAI here */ + ret =snd_soc_register_dais (&neo1973_gta02_snd_device->dev, &bt_dai,1 );if (ret) - goto err_unregister_dai; + goto err_unregister_device; ret =gpio_request_array (neo1973_gta02_gpios,ARRAY_SIZE (neo1973_gta02_gpios));if (ret) {pr_err ("gta02_wm8753: Failed to request gpio\n" ); - goto err_del_device; + goto err_unregister_dai; }return 0 ; -err_del_device: -platform_device_del (neo1973_gta02_snd_device); err_unregister_dai:snd_soc_unregister_dai (&neo1973_gta02_snd_device->dev); -err_put_device: -platform_device_put (neo1973_gta02_snd_device); +err_unregister_device: +platform_device_unregister (neo1973_gta02_snd_device);return ret; }module_init (neo1973_gta02_init);
@@ -424,7 +423,7 @@ module_init(neo1973_gta02_init); static void __exit neo1973_gta02_exit(void) {gpio_free_array (neo1973_gta02_gpios,ARRAY_SIZE (neo1973_gta02_gpios)); -snd_soc_unregister_dai (&neo1973_gta02_snd_device->dev); +snd_soc_unregister_dais (&neo1973_gta02_snd_device->dev);platform_device_unregister (neo1973_gta02_snd_device); }module_exit (neo1973_gta02_exit);
Signature · 1 line
1.7.2.3
Re: [PATCH 6/7] ASoC: Samsung: neo1973_gta02: Fix bluetooth DAI registration
Quoted 2 lines · Lars-Peter Clausen
This patch fixes two issues with the bluethooth DAI registration:
* The DAI has to be registered only after the sound device has been added.
This isn't a problem, components in the system can be registered in any order.
Quoted 4 lines
* Currently the DAI is registered with
snd_soc_register_daiwhich causes it to be named after the device it was registered for. Which is in this case the "soc-audio" device. (Ab)usesnd_soc_register_daiswhich causes the DAI to be named after the DAI driver, which is what we want in this case.
This doesn't tie up with your change which...
sound/soc/samsung/neo1973_gta02_wm8753.c static int __init neo1973_gta02_init(void) · line 404
Quoted 10 lines
sound/soc/samsung/neo1973_gta02_wm8753.c +3
-5-/* register bluetooth DAI here */ - ret =snd_soc_register_dai (&neo1973_gta02_snd_device->dev, &bt_dai); -if (ret) - goto err_put_device; +/* register bluetooth DAI here */ + ret =snd_soc_register_dais (&neo1973_gta02_snd_device->dev, &bt_dai,1 );if (ret) - goto err_unregister_dai; + goto err_unregister_device;
...uses the same device in both cases and looking briefly at the code both register functions just use the dev that was passed in. In any case, we clearly shouldn't be applying patches which bodge around the core.
Re: [PATCH 6/7] ASoC: Samsung: neo1973_gta02: Fix bluetooth DAI registration
Quoted 6 lines · Mark Brown
Quoted 2 lines · Lars-Peter Clausen
This patch fixes two issues with the bluethooth DAI registration:
* The DAI has to be registered only after the sound device has been added.This isn't a problem, components in the system can be registered in any order.
By device I mean the soc-core platform device, which has to exist before a dai can be registered with that device.
Quoted 13 lines
Quoted 5 lines
* Currently the DAI is registered with
snd_soc_register_daiwhich causes it to be named after the device it was registered for. Which is in this case the "soc-audio" device. (Ab)usesnd_soc_register_daiswhich causes the DAI to be named after the DAI driver, which is what we want in this case.This doesn't tie up with your change which...
Quoted 4 lines
sound/soc/samsung/neo1973_gta02_wm8753.c +0
-4-/* register bluetooth DAI here */ - ret =snd_soc_register_dai (&neo1973_gta02_snd_device->dev, &bt_dai); -if (ret) - goto err_put_device;
Quoted 8 lines
sound/soc/samsung/neo1973_gta02_wm8753.c static int __init neo1973_gta02_init(void) · line 404
Quoted 5 lines
sound/soc/samsung/neo1973_gta02_wm8753.c +3
-1+/* register bluetooth DAI here */ + ret =snd_soc_register_dais (&neo1973_gta02_snd_device->dev, &bt_dai,1 );if (ret) - goto err_unregister_dai; + goto err_unregister_device;...uses the same device in both cases and looking briefly at the code both register functions just use the dev that was passed in.
The difference between the two is that snd_soc_register_dais calls fmt_multiple_name, but snd_soc_register_dai uses fmt_single_name. The later uses the name of device for which the dai is registered to generate the dai_device name, while the former uses the name of the dai_driver.
So by calling snd_soc_register_dai the bluetooth dai_device will be name "soc-core" instead of "bluetooth-dai". So currently there is no match between the dai_link and the dai_device, as a result the sound card is not instantiated.
Quoted 3 lines
In any
case, we clearly shouldn't be applying patches which bodge around the core.
Well the alternative would be a patch looking like this:
- .cpu_dai_name = "bluetooth-dai",
+ .cpu_dai_name = "soc-core",
Which isn't really nice either.
- Lars
Re: [PATCH 6/7] ASoC: Samsung: neo1973_gta02: Fix bluetooth DAI registration
Please fix your MUA to word wrap at less than 80 columns, I've reflowed your text so it's legible.
Quoted 10 lines · Lars-Peter Clausen
Quoted 3 lines
In any
case, we clearly shouldn't be applying patches which bodge around the core.Well the alternative would be a patch looking like this:
(quoted diff) +1
-1- .cpu_dai_name = "bluetooth-dai", + .cpu_dai_name = "soc-core",Which isn't really nice either.
If you think the core isn't behaving helpfully the core should be changed. This is part of how APIs evolve to be maximally useful.
To be honest it's not massively obvious that we shouldn't just be taking the name of the device here, either using a device to represent the modem or registering the card using snd_soc_register_machine() and using a more meaningful name for the card seems like a sensible approach here.
Re: [PATCH 6/7] ASoC: Samsung: neo1973_gta02: Fix bluetooth DAI registration
Quoted 11 lines · Mark Brown
Please fix your MUA to word wrap at less than 80 columns, I've reflowed your text so it's legible.
Quoted 5 lines · Lars-Peter Clausen
Quoted 3 lines
In any
case, we clearly shouldn't be applying patches which bodge around the core.Well the alternative would be a patch looking like this:
Quoted 8 lines
Quoted 4 lines
(quoted diff) +1
-1- .cpu_dai_name = "bluetooth-dai", + .cpu_dai_name = "soc-core",Which isn't really nice either.
If you think the core isn't behaving helpfully the core should be changed. This is part of how APIs evolve to be maximally useful.
As I see it the problem is that we have a deviceless dai and there is not really a way to register a dai without a device. But I have no idea right now how to change the core to make it "behave helpfully".
And in a sense snd_soc_register_dais seems to be the right thing to use for now, because the sound card as a whole has multiple dais they just not all registered at the same time.
Quoted 3 lines
To be honest it's not massively obvious that we shouldn't just be taking the name of the device here, either using a device to represent the modem
Seriously? I don't see how adding a dummy device wouldn't be "bodging around the core". Especially if using snd_soc_register_dais is.
Quoted 2 lines
or registering the card using
snd_soc_register_machine()and using a more meaningful name for the card seems like a sensible approach here.
Well, if were using snd_soc_register_machine to give the card a different name the bluetooth-dai would still be named after the card, wouldn't it? So there is no improvement here as to giving the dai a meaningful name.
- Lars
Re: [PATCH 6/7] ASoC: Samsung: neo1973_gta02: Fix bluetooth DAI registration
As I said when replying to your previous mail and I'm sure some earlier ones too you need to fix your MUA to word wrap at less than 80 columns. I've yet again reflowed your text so that it's legible.
Quoted 8 lines · Lars-Peter Clausen
Quoted 2 lines · Mark Brown
If you think the core isn't behaving helpfully the core should be changed. This is part of how APIs evolve to be maximally useful.
As I see it the problem is that we have a deviceless dai and there is not really a way to register a dai without a device. But I have no idea right now how to change the core to make it "behave helpfully".
You don't like the names the core is coming up with. Make better ones.
Quoted 3 lines
And in a sense
snd_soc_register_daisseems to be the right thing to use for now, because the sound card as a whole has multiple dais they just not all registered at the same time.
The card is only registering one DAI, all the other DAIs are attached to other devices in the system.
Quoted 6 lines
Quoted 3 lines
To be honest it's not massively obvious that we shouldn't just be taking the name of the device here, either using a device to represent the modem
Seriously? I don't see how adding a dummy device wouldn't be "bodging around the core". Especially if using
snd_soc_register_daisis.
The bluetooth chip is an actual device which I can point to on the board and schematic, having a struct device to represent a device that's actually present doesn't seem like a great leap.
Quoted 7 lines
Quoted 2 lines
or registering the card using
snd_soc_register_machine()and using a more meaningful name for the card seems like a sensible approach here.Well, if were using
snd_soc_register_machineto give the card a different name the bluetooth-dai would still be named after the card, wouldn't it? So there is no improvement here as to giving the dai a meaningful name.
It does mean it's named after the board.
Re: [PATCH 6/7] ASoC: Samsung: neo1973_gta02: Fix bluetooth DAI registration
Quoted 7 lines · Mark Brown
As I said when replying to your previous mail and I'm sure some earlier ones too you need to fix your MUA to word wrap at less than 80 columns. I've yet again reflowed your text so that it's legible.
Quoted 1 line · Lars-Peter Clausen
On 02/07/2011 06:02 PM, Mark Brown wrote:
Quoted 8 lines
Quoted 6 lines
Quoted 2 lines
If you think the core isn't behaving helpfully the core should be changed. This is part of how APIs evolve to be maximally useful.
As I see it the problem is that we have a deviceless dai and there is not really a way to register a dai without a device. But I have no idea right now how to change the core to make it "behave helpfully".
You don't like the names the core is coming up with. Make better ones.
I don't like the the names a specific function of the core is coming up with, so I used another one which names I like.
Quoted 7 lines
Quoted 4 lines
And in a sense
snd_soc_register_daisseems to be the right thing to use for now, because the sound card as a whole has multiple dais they just not all registered at the same time.The card is only registering one DAI, all the other DAIs are attached to other devices in the system.
Isn't the card the combination of these other devices?
Quoted 11 lines
Quoted 7 lines
Quoted 4 lines
To be honest it's not massively obvious that we shouldn't just be taking the name of the device here, either using a device to represent the modem
Seriously? I don't see how adding a dummy device wouldn't be "bodging around the core". Especially if using
snd_soc_register_daisis.The bluetooth chip is an actual device which I can point to on the board and schematic, having a struct device to represent a device that's actually present doesn't seem like a great leap.
Well, there is an actual device representing the bt device, but since this is the standard bt usb device I have no idea how we would get an reference to it from within the sound board driver.
Quoted 10 lines
Quoted 8 lines
Quoted 3 lines
or registering the card using
snd_soc_register_machine()and using a more meaningful name for the card seems like a sensible approach here.Well, if were using
snd_soc_register_machineto give the card a different name the bluetooth-dai would still be named after the card, wouldn't it? So there is no improvement here as to giving the dai a meaningful name.It does mean it's named after the board.
Ok. Could you please explain how snd_soc_register_machine would work and how it would effekt the naming of the dai? I couldn't find any reference to it.
- Lars
Re: [PATCH 6/7] ASoC: Samsung: neo1973_gta02: Fix bluetooth DAI registration
Once more I've reflowed your text. *Please* fix this, it's really hurting the legibility of your mail.
Quoted 6 lines · Lars-Peter Clausen
Quoted 2 lines · Mark Brown
The card is only registering one DAI, all the other DAIs are attached to other devices in the system.
Isn't the card the combination of these other devices?
Well, yes...
Quoted 7 lines
Quoted 3 lines
The bluetooth chip is an actual device which I can point to on the board and schematic, having a struct device to represent a device that's actually present doesn't seem like a great leap.
Well, there is an actual device representing the bt device, but since this is the standard bt usb device I have no idea how we would get an reference to it from within the sound board driver.
If you've got a real device and a driver binding to it then you can make the driver for that device register the DAI from its probe function, no need for the machine driver to get involved.
Quoted 5 lines
Quoted 1 line
It does mean it's named after the board.
Ok. Could you please explain how
snd_soc_register_machinewould work and how it would effekt the naming of the dai? I couldn't find any reference to it.
Sorry, snd_soc_register_card(). This skips the soc-audio device and allows the card to be registered from a regular device, meaning you can do things like pass platform data in sanely and handle multiple boards in a kernel without machine_is_() faff.
Adding bluetooth PCM interface support to ASoC (Was: Re: [PATCH 6/7] ASoC: Samsung: neo1973_gta02: Fix bluetooth DAI registration)
Quoted 4 lines · Mark Brown
Quoted 3 lines
Quoted 3 lines
The bluetooth chip is an actual device which I can point to on the board and schematic, having a struct device to represent a device that's actually present doesn't seem like a great leap.
Quoted 8 lines
Quoted 3 lines
Well, there is an actual device representing the bt device, but since this is the standard bt usb device I have no idea how we would get an reference to it from within the sound board driver.
If you've got a real device and a driver binding to it then you can make the driver for that device register the DAI from its probe function, no need for the machine driver to get involved.
The audio hardware setup of the board looks roughly like this:
[### SOC ###]
| | | USB | I2S | |
[BT]----[Codec]----[Modem]
PCM Analog
So the bluetooth chip is handeld by the standard USB BT HCI driver.
I did some research on the topic and it seems that this is a pretty common setup in embedded devices.
Audio to the bluetooth chip can either be send over the HCI interface (USB in this case) from the CPU or over the PCM interface from the codec, so that audio data from the modem to a bluetooth headset doesn't have to be routed through the CPU.
The PCM interface seems to be part of the bluetooth standard and there are even registers (PSKEY_PCM_CONFIG32) to configure the PCM format and bit-rate.
This and that neo1973 devices dont seem the only ones using such a setup, it would naturally make sense to write an ASoC driver to negotiate the PCM format between the codec and bluetooth chip and maybe do power management. (And ofcourse register a dai_device).
But the bluetooth audio support seems to be entirely written in userspace. The in-kernel bluetooth drivers in general seem only to provide a common interface to the underlying hardware and all of the higher level functionality seems to be implemented in userspace.
So right now I have no idea where to start if one wanted to add a ASoC driver which did the bt-dai configuration.
I've Cced Marcel Holtmann and the bluez mailinglist, maybe someone can give some input on subject.
- Lars
Re: Adding bluetooth PCM interface support to ASoC (Was: Re: [PATCH 6/7] ASoC: Samsung: neo1973_gta02: Fix bluetooth DAI registration)
Quoted 2 lines · Lars-Peter Clausen
I did some research on the topic and it seems that this is a pretty common setup in embedded devices.
Yes, this is a totally vanilla setup except that for modern hardware the baseband is connected digitally also.
Quoted 6 lines
But the bluetooth audio support seems to be entirely written in userspace. The in-kernel bluetooth drivers in general seem only to provide a common interface to the underlying hardware and all of the higher level functionality seems to be implemented in userspace.
So right now I have no idea where to start if one wanted to add a ASoC driver which did the bt-dai configuration.
The obvious starting point would seem to be to provide a driver which allows userspace to tell the kernel about configuration changes - that's what we're doing at the minute for the trivial case where the hardware doesn't change configuration. We could then look at pushing more of the code into the kernel if that made sense.
PATCH 7/7 ASoC: Samsung: Merge neo1937 and neo1973_gta02 sound board driver
In reply to Lars-Peter ClausenThe neo1973(GTA01) and neo1973_gta2(GTA02) have a very similar audio hardware setup. They both use the same codec with the same routing to the gsm modem and bluetooth chip. But they do use different AMPs though and there are some minor differences in the speaker setup.
As a result most of the code of those two drivers is identical.
So from a maintenance point of view it makes sense to merge them into a single driver. It also reduces the size of kernel images supporting both the GTA01 and GTA02.
As a side-effect of this merge the GTA01 for example gains support for routing audio to and from the bluetooth DAI.
--- sound/soc/samsung/Kconfig | 17 +- sound/soc/samsung/Makefile | 2 - sound/soc/samsung/neo1973_gta02_wm8753.c | 434 ------------------------------ sound/soc/samsung/neo1973_wm8753.c | 253 +++++++++++++----- 4 files changed, 192 insertions(+), 514 deletions(-) delete mode 100644 sound/soc/samsung/neo1973_gta02_wm8753.c
sound/soc/samsung/Kconfig +4 -13
@@ -35,23 +35,14 @@ config SND_SAMSUNG_I2S tristate config SND_SOC_SAMSUNG_NEO1973_WM8753 - tristate "SoC I2S Audio support for NEO1973 - WM8753" - depends on SND_SOC_SAMSUNG && MACH_NEO1973_GTA01 + tristate "Audio support for Openmoko Neo1973 Smartphones (GTA01/GTA02)" + depends on SND_SOC_SAMSUNG && (MACH_NEO1973_GTA01 || MACH_NEO1973_GTA02) select SND_S3C24XX_I2S select SND_SOC_WM8753 select SND_SOC_LM4857 help - Say Y if you want to add support for SoC audio on smdk2440 - with the WM8753. - -config SND_SOC_SAMSUNG_NEO1973_GTA02_WM8753 - tristate "Audio support for the Openmoko Neo FreeRunner (GTA02)" - depends on SND_SOC_SAMSUNG && MACH_NEO1973_GTA02 - select SND_S3C24XX_I2S - select SND_SOC_WM8753 - help - This driver provides audio support for the Openmoko Neo FreeRunner - smartphone. + Say Y here to enable audio support for the Openmoko Neo1973 + Smartphones. config SND_SOC_SAMSUNG_JIVE_WM8750 tristate "SoC I2S Audio support for Jive"
sound/soc/samsung/Makefile +0 -2
@@ -20,7 +20,6 @@ obj-$(CONFIG_SND_SAMSUNG_I2S) += snd-soc-i2s.o # S3C24XX Machine Support snd-soc-jive-wm8750-objs := jive_wm8750.o snd-soc-neo1973-wm8753-objs := neo1973_wm8753.o -snd-soc-neo1973-gta02-wm8753-objs := neo1973_gta02_wm8753.o snd-soc-smdk2443-wm9710-objs := smdk2443_wm9710.o snd-soc-ln2440sbc-alc650-objs := ln2440sbc_alc650.o snd-soc-s3c24xx-uda134x-objs := s3c24xx_uda134x.o
@@ -38,7 +37,6 @@ snd-soc-smdk-spdif-objs := smdk_spdif.o obj-$(CONFIG_SND_SOC_SAMSUNG_JIVE_WM8750) += snd-soc-jive-wm8750.o obj-$(CONFIG_SND_SOC_SAMSUNG_NEO1973_WM8753) += snd-soc-neo1973-wm8753.o -obj-$(CONFIG_SND_SOC_SAMSUNG_NEO1973_GTA02_WM8753) += snd-soc-neo1973-gta02-wm8753.o obj-$(CONFIG_SND_SOC_SAMSUNG_SMDK2443_WM9710) += snd-soc-smdk2443-wm9710.o obj-$(CONFIG_SND_SOC_SAMSUNG_LN2440SBC_ALC650) += snd-soc-ln2440sbc-alc650.o obj-$(CONFIG_SND_SOC_SAMSUNG_S3C24XX_UDA134X) += snd-soc-s3c24xx-uda134x.o
sound/soc/samsung/neo1973_gta02_wm8753.c deleted +0 -434
434 lines not on this page · raw message
sound/soc/samsung/neo1973_wm8753.c +188 -65
389 lines not on this page · raw message
Signature · 1 line
1.7.2.3
Quoted 7 lines · Lars-Peter Clausen
It has been proven to be inflexible to do scenario management in kernel space.
Since actual neo1973 board support has not been merged in mainline and this patch has been in the neo1973 tree for some time now it should be safe to remove this functionality without breaking existing userspace.
Signed-off-by Lars-Peter Clausen <[email protected]>
All
sound/soc/samsung/neo1973_wm8753.c static int neo1973_wm8753_init(struct snd_soc_pcm_runtime *rtd) · line 391
Quoted 5 lines · Lars-Peter Clausen
sound/soc/samsung/neo1973_wm8753.c +5
-0+snd_soc_dapm_disable_pin (codec,"Audio Out" ); +snd_soc_dapm_disable_pin (codec,"GSM Line Out" ); +snd_soc_dapm_disable_pin (codec,"GSM Line In" ); +snd_soc_dapm_disable_pin (codec,"Headset Mic" ); +snd_soc_dapm_disable_pin (codec,"Call Mic" );
This will mean that it's impossible to enable most (if not all) of the audio paths in the system which probably isn't what you want.
Quoted 10 lines · Mark Brown
sound/soc/samsung/neo1973_wm8753.c static int neo1973_wm8753_init(struct snd_soc_pcm_runtime *rtd) · line 391
Quoted 5 lines · Lars-Peter Clausen
sound/soc/samsung/neo1973_wm8753.c +5
-0+snd_soc_dapm_disable_pin (codec,"Audio Out" ); +snd_soc_dapm_disable_pin (codec,"GSM Line Out" ); +snd_soc_dapm_disable_pin (codec,"GSM Line In" ); +snd_soc_dapm_disable_pin (codec,"Headset Mic" ); +snd_soc_dapm_disable_pin (codec,"Call Mic" );This will mean that it's impossible to enable most (if not all) of the audio paths in the system which probably isn't what you want.
I've seem to have overlooked to add DAPM_SWITCH_PIN controls for these pins, since it has been done implicitly in the patch merging the gta01 and gta02 driver.
I'll resend a updated version.
- Lars