Re: [PATCH 0/5] ASoC: intel: use component_name for Component name

[Cezary Rojewski <cezary.rojewski@intel.com>]

On 6/26/2026 8:09 AM, Kuninori Morimoto wrote:
> Hi Mark, Intel developer
> 
> Current component has component->name, but we can't setup it via
> component_driver today, so the user need to use
> snd_soc_component_initialize() / snd_soc_add_component() directly
> instead of using snd_soc_register_component().
> 
> This patch-set try to solve root cause of this issue

Hi Kuninori,

Does this mean you have a patchset or two that follow this one up? 
Looking at this one alone, I'm not seeing why both ->driver_name and 
->component_name are added.

The driver is supposed to define _behavior_ of the entity it _drives_. 
Component's name is (typically) a static part of its description, not 
its runtime behavior.  To keep the design nice and clean shouldn't we 
leave driver->name and component->name alone?


Kind regards,
Czarek


> Kuninori Morimoto (5):
>    ASoC: soc-component: add driver_name
>    ASoC: soc-component: add component_name
>    ASoC: intel: avs: pcm: use component_name for Component name
>    ASoC: intel: avs: probes: use component_name for Component name
>    ASoC: intel: catpt: pcm: use component_name for Component name
> 
>   include/sound/soc-component.h |  6 +++++-
>   sound/soc/intel/avs/pcm.c     |  4 ++--
>   sound/soc/intel/avs/probes.c  | 27 ++++++++++-----------------
>   sound/soc/intel/catpt/pcm.c   | 20 ++++----------------
>   sound/soc/soc-core.c          | 11 ++++++-----
>   5 files changed, 27 insertions(+), 41 deletions(-)
>