02-06-2024, 03:46 PM
Technically the files are not the actual device driver but whats called a device tree overlay (dtoverlay) file. It's basically a setup file thats used to specify to the Linux kernel the audio CODEC, supported sample rates, whether I2C comms is used, clock switching, etc.
Generic 1 loads the device tree overlay named hifiberry-dac which specifies audio CODEC pcm5102a
https://github.com/raspberrypi/linux/blo...verlay.dts
Generic 2 loads the device tree overlay named i2s-dac which specifies audio CODEC pcm1794a
https://github.com/raspberrypi/linux/blo...verlay.dts
Kernel overlay readme
https://github.com/raspberrypi/linux/blo...ays/README
You can search the Raspberry Pi Linux sources for the audio CODEC sources and other related files.
https://github.com/raspberrypi/linux/
*** In any case the maker of the DAC should be able to tell you specifically what Linux I2S overlay should be used.
Generic 1 loads the device tree overlay named hifiberry-dac which specifies audio CODEC pcm5102a
https://github.com/raspberrypi/linux/blo...verlay.dts
Generic 2 loads the device tree overlay named i2s-dac which specifies audio CODEC pcm1794a
https://github.com/raspberrypi/linux/blo...verlay.dts
Kernel overlay readme
https://github.com/raspberrypi/linux/blo...ays/README
You can search the Raspberry Pi Linux sources for the audio CODEC sources and other related files.
https://github.com/raspberrypi/linux/
*** In any case the maker of the DAC should be able to tell you specifically what Linux I2S overlay should be used.