Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Cezary Rojewski <cezary.rojewski@intel.com>,
	alsa-devel@alsa-project.org,  broonie@kernel.org
Cc: hdegoede@redhat.com, tiwai@suse.com, amadeuszx.slawinski@linux.intel.com
Subject: Re: [PATCH 00/17] ASoC: Intel: haswell and broadwell boards update
Date: Fri, 10 Jun 2022 13:48:46 -0500	[thread overview]
Message-ID: <dae93c48-7fc0-bde0-bcc5-b66dc79ac205@linux.intel.com> (raw)
In-Reply-To: <2634f801-446e-04e0-89d6-5bee25dab109@intel.com>



On 6/10/22 12:33, Cezary Rojewski wrote:
> On 2022-06-10 2:36 PM, Cezary Rojewski wrote:
>> A number of patches improving overall quality and readability of
>> haswell.c and broadwell.c source files found in sound/soc/intel/boards.
>> Both files are first renamed and only then actual changes are being
>> incrementally added. The respective names are: hsw_rt5640 and bdw_rt286
>> to match the pattern found in more recent boards.
>>
>> Most patches bring no functional change - the more impactful patches at
>> are placed the end:
>>
>> Refactor of suspend/resume flow for the bdw_rt286 board by dropping
>> dev->remove() in favour of card->remove() and adjust jack handling to
>> reduce code size slightly by implementing card_set_jack().
>>
>> The last patch is removing of FE DAI ops. Given the existence of
>> platform FE DAI capabilities (either static declaration or through
>> topology file), this code is redundant.
> 
> 
> Hello,
> 
> While this patchset reorganizes and rewords code of two boards in
> question, module (kernel module) names are unchanged. Currently those
> two are:
> 
> - snd_soc_sst_haswell.ko
> - snd_soc_sst_broadwell.ko
> 
> My question is: Is it viable to reword these two?
> 
> Both modules accept no custom parameters, perhaps *dyndbg* is the only
> possibility so the impact is reduced.

Thanks for asking the question.

I have no objection to the driver name change and haswell is not used in
commercial products outside of Intel.

You have a point that most of the machine driver module names make
limited sense in hindsight, but it's better to leave them as is.
Changing them will increase confusion IMHO.

We have scripts to remove/re-insert modules and every time we add a name
change we break the test suite. This happened when we changed all the
PCI names, it wasn't pretty. See e.g. all the 'obsolete' references in
those scripts to keep them working across kernel versions.

https://github.com/thesofproject/sof-test/blob/main/tools/kmod/sof_remove.sh#L134

we also enable dyndbg with /etc/modprobe.d/sof-dyndbg.conf deployed on
test devices, if we change module names it gives everyone involved in
CI/testing more work.

And last if you Google a bit you'll see references in a couple of wikis
and bug reports to modprobe snd-soc-sst-broadwell, so if you change the
module name you make the information obsolete.


  reply	other threads:[~2022-06-10 18:49 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-10 12:36 [PATCH 00/17] ASoC: Intel: haswell and broadwell boards update Cezary Rojewski
2022-06-10 12:36 ` [PATCH 01/17] ASoC: Intel: Rename haswell source file to hsw_rt5640 Cezary Rojewski
2022-06-10 12:36 ` [PATCH 02/17] ASoC: Intel: hsw_rt5640: Reword prefixes of all driver members Cezary Rojewski
2022-06-10 13:11   ` Cezary Rojewski
2022-06-10 12:36 ` [PATCH 03/17] ASoC: Intel: hsw_rt5640: Reword driver name Cezary Rojewski
2022-06-10 12:36 ` [PATCH 04/17] ASoC: Intel: hsw_rt5640: Update code indentation Cezary Rojewski
2022-06-10 12:36 ` [PATCH 05/17] ASoC: Intel: hsw_rt5640: Update file comments Cezary Rojewski
2022-06-10 12:36 ` [PATCH 06/17] ASoC: Intel: hsw_rt5640: Improve probe() function quality Cezary Rojewski
2022-06-10 12:36 ` [PATCH 07/17] ASoC: Intel: hsw_rt5640: Improve hw_params() debug-ability Cezary Rojewski
2022-06-10 12:36 ` [PATCH 08/17] ASoC: Intel: Rename broadwell source file to bdw_rt286 Cezary Rojewski
2022-06-10 12:36 ` [PATCH 09/17] ASoC: Intel: bdw_rt286: Reword prefixes of all driver members Cezary Rojewski
2022-06-10 16:34   ` Pierre-Louis Bossart
2022-06-10 17:25     ` Cezary Rojewski
2022-06-10 12:36 ` [PATCH 10/17] ASoC: Intel: bdw_rt286: Reword driver name Cezary Rojewski
2022-06-10 12:36 ` [PATCH 11/17] ASoC: Intel: bdw_rt286: Update code indentation Cezary Rojewski
2022-06-10 12:36 ` [PATCH 12/17] ASoC: Intel: bdw_rt286: Update file comments Cezary Rojewski
2022-06-10 12:36 ` [PATCH 13/17] ASoC: Intel: bdw_rt286: Improve probe() function quality Cezary Rojewski
2022-06-10 12:36 ` [PATCH 14/17] ASoC: Intel: bdw_rt286: Improve hw_params() debug-ability Cezary Rojewski
2022-06-10 12:36 ` [PATCH 15/17] ASoC: Intel: bdw_rt286: Improve codec_init() quality Cezary Rojewski
2022-06-10 12:36 ` [PATCH 16/17] ASoC: Intel: bdw_rt286: Refactor suspend/resume Cezary Rojewski
2022-06-10 12:36 ` [PATCH 17/17] ASoC: Intel: bdw_rt286: Remove FE DAI ops Cezary Rojewski
2022-06-10 17:33 ` [PATCH 00/17] ASoC: Intel: haswell and broadwell boards update Cezary Rojewski
2022-06-10 18:48   ` Pierre-Louis Bossart [this message]
2022-06-13  9:52     ` Cezary Rojewski

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=dae93c48-7fc0-bde0-bcc5-b66dc79ac205@linux.intel.com \
    --to=pierre-louis.bossart@linux.intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=amadeuszx.slawinski@linux.intel.com \
    --cc=broonie@kernel.org \
    --cc=cezary.rojewski@intel.com \
    --cc=hdegoede@redhat.com \
    --cc=tiwai@suse.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox