0.1.17

overlays

Additional device tree overlays to support different hardware on Radxa products

Build overlay dkms package

Due to the much more frequent development happening on the overlay compared to
the kernel in general, we are once again splitting the overlay into a dedicated package.

However, to guarantee the overlay is compatible with the installed kernel, this
package will be delivered as a source code package using dkms, instead of a prebuilt
binary package.

You can build the dkms package using the below commands:

sudo apt-get update
sudo apt-get build-dep --no-install-recommends -y .
make all deb

Build overlays in-tree

You will need this patch so this repo can be built with the kernel.

This is how overlays were distributed previously as part of the kernel package.
We are still supporting this for older kernels. Newer kernels like Rockchip 6.1
kernel will use the above dkms package instead.

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 build-dtbo -j$(nproc)

Please be aware this only builds a subset of overlays, and any overlays that depend on vendor headers will fail,
as this command will use the current system's kernel header.

Please take a look at the CI workflow to see how to select installed vendor kernel header.

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 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 the 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:

/ {
	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)

1. title should not contain the product name.
   rsetup will only show compatible overlays with compatible field defined. As such, do not confuse users to second guess if an overlay is truly compatible when the product name is not explicitly mentioned.
2. title should not end with a period.

B. Category (string)

1. category currently can be one of the following:
   camera, display, misc

C. Compatible (array)

1. compatible should not be an SoC unless it is truly compatible with every product using that SoC.
   rsetup will match the base device tree's compatible with the overlay's compatible. As long as one value from each match, the overlay is considered compatible. Since most products' device tree contains their SoC in compatible, setting SoC in overlay's compatible will make it compatible with every such product.
   Explicit products list should be preferred to generic SoC matching.
2. If an overlay is broken, compatible should be unknown.

D. Description (string)

1. description is a multi-line text to describe the function of the overlay. It can be the same as title with an ending period.
2. Newline in description should use \n.
3. Hardware parameters should be listed at the end to help the user connecting their devices.

E. Exclusive (array)

1. exclusive should refer to the device tree node and property.
2. For features that are muxed to a GPIO line, exclusive should be the GPIO ID.
3. For features that use multiple GPIO lines, they should all be listed under exclusive.

F. Package (array)

1. package specify the additional packages to be used with this overlay.
2. When the overlay is disabled, the specified package will NOT be removed.

Changelog for 0.1.17

radxa-overlays (0.1.17) jammy; urgency=medium
.
  [ Ken Wang ]
  * add some overlays support for rock 5t
.
  [ Chen Jiali ]
  * feat: add rockchip-uart-dma
.
  [ ZHANG Yuntian ]
  * fix: correctly disable FIQ debugger
  * refactor: reuse existing FIQ debugger overlay
  * feat: add pcf8563 overlay
.
  [ Nascs Fang ]
  * feat: add PCIe2x1 on rock 3a
.
  [ vickash ]
  * Add zero3 to rk3568-i2c5-m0.dts
  * Add rock-3c to rk3568-i2c5-m0.dts

0.1.16

overlays

Additional device tree overlays to support different hardware on Radxa products

Build overlay dkms package

Due to the much more frequent development happening on the overlay compared to
the kernel in general, we are once again splitting the overlay into a dedicated package.

However, to guarantee the overlay is compatible with the installed kernel, this
package will be delivered as a source code package using dkms, instead of a prebuilt
binary package.

You can build the dkms package using the below commands:

sudo apt-get update
sudo apt-get build-dep --no-install-recommends -y .
make all deb

Build overlays in-tree

You will need this patch so this repo can be built with the kernel.

This is how overlays were distributed previously as part of the kernel package.
We are still supporting this for older kernels. Newer kernels like Rockchip 6.1
kernel will use the above dkms package instead.

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 build-dtbo -j$(nproc)

Please be aware this only builds a subset of overlays, and any overlays that depend on vendor headers will fail,
as this command will use the current system's kernel header.

Please take a look at the CI workflow to see how to select installed vendor kernel header.

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 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 the 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:

/ {
	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)

1. title should not contain the product name.
   rsetup will only show compatible overlays with compatible field defined. As such, do not confuse users to second guess if an overlay is truly compatible when the product name is not explicitly mentioned.
2. title should not end with a period.

B. Category (string)

1. category currently can be one of the following:
   camera, display, misc

C. Compatible (array)

1. compatible should not be an SoC unless it is truly compatible with every product using that SoC.
   rsetup will match the base device tree's compatible with the overlay's compatible. As long as one value from each match, the overlay is considered compatible. Since most products' device tree contains their SoC in compatible, setting SoC in overlay's compatible will make it compatible with every such product.
   Explicit products list should be preferred to generic SoC matching.
2. If an overlay is broken, compatible should be unknown.

D. Description (string)

1. description is a multi-line text to describe the function of the overlay. It can be the same as title with an ending period.
2. Newline in description should use \n.
3. Hardware parameters should be listed at the end to help the user connecting their devices.

E. Exclusive (array)

1. exclusive should refer to the device tree node and property.
2. For features that are muxed to a GPIO line, exclusive should be the GPIO ID.
3. For features that use multiple GPIO lines, they should all be listed under exclusive.

F. Package (array)

1. package specify the additional packages to be used with this overlay.
2. When the overlay is disabled, the specified package will NOT be removed.

Changelog for 0.1.16

radxa-overlays (0.1.16) jammy; urgency=medium
.
  [ Chen Jiali ]
  * feat: rk3588: add two i2s2 sound card
.
  [ Ken Wang ]
  * update some overlays for radxa cm5 io

0.1.15

overlays

Additional device tree overlays to support different hardware on Radxa products

Build overlay dkms package

Due to the much more frequent development happening on the overlay compared to
the kernel in general, we are once again splitting the overlay into a dedicated package.

However, to guarantee the overlay is compatible with the installed kernel, this
package will be delivered as a source code package using dkms, instead of a prebuilt
binary package.

You can build the dkms package using the below commands:

sudo apt-get update
sudo apt-get build-dep --no-install-recommends -y .
make all deb

Build overlays in-tree

You will need this patch so this repo can be built with the kernel.

This is how overlays were distributed previously as part of the kernel package.
We are still supporting this for older kernels. Newer kernels like Rockchip 6.1
kernel will use the above dkms package instead.

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 build-dtbo -j$(nproc)

Please be aware this only builds a subset of overlays, and any overlays that depend on vendor headers will fail,
as this command will use the current system's kernel header.

Please take a look at the CI workflow to see how to select installed vendor kernel header.

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 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 the 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:

/ {
	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)

1. title should not contain the product name.
   rsetup will only show compatible overlays with compatible field defined. As such, do not confuse users to second guess if an overlay is truly compatible when the product name is not explicitly mentioned.
2. title should not end with a period.

B. Category (string)

1. category currently can be one of the following:
   camera, display, misc

C. Compatible (array)

1. compatible should not be an SoC unless it is truly compatible with every product using that SoC.
   rsetup will match the base device tree's compatible with the overlay's compatible. As long as one value from each match, the overlay is considered compatible. Since most products' device tree contains their SoC in compatible, setting SoC in overlay's compatible will make it compatible with every such product.
   Explicit products list should be preferred to generic SoC matching.
2. If an overlay is broken, compatible should be unknown.

D. Description (string)

1. description is a multi-line text to describe the function of the overlay. It can be the same as title with an ending period.
2. Newline in description should use \n.
3. Hardware parameters should be listed at the end to help the user connecting their devices.

E. Exclusive (array)

1. exclusive should refer to the device tree node and property.
2. For features that are muxed to a GPIO line, exclusive should be the GPIO ID.
3. For features that use multiple GPIO lines, they should all be listed under exclusive.

F. Package (array)

1. package specify the additional packages to be used with this overlay.
2. When the overlay is disabled, the specified package will NOT be removed.

Changelog for 0.1.15

radxa-overlays (0.1.15) jammy; urgency=medium
.
  [ Ken Wang ]
  * add i2c/pwm for radxa cm5 rpi cm4 io
.
  [ ZHANG Yuntian ]
  * fix: resolve some build warnings
  * fix: consolidate CI workflows
  * docs: update build guide

0.1.10

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)

1. title should not contain the product name.
   rsetup will only show compatible overlays with compatible field. As such, do not confuse users to second guess if an overlay is truly compatible when the product name is not explicitly mentioned.
2. title should not end with a period.

B. Category (string)

1. category currently can be one of the following:
   camera, display, misc

C. Compatible (array)

1. compatible should not be an SoC unless it is truly compatible with every products using that SoC.
   rsetup will match the base device tree's compatible with the overlay's compatible. As long as one value from each match, the overlay is considered compatible. Since most products' device tree contains their SoC in compatible, setting SoC in overlay's compatible will make it compatible with every such product.
   Explicit products list should be preferred to generic SoC matching.
2. If a overlay is broken, compatible should be unknown.

D. Description (string)

1. description is a multi line text to describe the function of the overlay. It can be the same as title with an ending period.
2. Newline in description should use \n.
3. Hardware parameters should be listed at the end to help user to connect their devices.

E. Exclusive (array)

1. exclusive should refer to the device tree node and property.
2. For features that are muxed to a GPIO line, exclusive should be the GPIO ID.
3. For features that use multiple GPIO lines, they should all be listed under exclusive.

F. Package (array)

1. package specify the additional packages to be used with this overlay.
2. When the overlay is disabled, the specified package will NOT be removed.

Changelog for 0.1.10

radxa-overlays (0.1.10) jammy; urgency=medium
.
  [ Feng Zhang ]
  * arm64: rockchip: add rock 5d overlays
.
  [ Ken Wang ]
  * add radxa cm5 io rpi camera v13 and update csi0 camera-module-index
  * add radxa camera 8m 219 for rock 5a/b

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)

1. title should not contain the product name.
   rsetup will only show compatible overlays with compatible field. As such, do not confuse users to second guess if an overlay is truly compatible when the product name is not explicitly mentioned.
2. title should not end with a period.

B. Category (string)

1. category currently can be one of the following:
   camera, display, misc

C. Compatible (array)

1. compatible should not be an SoC unless it is truly compatible with every products using that SoC.
   rsetup will match the base device tree's compatible with the overlay's compatible. As long as one value from each match, the overlay is considered compatible. Since most products' device tree contains their SoC in compatible, setting SoC in overlay's compatible will make it compatible with every such product.
   Explicit products list should be preferred to generic SoC matching.
2. If a overlay is broken, compatible should be unknown.

D. Description (string)

1. description is a multi line text to describe the function of the overlay. It can be the same as title with an ending period.
2. Newline in description should use \n.
3. Hardware parameters should be listed at the end to help user to connect their devices.

E. Exclusive (array)

1. exclusive should refer to the device tree node and property.
2. For features that are muxed to a GPIO line, exclusive should be the GPIO ID.
3. For features that use multiple GPIO lines, they should all be listed under exclusive.

F. Package (array)

1. package specify the additional packages to be used with this overlay.
2. 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

0.1.7

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)

1. title should not contain the product name.
   rsetup will only show compatible overlays with compatible field. As such, do not confuse users to second guess if an overlay is truly compatible when the product name is not explicitly mentioned.
2. title should not end with a period.

B. Category (string)

1. category currently can be one of the following:
   camera, display, misc

C. Compatible (array)

1. compatible should not be an SoC unless it is truly compatible with every products using that SoC.
   rsetup will match the base device tree's compatible with the overlay's compatible. As long as one value from each match, the overlay is considered compatible. Since most products' device tree contains their SoC in compatible, setting SoC in overlay's compatible will make it compatible with every such product.
   Explicit products list should be preferred to generic SoC matching.
2. If a overlay is broken, compatible should be unknown.

D. Description (string)

1. description is a multi line text to describe the function of the overlay. It can be the same as title with an ending period.
2. Newline in description should use \n.
3. Hardware parameters should be listed at the end to help user to connect their devices.

E. Exclusive (array)

1. exclusive should refer to the device tree node and property.
2. For features that are muxed to a GPIO line, exclusive should be the GPIO ID.
3. For features that use multiple GPIO lines, they should all be listed under exclusive.

F. Package (array)

1. package specify the additional packages to be used with this overlay.
2. When the overlay is disabled, the specified package will NOT be removed.

Changelog for 0.1.7

radxa-overlays (0.1.7) jammy; urgency=medium
.
  [ Alvin Xie ]
  * feat: add radxa zero3 poe overlay
  * feat: add rock 2a radxa poe overlay
  * fix: add pcie power supply for rock 2a pcie overlay
.
  [ Ken Wang ]
  * overlays: delete duplicate dts
  * add rk3588-disable-sdhci
.
  [ Nascs Fang ]
  * feat: add i2c7-m3 for rock 5a and rock 5c
.
  [ CodeChenL ]
  * fix: installation with deb without compile rk3588 can overlays

0.1.6

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)

1. title should not contain the product name.
   rsetup will only show compatible overlays with compatible field. As such, do not confuse users to second guess if an overlay is truly compatible when the product name is not explicitly mentioned.
2. title should not end with a period.

B. Category (string)

1. category currently can be one of the following:
   camera, display, misc

C. Compatible (array)

1. compatible should not be an SoC unless it is truly compatible with every products using that SoC.
   rsetup will match the base device tree's compatible with the overlay's compatible. As long as one value from each match, the overlay is considered compatible. Since most products' device tree contains their SoC in compatible, setting SoC in overlay's compatible will make it compatible with every such product.
   Explicit products list should be preferred to generic SoC matching.
2. If a overlay is broken, compatible should be unknown.

D. Description (string)

1. description is a multi line text to describe the function of the overlay. It can be the same as title with an ending period.
2. Newline in description should use \n.
3. Hardware parameters should be listed at the end to help user to connect their devices.

E. Exclusive (array)

1. exclusive should refer to the device tree node and property.
2. For features that are muxed to a GPIO line, exclusive should be the GPIO ID.
3. For features that use multiple GPIO lines, they should all be listed under exclusive.

F. Package (array)

1. package specify the additional packages to be used with this overlay.
2. When the overlay is disabled, the specified package will NOT be removed.

Changelog for 0.1.6

radxa-overlays (0.1.6) jammy; urgency=medium
.
  [ ZHANG Yuntian ]
  * feat: add radxa-zero-emmc-full-speed.dts
  * format: use multiline text instead of \n
  * fix: use constant instead of magic numbers
  * format: reorder overlays alphabetically
  * feat: add CM3 LVDS overlay
.
  [ Alvin Xie ]
  * rock 5a/5c: modify rpi 7inch display proch
  * rock 5c: add spi module support
.
  [ RadxaMitchell ]
  * update rk3588-i2c6-m0.dts
  * fix: rk3588-spi0-m1-cs0-mcp2515-8mhz.dts
.
  [ Feng Zhang ]
  * arm64: overlays: Add overlay description for rock 5c

0.1.2

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)

1. title should not contain the product name.
   rsetup will only show compatible overlays with compatible field. As such, do not confuse users to second guess if an overlay is truly compatible when the product name is not explicitly mentioned.
2. title should not end with a period.

B. Category (string)

1. category currently can be one of the following:
   camera, display, misc

C. Compatible (array)

1. compatible should not be an SoC unless it is truly compatible with every products using that SoC.
   rsetup will match the base device tree's compatible with the overlay's compatible. As long as one value from each match, the overlay is considered compatible. Since most products' device tree contains their SoC in compatible, setting SoC in overlay's compatible will make it compatible with every such product.
   Explicit products list should be preferred to generic SoC matching.
2. If a overlay is broken, compatible should be unknown.

D. Description (string)

1. description is a multi line text to describe the function of the overlay. It can be the same as title with an ending period.
2. Newline in description should use \n.
3. Hardware parameters should be listed at the end to help user to connect their devices.

E. Exclusive (array)

1. exclusive should refer to the device tree node and property.
2. For features that are muxed to a GPIO line, exclusive should be the GPIO ID.
3. For features that use multiple GPIO lines, they should all be listed under exclusive.

F. Package (array)

1. package specify the additional packages to be used with this overlay.
2. When the overlay is disabled, the specified package will NOT be removed.

Changelog for 0.1.2

radxa-overlays (0.1.2) jammy; urgency=medium
.
  [ ZHANG Yuntian ]
  * fix: trigger rebuild_overlays after installing

0.1.0

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)

1. title should not contain the product name.
   rsetup will only show compatible overlays with compatible field. As such, do not confuse users to second guess if an overlay is truly compatible when the product name is not explicitly mentioned.
2. title should not end with a period.

B. Category (string)

1. category currently can be one of the following:
   camera, display, misc

C. Compatible (array)

1. compatible should not be an SoC unless it is truly compatible with every products using that SoC.
   rsetup will match the base device tree's compatible with the overlay's compatible. As long as one value from each match, the overlay is considered compatible. Since most products' device tree contains their SoC in compatible, setting SoC in overlay's compatible will make it compatible with every such product.
   Explicit products list should be preferred to generic SoC matching.
2. If a overlay is broken, compatible should be unknown.

D. Description (string)

1. description is a multi line text to describe the function of the overlay. It can be the same as title with an ending period.
2. Newline in description should use \n.
3. Hardware parameters should be listed at the end to help user to connect their devices.

E. Exclusive (array)

1. exclusive should refer to the device tree node and property.
2. For features that are muxed to a GPIO line, exclusive should be the GPIO ID.
3. For features that use multiple GPIO lines, they should all be listed under exclusive.

F. Package (array)

1. package specify the additional packages to be used with this overlay.
2. When the overlay is disabled, the specified package will NOT be removed.

Changelog for 0.1.0

radxa-overlays (0.1.0) jammy; urgency=medium
.
  [ "Radxa Computer Co., Ltd" ]
  * Initial release