@@ -51,29 +51,39 @@ int mtk_afe_add_sub_dai_control(struct snd_soc_component *component)structsnd_soc_dapm_context*dapm=snd_soc_component_to_dapm(component);structmtk_base_afe*afe=snd_soc_component_get_drvdata(component);structmtk_base_afe_dai*dai;+intret;list_for_each_entry(dai,&afe->sub_dais,list){-if(dai->controls)-snd_soc_add_component_controls(component,-dai->controls,-dai->num_controls);+if(dai->controls){+ret=snd_soc_add_component_controls(component,+dai->controls,+dai->num_controls);+if(ret)+returnret;+}-if(dai->dapm_widgets)-snd_soc_dapm_new_controls(dapm,-dai->dapm_widgets,-dai->num_dapm_widgets);+if(dai->dapm_widgets){+ret=snd_soc_dapm_new_controls(dapm,+dai->dapm_widgets,+dai->num_dapm_widgets);+if(ret)+returnret;+}}/* add routes after all widgets are added */list_for_each_entry(dai,&afe->sub_dais,list){-if(dai->dapm_routes)-snd_soc_dapm_add_routes(dapm,-dai->dapm_routes,-dai->num_dapm_routes);+if(dai->dapm_routes){+ret=snd_soc_dapm_add_routes(dapm,+dai->dapm_routes,+dai->num_dapm_routes);+if(ret)+returnret;+}}-snd_soc_dapm_new_widgets(component->card);+ret=snd_soc_dapm_new_widgets(component->card);-return0;+returnret;}EXPORT_SYMBOL_GPL(mtk_afe_add_sub_dai_control);
From: Mark Brown <broonie@kernel.org> Date: 2026-09-10 17:23:42
On Thu, Sep 10, 2026 at 06:43:37PM +0700, phucduc.bui@gmail.com wrote:
From: bui duc phuc <redacted>
mtk_afe_add_sub_dai_control() currently ignores errors from
ASoC control and DAPM setup functions.
Propagate these errors to the caller.
mt8365-afe-pcm.c has:
{"HW_GAIN1_IN_CH1", "CONNSYS_I2S_CH1", "Hostless FM DL"},
missing a Switch from the control. I suspect there's other errors; this
really needs to be tested before it can be applied. Given the general
quality of the driver here and the lack of anything constructive we're
doing with the errors changes like this have high risk and low reward
unless we're actually running the code.
mt8365-afe-pcm.c has:
{"HW_GAIN1_IN_CH1", "CONNSYS_I2S_CH1", "Hostless FM DL"},
missing a Switch from the control. I suspect there's other errors; this
really needs to be tested before it can be applied. Given the general
quality of the driver here and the lack of anything constructive we're
doing with the errors changes like this have high risk and low reward
unless we're actually running the code.
I agree that these changes should ideally be tested on real hardware.
Unfortunately, I don't currently have any MTK boards available for
testing.
If these changes cannot be properly tested, I'm also fine with
dropping this patch.
On a related note: do MediaTek or other hardware vendors typically
provide development boards to independent upstream contributors for
testing purposes? It would make it much easier for contributors like
me to properly validate changes like this one.
Best regards,
Phuc
From: Mark Brown <broonie@kernel.org> Date: 2026-09-11 12:07:15
On Fri, Sep 11, 2026 at 10:00:39AM +0700, Bui Duc Phuc wrote:
On a related note: do MediaTek or other hardware vendors typically
provide development boards to independent upstream contributors for
testing purposes? It would make it much easier for contributors like
me to properly validate changes like this one.