0.1.9
overlays
Additional device tree overlays to support different hardware on Radxa products
Build overlays in-tree
You will need this patch so this repo can be built with the kernel.
The official overlays are built in-tree, and is delivered as part of the kernel package.
Build overlays locally
First, make sure you have the running kernel header, gcc
, and device-tree-compiler
installed.
You can then run the following command to build overlays:
make -j$(nproc)
Please be aware this only build a subset of overlays, and any overlays that depend on vendor headers will fail. This is because the Makefile is intended to find overlays that are incompatible with upstream kernel.
To delete built overlays, run the following command:
make clean
Download prebuilt artifacts
As part of our CI pipeline, the built overlays are uploaded at the end. You can find all CI runs here, and the artifact is located inside each indvidual run.
Please be aware that artifacts expire over time, and they are not officially tested versions.
Code style
We mandate reference style for our overlays. Please visit DTO Syntax page to learn more.
If your existing overlay uses target-path
, then the Android documentation does not show a clear migration path. Below is an example of how to convert them:
/{
fragment@0 {
target-path = "/";
__overlay__ {
some_node: some-node {
some_prop = "okay";
...
};
};
};
}
&{/} {
some_node: some-node {
some_prop = "okay";
...
};
}
Metadata specs
Currently, we mandate a custom metadata
node in overlays. This data is parsed by rsetup
to provide a human readable description and conflict detection. Below is a sample metadata
node with detailed guidelines after:
/ {
metadata {
title = "Enable ENC28J60 on SPI2";
category = "misc";
compatible = "unknown";
description = "Enable Microchip ENC28J60 SPI Ethernet controller on SPI2.\nINT=40";
exclusive = "GPIO2_B3", "GPIO2_B2", "GPIO2_B1", "GPIO2_B4", "GPIO4_A7";
package = "dkms-enc28j60";
};
};
A. Title (string)
title
should not contain the product name.
rsetup
will only show compatible overlays withcompatible
field. As such, do not confuse users to second guess if an overlay is truly compatible when the product name is not explicitly mentioned.title
should not end with a period.
B. Category (string)
category
currently can be one of the following:
camera, display, misc
C. Compatible (array)
compatible
should not be an SoC unless it is truly compatible with every products using that SoC.
rsetup
will match the base device tree'scompatible
with the overlay'scompatible
. As long as one value from each match, the overlay is considered compatible. Since most products' device tree contains their SoC incompatible
, setting SoC in overlay'scompatible
will make it compatible with every such product.
Explicit products list should be preferred to generic SoC matching.- If a overlay is broken,
compatible
should beunknown
.
D. Description (string)
description
is a multi line text to describe the function of the overlay. It can be the same astitle
with an ending period.- Newline in
description
should use\n
. - Hardware parameters should be listed at the end to help user to connect their devices.
E. Exclusive (array)
exclusive
should refer to the device tree node and property.- For features that are muxed to a GPIO line,
exclusive
should be the GPIO ID. - For features that use multiple GPIO lines, they should all be listed under
exclusive
.
F. Package (array)
package
specify the additional packages to be used with this overlay.- When the overlay is disabled, the specified package will NOT be removed.
Changelog for 0.1.9
radxa-overlays (0.1.9) jammy; urgency=medium
.
[ Alvin Xie ]
* fix: modify rock5 poe fan cooling maps
* feat: add cm3j rpi cm4 io camera overlays
* feat: add radxa cm3j rpi cm4 io 7inch touchscreen overlays
* feat: add cm3j rpi cm4 io 40pin overlays
* feat: add radxa cm3j rpi cm4 io 40 pin pwm overlay
.
[ Feng Zhang ]
* add rock 5b otg port1 dts