Re: [EXTERNAL] Re: [PATCH v1 2/2] ASoC: tas2781: Add tas5832 support

[Xu, Baojun]

> 
> ________________________________________
> From: Krzysztof Kozlowski <krzk@xxxxxxxxxx>
> Sent: 02 March 2026 16:58
> To: Xu, Baojun
> Cc: broonie@xxxxxxxxxx; tiwai@xxxxxxx; andriy.shevchenko@xxxxxxxxxxxxxxx; 13916275206@xxxxxxx; Ding, Shenghao; linux-sound@xxxxxxxxxxxxxxx; linux-kernel@xxxxxxxxxxxxxxx; lgirdwood@xxxxxxxxx; robh@xxxxxxxxxx; krzk+dt@xxxxxxxxxx; conor+dt@xxxxxxxxxx; devicetree@xxxxxxxxxxxxxxx; Yi, Ken; Lo, Henry; Chen, Robin; Wang, Will; jim.shil@xxxxxxxxxxx; toastcheng@xxxxxxxxxx; chinkaiting@xxxxxxxxxx
> Subject: Re: [EXTERNAL] Re: [PATCH v1 2/2] ASoC: tas2781: Add tas5832 support
> 
> On 02/03/2026 09:24, Xu, Baojun wrote:
> >>>>
> >>>>>  MODULE_DEVICE_TABLE(i2c, tasdevice_id);
> >>>>> @@ -144,6 +145,7 @@ static const struct of_device_id tasdevice_of_match[] = {
> >>>>>       { .compatible = "ti,tas5827" },
> >>>>>       { .compatible = "ti,tas5828" },
> >>>>>       { .compatible = "ti,tas5830" },
> >>>>> +     { .compatible = "ti,tas5832" },
> >>>>
> >>>> So it is fully compatible with tas5830 and most of the changes here are
> >>>> not needed?
> >>>
> >>> Yes, it's fully compatible with tas5827/28/30.
> >>
> >> Then above hunk and many others are not needed.
> >
> > Hi, because those chips have different on the voltage, so the parameters
> > is different, have to use different firmware binary, so we must identify
> > every chip in the driver.
> 
> That would explain other ID tables (and should be briefly mentioned in
> the commit msg), but not this one, because here you do not customize the
> binary at all.
> 

Hi, we save the chip_id in the dev_name:
strscpy(tas_priv->dev_name, tasdevice_id[tas_priv->chip_id].name,
	sizeof(tas_priv->dev_name));

And get firmware binary from this dev_name:
scnprintf(tas_priv->rca_binaryname, 64, "%sRCA%d.bin",
	tas_priv->dev_name, tas_priv->ndev);

> Best regards,
> Krzysztof
> 
> 
> 
Best Regards
Jim