lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-ID: <YiBPE9z+iHU7unn7@google.com> Date: Thu, 3 Mar 2022 13:16:03 +0800 From: Tzung-Bi Shih <tzungbi@...nel.org> To: Jiaxin Yu <jiaxin.yu@...iatek.com> Cc: broonie@...nel.org, robh+dt@...nel.org, matthias.bgg@...il.com, trevor.wu@...iatek.com, alsa-devel@...a-project.org, devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org, linux-mediatek@...ts.infradead.org, linux-kernel@...r.kernel.org, Project_Global_Chrome_Upstream_Group@...iatek.com, Jiaxin Yu <jiaxin.yu@...iatek.corp-partner.google.com> Subject: Re: [PATCH 2/2] ASoC: mediatek: mt8192: support rt1015p_rt5682s On Wed, Mar 02, 2022 at 12:07:39PM +0800, Jiaxin Yu wrote: > On Tue, 2022-03-01 at 17:03 +0800, Tzung-Bi Shih wrote: > > After seeing the code, I am starting to wonder if the reuse is > > overkill. If > > they (RT5682 vs. RT5682S) only have some minor differences, probably > > it could > > reuse more by: > > > > SND_SOC_DAILINK_DEFS(i2s8, ... > > SND_SOC_DAILINK_DEFS(i2s9, ... > > > > ... > > > > if (card == &mt8192_mt6359_rt1015p_rt5682s_card) { > > i2s8_codecs.name = RT5682S_DEV0_NAME; > > i2s8_codecs.dai_name = RT5682S_CODEC_DAI; > > ... > > } > > > > Or even uses of_device_is_compatible() if it would like to reuse the > > struct > > snd_soc_card. > If we reuse the struct snd_soc_card, the card .name will be same. > Should I change the card .name through of_device_is_compatible()? Exactly yes.
Powered by blists - more mailing lists