BeagleBoard-DeviceTrees issueshttps://git.beagleboard.org/beagleboard/BeagleBoard-DeviceTrees/-/issues2023-06-29T03:11:46-04:00https://git.beagleboard.org/beagleboard/BeagleBoard-DeviceTrees/-/issues/54BeaglePlay: mikrobus gpio line names2023-06-29T03:11:46-04:00Jason KridnerBeaglePlay: mikrobus gpio line namesline names should represent the board pins, not the SoC gpio indexes.line names should represent the board pins, not the SoC gpio indexes.https://git.beagleboard.org/beagleboard/BeagleBoard-DeviceTrees/-/issues/53Path references in overlays do not work, need hardcoded paths instead2023-05-09T14:04:46-04:00Matthijs van DuinPath references in overlays do not work, need hardcoded paths insteadThere's a bunch of overlays (here and in bb.org-overlays) that create properties in `/aliases` whose value is a node reference, e.g. [BB-BBGG-WL1835-00A0.dts](https://git.beagleboard.org/beagleboard/BeagleBoard-DeviceTrees/-/blob/v5.10.x...There's a bunch of overlays (here and in bb.org-overlays) that create properties in `/aliases` whose value is a node reference, e.g. [BB-BBGG-WL1835-00A0.dts](https://git.beagleboard.org/beagleboard/BeagleBoard-DeviceTrees/-/blob/v5.10.x-ti/src/arm/overlays/BB-BBGG-WL1835-00A0.dts) has:
```
aliases {
rtc0 = &extrtc;
rtc1 = "/ocp/rtc@44e3e000";
};
```
Node references (`&extrtc`) are typically encountered inside an integer array (`<...>`), which causes them to be replaced by the node's phandle. One outside an array, as is here the case, is replaced by the node's full path. This is basically a legacy thing used by some stuff inherited from Open Firmware, such as `/aliases` and `/chosen`.
These do not work in overlays and never have, since the overlay format only has support for fixing up phandles in properties, not paths. DTC of course doesn't warn about this but just sets the property to e.g. `"/fragment@7/__overlay__/rtc@68";` or fails on an undefined reference if you're trying to reference a node that's not defined in the overlay.
The workaround is to use the what we see for rtc1: just convert the label to a path. Unfortunately however these paths will be kernel version dependent, and this particular path is wrong for the branch I found this in (v5.10.x-ti).
This managed to go unnoticed for a long time because as long as the AM335x RTC is reassigned to rtc1 (i.e. as long as the path is correct), the external rtc will end up getting assigned to rtc0 by the kernel even if it has no entry in `/aliases`, since it's the first unused number. The fact that it works like that is kinda bad though, the kernel should have reserved "rtc0" in case the device it's assigned shows up, and the external rtc should therefore have become rtc2. Some other linux subsystems do actually get this right. (And if the kernel did that it wouldn't be necessary to manually move the built-in rtc to rtc1, the kernel would do that automatically if you assign some other device to be rtc0).https://git.beagleboard.org/beagleboard/BeagleBoard-DeviceTrees/-/issues/32BBORG_COMMS-00A2.dts is missing the RS485 configuration2021-04-01T11:27:31-04:00Jason KridnerBBORG_COMMS-00A2.dts is missing the RS485 configuration*Created by: jadonk*
This needs to be added and tested. See https://groups.google.com/g/beagleboard/c/tq-iAbS8iRY/m/tPIcqEZbAgAJ.*Created by: jadonk*
This needs to be added and tested. See https://groups.google.com/g/beagleboard/c/tq-iAbS8iRY/m/tPIcqEZbAgAJ.https://git.beagleboard.org/beagleboard/BeagleBoard-DeviceTrees/-/issues/27Convert to panel-simple2021-02-01T13:24:37-05:00Jason KridnerConvert to panel-simple*Created by: RobertCNelson*
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/gpu/drm/panel/panel-simple.c
https://github.com/beagleboard/BeagleBoard-DeviceTrees/blob/456d8d36d4226f7375aef1c4dffc19fdfc...*Created by: RobertCNelson*
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/gpu/drm/panel/panel-simple.c
https://github.com/beagleboard/BeagleBoard-DeviceTrees/blob/456d8d36d4226f7375aef1c4dffc19fdfc09dc11/src/arm/bbb-bone-buses.dtsi#L652-L670https://git.beagleboard.org/beagleboard/BeagleBoard-DeviceTrees/-/issues/30Overlay for GEN4-4DCAPE-43CT-CLB not working for BBAI2021-01-31T10:33:50-05:00Jason KridnerOverlay for GEN4-4DCAPE-43CT-CLB not working for BBAI*Created by: mjr1ch*
Hi
I have the compatibility layer and appropriate overlay installed. Show pins has the proper pins slated for the cape. Also modification to the cape adapter board was made to allow power from the USB port sinc...*Created by: mjr1ch*
Hi
I have the compatibility layer and appropriate overlay installed. Show pins has the proper pins slated for the cape. Also modification to the cape adapter board was made to allow power from the USB port since the BBAI lacks a barrel jack. When powered the Power LED stays on but I have no activity otherwise. This behavior only occurs when the cape is attached. If the cape is removed the BBAI functions as normal.
Please advise and thanks in advance.