Linux Sound subsystem development
 help / color / mirror / Atom feed
From: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
To: Mark Brown <broonie@kernel.org>,
	Rui Zhou <zhourui@huaqin.corp-partner.google.com>
Cc: lgirdwood@gmail.com, perex@perex.cz, tiwai@suse.com,
	matthias.bgg@gmail.com, trevor.wu@mediatek.com,
	allen-kh.cheng@mediatek.com, kuninori.morimoto.gx@renesas.com,
	maso.huang@mediatek.com, linux-sound@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-mediatek@lists.infradead.org
Subject: Re: [PATCH v1] ASoC: support machine driver with TAS2781
Date: Tue, 11 Jun 2024 14:38:09 +0200	[thread overview]
Message-ID: <d7d32ef3-8b2e-476c-a15e-7f829ea0d60a@collabora.com> (raw)
In-Reply-To: <Zmgsfafmfedd9_MV@finisterre.sirena.org.uk>

Il 11/06/24 12:52, Mark Brown ha scritto:
> On Tue, Jun 11, 2024 at 10:22:27AM +0800, Rui Zhou wrote:
>> Support amp TAS2781 for mt8188 platform
>>
>> Signed-off-by: Rui Zhou <zhourui@huaqin.corp-partner.google.com>
>> ---
>>   sound/soc/mediatek/Kconfig | 1 +
>>   1 file changed, 1 insertion(+)
>>
>> diff --git a/sound/soc/mediatek/Kconfig b/sound/soc/mediatek/Kconfig
>> index 5a8476e1ecca..07f67f96c889 100644
>> --- a/sound/soc/mediatek/Kconfig
>> +++ b/sound/soc/mediatek/Kconfig
>> @@ -233,6 +233,7 @@ config SND_SOC_MT8188_MT6359
>>   	select SND_SOC_HDMI_CODEC
>>   	select SND_SOC_DMIC
>>   	select SND_SOC_MAX98390
>> +	select SND_SOC_TAS2781_I2C
>>   	select SND_SOC_NAU8315
>>   	select SND_SOC_NAU8825
> 
> Ideally this would be sorted to avoid spurious merge conficts.  Also do
> we really have dependencies here or should these just be being enabled
> by users - these drivers are all pretty generic now?

The only dependency is on the MT6359 PMIC's audio related IPs and nothing else.

I'd even remove the other select statements for the other codecs, honestly,
as there's no reason why MT8188 wouldn't support a codec or the other, and
there is no reason why that SoC needs exactly those codecs, apart from some
board (Chromebooks) having one, or the other.

Instead of adding a select statement on MT8188_MT6359, adding the TAS2781_I2C
driver as a module in defconfig is a better idea..... at least, IMO.

>  Not that this
> change in itself makes a huge difference to the existing state.

I agree it doesn't make any huge difference, but I also don't see why users
can't simply enable (y/m) that in the kernel configuration :-)

Cheers,
Angelo

  reply	other threads:[~2024-06-11 12:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-11  2:22 [PATCH v1] ASoC: support machine driver with TAS2781 Rui Zhou
2024-06-11 10:52 ` Mark Brown
2024-06-11 12:38   ` AngeloGioacchino Del Regno [this message]
2024-06-11 13:19     ` Mark Brown
2024-06-11 14:09       ` AngeloGioacchino Del Regno

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=d7d32ef3-8b2e-476c-a15e-7f829ea0d60a@collabora.com \
    --to=angelogioacchino.delregno@collabora.com \
    --cc=allen-kh.cheng@mediatek.com \
    --cc=broonie@kernel.org \
    --cc=kuninori.morimoto.gx@renesas.com \
    --cc=lgirdwood@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=maso.huang@mediatek.com \
    --cc=matthias.bgg@gmail.com \
    --cc=perex@perex.cz \
    --cc=tiwai@suse.com \
    --cc=trevor.wu@mediatek.com \
    --cc=zhourui@huaqin.corp-partner.google.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