# Linux 6.12, upstream device tree for a311d outdated?

**URL:** <https://community.mnt.re/t/linux-6-12-upstream-device-tree-for-a311d-outdated/3284>\
**Category:** MNT Reform\
**Created:** [April 11, 2025, 6:02pm UTC](https://community.mnt.re/t/linux-6-12-upstream-device-tree-for-a311d-outdated/3284 "2025-04-11T18:02:39Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![soulsource](https://community.mnt.re/letter_avatar_proxy/v4/letter/s/cc9497/32.png) [@soulsource](https://community.mnt.re/u/soulsource)\
**Post date:** [April 11, 2025, 6:02pm UTC](https://community.mnt.re/t/linux-6-12-upstream-device-tree-for-a311d-outdated/3284/1 "2025-04-11T18:02:40Z")

</div>

I am currently trying to update my Gentoo installation’s kernel to 6.12, and am wondering about some discrepancies between the device tree file (meson-g12b-bananapi-cm4-mnt-reform2.dts) [from the MNT Reform Debian repo](https://source.mnt.re/reform/reform-debian-packages/-/blob/main/linux/meson-g12b-bananapi-cm4-mnt-reform2.dts), and [the file that is available as part of the upstream kernel 6.12](https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/tree/arch/arm64/boot/dts/amlogic/meson-g12b-bananapi-cm4-mnt-reform2.dts?h=v6.12.23), as there are some notable differences:

- The upstream version of meson-g12b-bananapi-cm4-mnt-reform2.dts does not have the section about the spi-gpio (and the lpc11u24) at all.
  - Without this section, communication with the system controller (and therefore stuff like poweroff on shutdown) does not work.

- The upstream version of meson-g12b-bananapi-cm4-mnt-reform2.dts lists the sound chip (wm8960) and the real-time-clock (pcf8523) as connected via i2c2, while the version from the debian repo lists them connected to i2c3.
  - The correct value is, afaict, i2c3.

- Burst mode for the eDP bridge is not enabled upstream.

The [history of the file in the MNT Reform Debian repo](https://source.mnt.re/reform/reform-debian-packages/-/commits/main/linux/meson-g12b-bananapi-cm4-mnt-reform2.dts?ref_type=heads) shows that those changes were all added after the initial commit. So, can it be that an outdated version of this file has been upstreamed?

---

<div class="post-metadata">

**Author:** ![doctorhoo](https://community.mnt.re/user_avatar/community.mnt.re/doctorhoo/32/338_2.png) [@doctorhoo](https://community.mnt.re/u/doctorhoo)\
**Post date:** [April 17, 2025, 10:12am UTC](https://community.mnt.re/t/linux-6-12-upstream-device-tree-for-a311d-outdated/3284/2 "2025-04-17T10:12:24Z")

</div>

Interesting find! I am wondering whether this might have something to do with the issue I have with the TRRS microphone in on the A311D: [No input device selectable for wired headset plugged into TRRS port - #13 by doctorhoo](https://community.mnt.re/t/no-input-device-selectable-for-wired-headset-plugged-into-trrs-port/3205/13)

But I suspect that the wrong value (`i2c3` vs `i2c2`) would make the entire sound chip non-functional?

Sound in general works for me, so I could verify the correct value on my system. How do I get this from the current device tree? I am not really sure how to read what `dtc` dumps at me..

---

<div class="post-metadata">

**Author:** ![soulsource](https://community.mnt.re/letter_avatar_proxy/v4/letter/s/cc9497/32.png) [@soulsource](https://community.mnt.re/u/soulsource)\
**Post date:** [April 17, 2025, 1:32pm UTC](https://community.mnt.re/t/linux-6-12-upstream-device-tree-for-a311d-outdated/3284/3 "2025-04-17T13:32:40Z")

</div>

With the upstream device tree, the sound card is not detected at all, so ther also is no audio output.

I have never really tried to actually read the output of a decompiled binary device tree or of the /proc/device-tree folder. It sounds pretty difficult to do, given that it will not use any alias names… However, looking at my working setup (`dtc -I fs /proc/device-tree`), I see the devices in question (rtc, audio codec) hooked up to i2c@1c000, which I assume is what uses the i2c3 alias in the dts file.

Regarding the microphone: I too [never managed to get audio-in working](https://community.mnt.re/t/record-audio-without-pulseaudio-pipewire/2190), but since I am not on the official Debian image, I “just” blamed my ALSA configuration. Furthermore, I figured out that what I really wanted, namely the line-in port, is not wired up to any external connector, so I would have to solder a plug to the mainboard to get it working… So, I just gave up on this and bought [a USB sound card](https://www.delock.de/produkt/61803/merkmale.html).

---

<div class="post-metadata">

**Author:** ![doctorhoo](https://community.mnt.re/user_avatar/community.mnt.re/doctorhoo/32/338_2.png) [@doctorhoo](https://community.mnt.re/u/doctorhoo)\
**Post date:** [April 17, 2025, 2:05pm UTC](https://community.mnt.re/t/linux-6-12-upstream-device-tree-for-a311d-outdated/3284/4 "2025-04-17T14:05:06Z")

</div>

Just to clarify: Were you already using the A311D when trying to get the audio input working?

---

<div class="post-metadata">

**Author:** ![josch](https://community.mnt.re/user_avatar/community.mnt.re/josch/32/1003_2.png) [@josch](https://community.mnt.re/u/josch)\
**Post date:** [April 17, 2025, 3:54pm UTC](https://community.mnt.re/t/linux-6-12-upstream-device-tree-for-a311d-outdated/3284/5 "2025-04-17T15:54:34Z")

</div>

Thank you for bringing this up. Instead shipping a near-copy of upstream dts, reform-debian-packages should ship a patch against the upstream dts. This is now proposed here: [linux: patch meson-g12b-bananapi-cm4-mnt-reform2.dts instead of overwriting (!94) · Merge requests · Reform / reform-debian-packages · GitLab](https://source.mnt.re/reform/reform-debian-packages/-/merge_requests/94)

---

<div class="post-metadata">

**Author:** ![soulsource](https://community.mnt.re/letter_avatar_proxy/v4/letter/s/cc9497/32.png) [@soulsource](https://community.mnt.re/u/soulsource)\
**Post date:** [May 5, 2025, 8:41am UTC](https://community.mnt.re/t/linux-6-12-upstream-device-tree-for-a311d-outdated/3284/6 "2025-05-05T08:41:49Z")

</div>

(Sorry for the late and off-topic reply)  
Yes, I’ve been using an a311d already back then.
