linux-kernel - RE: [PATCH 2/2] ASoC: Intel: sof

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Thu, 27 Oct 2022 04:33:40 +0000
From:   "Lu, Brent" <brent.lu@...el.com>
To:     Pierre-Louis Bossart <pierre-louis.bossart@...ux.intel.com>,
        "alsa-devel@...a-project.org" <alsa-devel@...a-project.org>
CC:     "C, Balamurugan" <balamurugan.c@...el.com>,
        "Rojewski, Cezary" <cezary.rojewski@...el.com>,
        Chao Song <chao.song@...ux.intel.com>,
        "Kai Vehmanen" <kai.vehmanen@...ux.intel.com>,
        "Wang, Rander" <rander.wang@...el.com>,
        Bard Liao <yung-chuan.liao@...ux.intel.com>,
        "Takashi Iwai" <tiwai@...e.com>,
        "Song, Gongjun" <gongjun.song@...el.com>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        Liam Girdwood <liam.r.girdwood@...ux.intel.com>,
        "Chiang, Mac" <mac.chiang@...el.com>,
        "Mark Brown" <broonie@...nel.org>,
        "Reddy, Muralidhar" <muralidhar.reddy@...el.com>,
        Ranjani Sridharan <ranjani.sridharan@...ux.intel.com>,
        Ajye Huang <ajye.huang@...il.com>,
        Peter Ujfalusi <peter.ujfalusi@...ux.intel.com>,
        "Gopal, Vamshi Krishna" <vamshi.krishna.gopal@...el.com>,
        "Zhi, Yong" <yong.zhi@...el.com>
Subject: RE: [PATCH 2/2] ASoC: Intel: sof_rt5682: quirk auto detection

> 
> I appreciate what you are trying to suggest, and I am all for trying to put this
> proliferation of quirks under control, but the autodetection based on rules
> seems out-of-reach if we don't first cleanup the existing quirks.
> 
> If "volteer" and "brya" mean different things to different people, and reference
> and derivatives are not well identified, the odds of regressions seem very high to
> me.
> 

The reason that we need so many DMI quirks is that we are not able to know
which SSP port is used by headphone and amplifier. However, it seems to me
that platform and machine driver does not care about the DAI name.

I've tested to rename the backend DAIs as something like 'SSP-HP', 'SSP-SPK',
and 'SSP-BT' so we don't need to create new board info just because the SSP
port is different. However, we need to modify topology since DAI name is
changed.

Regards,
Brent