linux-kernel - [RFC] Device addition to the tlv320adcx140 and tas2562

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-next>] [day] [month] [year] [list]

Date:   Wed, 9 Sep 2020 10:01:51 -0500
From:   Dan Murphy <dmurphy@...com>
To:     Mark Brown <broonie@...nel.org>,
        Liam Girdwood <lgirdwood@...il.com>,
        "tiwai@...e.com" <tiwai@...e.com>
CC:     "alsa-devel@...a-project.org" <alsa-devel@...a-project.org>,
        LKML <linux-kernel@...r.kernel.org>
Subject: [RFC] Device addition to the tlv320adcx140 and tas2562

Hello

Looking for guidance on how to move forward with adding a device to 
existing drivers.

For the TLV320adcx140 driver I have another device which is register and 
bitmap compatible but it does not support Analog microphones or Line In 
like the x140.

Should I add a new driver specifically for this part or should I add the 
new audio maps, widgets and controls to the existing driver?  This would 
make this existing driver really big in terms of LoC and object size.

Similar question for the TAS2562.  I have a new device that is register 
and bitmap compatible but removes the I/V sense. Adding this new device 
to the existing driver wouldn't be as intrusive as the x140 as the audio 
map and controls are much simpler

Dan