Torsten Duwe wrote:
On Mon, 25 Nov 2019 20:15:26 +0000 Richard MQ <osl2008@gmail.com> wrote:
And I already knew about /boot/efi/extraconfig.txt and had dtoverlay=hifiberry-dacplus to no avail, I have pre-pended dtparam=i2s=on as suggested but still no dice (nothing shows up in hwinfo, nor Yast - Sound Card)
@Torsten - please can you advise where to configure the strings and addresses that you mention?
Accessing the little box, which has been running happily for quite some time now, I hope I can remember the tweaks I had to do back then:
It is a RPi Zero W, with a "justboom amp zero" pHAT. The point is, no overlay matched it exactly back then so I chose a compatible chip from the "iqaudio-dac" and fixed the I2C address, IIRC.
config.txt has: --------------- dtoverlay=iqaudio-dac dtparam=audio=on dtparam=i2c0=on dtparam=i2c1=on
The overlay produces in my fdt: i2c@7e804000 { compatible = "brcm,bcm2708-i2c"; [...] pcm5122@4d { status = "okay"; reg = <0x4d>; compatible = "ti,pcm5122"; #sound-dai-cells = <0x0>; };
The kernel loads snd_soc_pcm512x_i2c and dmesg yields:
snd-rpi-iqaudio-dac soc:sound: pcm512x-hifi <-> 20203000.i2s mapping ok
hifiberry-dacplus already has an overlay that should work out of the box, in theory.
Thanks Torsten, Am I right in thinking I need "fdtdump" (or is it "dtoverlay"?) to see the fdt? I seem to be lacking the key tools to debug this, and can't work out where to get them. Please can anyone point me at a source for "fdtdump", "vcdbg", "dtoverlay" etc as "zypper se", googling for e.g. "opensuse raspberry vcdbg" are not giving me anything useful. Also I clearly need to bone up on the device tree implementation. I have been reading https://www.raspberrypi.org/documentation/configuration/device-tree.md but if anything I think I am more confused than ever! Is there a better intro? Thanks again both for your help Best regards Richard -- To unsubscribe, e-mail: opensuse-arm+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-arm+owner@opensuse.org