[PATCH 0/3] Add support for BeagleBone Black RevD

[PATCH 0/3] Add support for BeagleBone Black RevD

[Robert Nelson]

The BeagleBoard.org BeagleBone Black RevD and Industrial (00D0/EID0) are
redesigns of the BeagleBone Black Rev C3. They feature an IT66122 HDMI
PHY to replace the EOL NXP TDA19988.

Signed-off-by: Robert Nelson <robertcnelson@gmail.com>
---
Robert Nelson (3):
      dt-bindings: omap: Add BeagleBone Black RevD
      arm: dts: omap: Add support for BeagleBone Black RevD
      arm: dts: ti: Enable overlays for BeagleBone Black RevD

 Documentation/devicetree/bindings/arm/ti/omap.yaml |   1 +
 arch/arm/boot/dts/ti/omap/Makefile                 |   2 +
 .../dts/ti/omap/am335x-boneblack-ite-hdmi.dtsi     | 184 +++++++++++++++++++++
 .../arm/boot/dts/ti/omap/am335x-boneblack-revd.dts | 166 +++++++++++++++++++
 4 files changed, 353 insertions(+)
---
base-commit: cee9395acd8043be0644b25c34bfa86623f2b935
change-id: 20260901-v7-3-rc1-beaglebone-black-revd-7cab3f1a6563

Best regards,
--  
Robert Nelson <robertcnelson@gmail.com>

[PATCH 1/3] dt-bindings: omap: Add BeagleBone Black RevD

[Robert Nelson]

Document the beagle,am335x-bone-black-revd compatible string in the
appropriate place within the omap family binding file.

Signed-off-by: Robert Nelson <robertcnelson@gmail.com>
---
 Documentation/devicetree/bindings/arm/ti/omap.yaml | 1 +
 1 file changed, 1 insertion(+)

diff --git a/Documentation/devicetree/bindings/arm/ti/omap.yaml b/Documentation/devicetree/bindings/arm/ti/omap.yaml
index f694dcbf2348..9666c455628d 100644
--- a/Documentation/devicetree/bindings/arm/ti/omap.yaml
+++ b/Documentation/devicetree/bindings/arm/ti/omap.yaml
@@ -104,6 +104,7 @@ properties:
       - description: TI AM33 based platform
         items:
           - enum:
+              - beagle,am335x-bone-black-revd
               - compulab,cm-t335
               - moxa,uc-8100-me-t
               - novatech,am335x-lxm

-- 
2.55.0

[PATCH 2/3] arm: dts: omap: Add support for BeagleBone Black RevD

[Robert Nelson]

The BeagleBoard.org BeagleBone Black RevD and Industrial (00D0/EID0) are
redesigns of the BeagleBone Black Rev C3. They feature an IT66122 HDMI PHY to
replace the EOL NXP TDA19988. Additionally, these models include a larger eMMC
capacity to address the limited availability of 4GB modules.

Signed-off-by: Robert Nelson <robertcnelson@gmail.com>
---
 arch/arm/boot/dts/ti/omap/Makefile                 |   1 +
 .../dts/ti/omap/am335x-boneblack-ite-hdmi.dtsi     | 184 +++++++++++++++++++++
 .../arm/boot/dts/ti/omap/am335x-boneblack-revd.dts | 166 +++++++++++++++++++
 3 files changed, 351 insertions(+)

diff --git a/arch/arm/boot/dts/ti/omap/Makefile b/arch/arm/boot/dts/ti/omap/Makefile
index 498c36ccb5ea..55cab3e8a05c 100644
--- a/arch/arm/boot/dts/ti/omap/Makefile
+++ b/arch/arm/boot/dts/ti/omap/Makefile
@@ -97,6 +97,7 @@ dtb-$(CONFIG_SOC_AM33XX) += \
 	am335x-baltos-ir5221.dtb \
 	am335x-bone.dtb \
 	am335x-boneblack.dtb \
+	am335x-boneblack-revd.dtb \
 	am335x-boneblack-wireless.dtb \
 	am335x-boneblue.dtb \
 	am335x-bonegreen.dtb \
diff --git a/arch/arm/boot/dts/ti/omap/am335x-boneblack-ite-hdmi.dtsi b/arch/arm/boot/dts/ti/omap/am335x-boneblack-ite-hdmi.dtsi
new file mode 100644
index 000000000000..77dd7d9aa57d
--- /dev/null
+++ b/arch/arm/boot/dts/ti/omap/am335x-boneblack-ite-hdmi.dtsi
@@ -0,0 +1,184 @@
+// SPDX-License-Identifier: GPL-2.0-only
+/*
+ * https://github.com/beagleboard/beaglebone-black
+ *
+ * Copyright (C) 2026 Texas Instruments Incorporated - https://www.ti.com/
+ * Copyright (C) 2026 Robert Nelson, BeagleBoard.org Foundation
+ */
+
+#include <dt-bindings/interrupt-controller/irq.h>
+
+/ {
+	connector-hdmi {
+		compatible = "hdmi-connector";
+		label = "hdmi";
+		type = "a";
+		port {
+			hdmi_connector_in: endpoint {
+				remote-endpoint = <&it66122_out>;
+			};
+		};
+	};
+
+	it66122_vcn18_fixed: fixedregulator1 {
+		compatible = "regulator-fixed";
+		regulator-name = "it66122_vcn18_fixed";
+		regulator-min-microvolt = <1800000>;
+		regulator-max-microvolt = <1800000>;
+	};
+
+	it66122_vcn12_fixed: fixedregulator2 {
+		compatible = "regulator-fixed";
+		regulator-name = "it66122_vcn12_fixed";
+		regulator-min-microvolt = <1200000>;
+		regulator-max-microvolt = <1200000>;
+	};
+};
+
+&am33xx_pinmux {
+	nxp_hdmi_bonelt_pins: nxp-hdmi-bonelt-pins {
+		pinctrl-single,pins = <
+			AM33XX_PADCONF(AM335X_PIN_XDMA_EVENT_INTR0, PIN_OUTPUT_PULLDOWN, MUX_MODE3)
+			AM33XX_PADCONF(AM335X_PIN_LCD_DATA0, PIN_OUTPUT, MUX_MODE0)
+			AM33XX_PADCONF(AM335X_PIN_LCD_DATA1, PIN_OUTPUT, MUX_MODE0)
+			AM33XX_PADCONF(AM335X_PIN_LCD_DATA2, PIN_OUTPUT, MUX_MODE0)
+			AM33XX_PADCONF(AM335X_PIN_LCD_DATA3, PIN_OUTPUT, MUX_MODE0)
+			AM33XX_PADCONF(AM335X_PIN_LCD_DATA4, PIN_OUTPUT, MUX_MODE0)
+			AM33XX_PADCONF(AM335X_PIN_LCD_DATA5, PIN_OUTPUT, MUX_MODE0)
+			AM33XX_PADCONF(AM335X_PIN_LCD_DATA6, PIN_OUTPUT, MUX_MODE0)
+			AM33XX_PADCONF(AM335X_PIN_LCD_DATA7, PIN_OUTPUT, MUX_MODE0)
+			AM33XX_PADCONF(AM335X_PIN_LCD_DATA8, PIN_OUTPUT, MUX_MODE0)
+			AM33XX_PADCONF(AM335X_PIN_LCD_DATA9, PIN_OUTPUT, MUX_MODE0)
+			AM33XX_PADCONF(AM335X_PIN_LCD_DATA10, PIN_OUTPUT, MUX_MODE0)
+			AM33XX_PADCONF(AM335X_PIN_LCD_DATA11, PIN_OUTPUT, MUX_MODE0)
+			AM33XX_PADCONF(AM335X_PIN_LCD_DATA12, PIN_OUTPUT, MUX_MODE0)
+			AM33XX_PADCONF(AM335X_PIN_LCD_DATA13, PIN_OUTPUT, MUX_MODE0)
+			AM33XX_PADCONF(AM335X_PIN_LCD_DATA14, PIN_OUTPUT, MUX_MODE0)
+			AM33XX_PADCONF(AM335X_PIN_LCD_DATA15, PIN_OUTPUT, MUX_MODE0)
+			AM33XX_PADCONF(AM335X_PIN_LCD_VSYNC, PIN_OUTPUT_PULLDOWN, MUX_MODE0)
+			AM33XX_PADCONF(AM335X_PIN_LCD_HSYNC, PIN_OUTPUT_PULLDOWN, MUX_MODE0)
+			AM33XX_PADCONF(AM335X_PIN_LCD_PCLK, PIN_OUTPUT_PULLDOWN, MUX_MODE0)
+			AM33XX_PADCONF(AM335X_PIN_LCD_AC_BIAS_EN, PIN_OUTPUT_PULLDOWN, MUX_MODE0)
+		>;
+	};
+
+	hdmi_gpio_pins_default: hdmi-gpio-default-pins {
+		pinctrl-single,pins = <
+			AM33XX_PADCONF(AM335X_PIN_GPMC_A9, PIN_INPUT_PULLUP, MUX_MODE7)	/* HDMI_INT gpmc_a9.GPIO1_25 */
+			AM33XX_PADCONF(AM335X_PIN_UART0_RTSN, PIN_OUTPUT_PULLUP, MUX_MODE7) /* HDMI_RESET uart0_rtsn.GPIO1_9 */
+		>;
+	};
+
+	mcasp0_pins: mcasp0-pins {
+		pinctrl-single,pins = <
+			AM33XX_PADCONF(AM335X_PIN_MCASP0_AHCLKX, PIN_INPUT_PULLUP, MUX_MODE0) /* mcasp0_ahcklx.mcasp0_ahclkx */
+			AM33XX_PADCONF(AM335X_PIN_MCASP0_AHCLKR, PIN_OUTPUT_PULLDOWN, MUX_MODE2) /* mcasp0_ahclkr.mcasp0_axr2*/
+			AM33XX_PADCONF(AM335X_PIN_MCASP0_FSX, PIN_OUTPUT_PULLUP, MUX_MODE0)
+			AM33XX_PADCONF(AM335X_PIN_MCASP0_ACLKX, PIN_OUTPUT_PULLDOWN, MUX_MODE0)
+			AM33XX_PADCONF(AM335X_PIN_GPMC_A11, PIN_OUTPUT_PULLDOWN, MUX_MODE7) /* gpmc_a11.GPIO1_27 */
+		>;
+	};
+};
+
+&lcdc {
+	status = "okay";
+	pinctrl-names = "default";
+	pinctrl-0 = <&nxp_hdmi_bonelt_pins>;
+
+	/* If you want to get 24 bit RGB and 16 BGR mode instead of
+	 * current 16 bit RGB and 24 BGR modes, set the propety
+	 * below to "crossed" and uncomment the video-ports -property
+	 * in tda19988 node.
+	 */
+	blue-and-red-wiring = "straight";
+
+	port {
+		lcdc_0: endpoint@0 {
+			remote-endpoint = <&it66122_in>;
+		};
+	};
+};
+
+&i2c0 {
+	it66122: bridge-hdmi@4c {
+		compatible = "ite,it66122";
+		reg = <0x4c>;
+		pinctrl-names = "default";
+		pinctrl-0 = <&hdmi_gpio_pins_default>;
+		vcn33-supply = <&vmmcsd_fixed>;
+		vcn18-supply = <&it66122_vcn18_fixed>;
+		vrf12-supply = <&it66122_vcn12_fixed>;
+		reset-gpios = <&gpio1 9 GPIO_ACTIVE_LOW>;
+		interrupt-parent = <&gpio1>;
+		interrupts = <25 IRQ_TYPE_EDGE_FALLING>;
+		#sound-dai-cells = <0>;
+
+		ports {
+			#address-cells = <1>;
+			#size-cells = <0>;
+
+			port@0 {
+				reg = <0>;
+
+				it66122_in: endpoint {
+					bus-width = <24>;
+					remote-endpoint = <&lcdc_0>;
+				};
+			};
+
+			port@1 {
+				reg = <1>;
+
+				it66122_out: endpoint {
+					remote-endpoint = <&hdmi_connector_in>;
+				};
+			};
+		};
+	};
+};
+
+&mcasp0 {
+	#sound-dai-cells = <0>;
+	pinctrl-names = "default";
+	pinctrl-0 = <&mcasp0_pins>;
+	status = "okay";
+	op-mode = <0>;	/* MCASP_IIS_MODE */
+	tdm-slots = <2>;
+	serial-dir = <	/* 0: INACTIVE, 1: TX, 2: RX */
+			0 0 1 0
+		>;
+	tx-num-evt = <32>;
+	rx-num-evt = <32>;
+};
+
+/ {
+	clk_mcasp0_fixed: clk_mcasp0_fixed {
+		#clock-cells = <0>;
+		compatible = "fixed-clock";
+		clock-frequency = <24576000>;
+	};
+
+	clk_mcasp0: clk_mcasp0 {
+		#clock-cells = <0>;
+		compatible = "gpio-gate-clock";
+		clocks = <&clk_mcasp0_fixed>;
+		enable-gpios = <&gpio1 27 0>; /* BeagleBone Black Clk enable on GPIO1_27 */
+	};
+
+	sound {
+		compatible = "simple-audio-card";
+		simple-audio-card,name = "TI BeagleBone Black";
+		simple-audio-card,format = "i2s";
+		simple-audio-card,bitclock-master = <&dailink0_master>;
+		simple-audio-card,frame-master = <&dailink0_master>;
+
+		dailink0_master: simple-audio-card,cpu {
+			sound-dai = <&mcasp0>;
+			clocks = <&clk_mcasp0>;
+		};
+
+		simple-audio-card,codec {
+			sound-dai = <&it66122>;
+		};
+	};
+};
diff --git a/arch/arm/boot/dts/ti/omap/am335x-boneblack-revd.dts b/arch/arm/boot/dts/ti/omap/am335x-boneblack-revd.dts
new file mode 100644
index 000000000000..fe9536d5f55e
--- /dev/null
+++ b/arch/arm/boot/dts/ti/omap/am335x-boneblack-revd.dts
@@ -0,0 +1,166 @@
+// SPDX-License-Identifier: GPL-2.0-only
+/*
+ * https://github.com/beagleboard/beaglebone-black
+ *
+ * Copyright (C) 2026 Texas Instruments Incorporated - https://www.ti.com/
+ * Copyright (C) 2026 Robert Nelson, BeagleBoard.org Foundation
+ */
+/dts-v1/;
+
+#include "am33xx.dtsi"
+#include "am335x-bone-common.dtsi"
+#include "am335x-boneblack-common.dtsi"
+#include "am335x-boneblack-ite-hdmi.dtsi"
+
+/ {
+	model = "TI AM335x BeagleBone Black Rev D";
+	compatible = "beagle,am335x-bone-black-revd", "ti,am33xx";
+};
+
+&gpio0 {
+	gpio-line-names =
+		"[mdio_data]",
+		"[mdio_clk]",
+		"P9_22 [spi0_sclk]",
+		"P9_21 [spi0_d0]",
+		"P9_18 [spi0_d1]",
+		"P9_17 [spi0_cs0]",
+		"[mmc0_cd]",
+		"P9_42A [ecappwm0]",
+		"P8_35 [lcd d12]",
+		"P8_33 [lcd d13]",
+		"P8_31 [lcd d14]",
+		"P8_32 [lcd d15]",
+		"P9_20 [i2c2_sda]",
+		"P9_19 [i2c2_scl]",
+		"P9_26 [uart1_rxd]",
+		"P9_24 [uart1_txd]",
+		"[rmii1_txd3]",
+		"[rmii1_txd2]",
+		"[usb0_drvvbus]",
+		"[hdmi cec]",
+		"P9_41B",
+		"[rmii1_txd1]",
+		"P8_19 [ehrpwm2a]",
+		"P8_13 [ehrpwm2b]",
+		"NC",
+		"NC",
+		"P8_14",
+		"P8_17",
+		"[rmii1_txd0]",
+		"[rmii1_refclk]",
+		"P9_11 [uart4_rxd]",
+		"P9_13 [uart4_txd]";
+};
+
+&gpio1 {
+	gpio-line-names =
+		"P8_25 [mmc1_dat0]",
+		"[mmc1_dat1]",
+		"P8_5 [mmc1_dat2]",
+		"P8_6 [mmc1_dat3]",
+		"P8_23 [mmc1_dat4]",
+		"P8_22 [mmc1_dat5]",
+		"P8_3 [mmc1_dat6]",
+		"P8_4 [mmc1_dat7]",
+		"NC",
+		"NC",
+		"NC",
+		"NC",
+		"P8_12",
+		"P8_11",
+		"P8_16",
+		"P8_15",
+		"P9_15A",
+		"P9_23",
+		"P9_14 [ehrpwm1a]",
+		"P9_16 [ehrpwm1b]",
+		"[emmc rst]",
+		"[usr0 led]",
+		"[usr1 led]",
+		"[usr2 led]",
+		"[usr3 led]",
+		"[hdmi irq]",
+		"[usb vbus oc]",
+		"[hdmi audio]",
+		"P9_12",
+		"P8_26",
+		"P8_21 [emmc]",
+		"P8_20 [emmc]";
+};
+
+&gpio2 {
+	gpio-line-names =
+		"P9_15B",
+		"P8_18",
+		"P8_7",
+		"P8_8",
+		"P8_10",
+		"P8_9",
+		"P8_45 [hdmi]",
+		"P8_46 [hdmi]",
+		"P8_43 [hdmi]",
+		"P8_44 [hdmi]",
+		"P8_41 [hdmi]",
+		"P8_42 [hdmi]",
+		"P8_39 [hdmi]",
+		"P8_40 [hdmi]",
+		"P8_37 [hdmi]",
+		"P8_38 [hdmi]",
+		"P8_36 [hdmi]",
+		"P8_34 [hdmi]",
+		"[rmii1_rxd3]",
+		"[rmii1_rxd2]",
+		"[rmii1_rxd1]",
+		"[rmii1_rxd0]",
+		"P8_27 [hdmi]",
+		"P8_29 [hdmi]",
+		"P8_28 [hdmi]",
+		"P8_30 [hdmi]",
+		"[mmc0_dat3]",
+		"[mmc0_dat2]",
+		"[mmc0_dat1]",
+		"[mmc0_dat0]",
+		"[mmc0_clk]",
+		"[mmc0_cmd]";
+};
+
+&gpio3 {
+	gpio-line-names =
+		"[mii col]",
+		"[mii crs]",
+		"[mii rx err]",
+		"[mii tx en]",
+		"[mii rx dv]",
+		"[i2c0 sda]",
+		"[i2c0 scl]",
+		"[jtag emu0]",
+		"[jtag emu1]",
+		"[mii tx clk]",
+		"[mii rx clk]",
+		"NC",
+		"NC",
+		"[usb vbus en]",
+		"P9_31 [spi1_sclk]",
+		"P9_29 [spi1_d0]",
+		"P9_30 [spi1_d1]",
+		"P9_28 [spi1_cs0]",
+		"P9_42B [ecappwm0]",
+		"P9_27",
+		"P9_41A",
+		"P9_25",
+		"NC",
+		"NC",
+		"NC",
+		"NC",
+		"NC",
+		"NC",
+		"NC",
+		"NC",
+		"NC",
+		"NC";
+};
+
+&baseboard_eeprom {
+	vcc-supply = <&ldo4_reg>;
+};

-- 
2.55.0

[PATCH 3/3] arm: dts: ti: Enable overlays for BeagleBone Black RevD

[Robert Nelson]

Allow overlays to be applied to am335x BeagleBone Black RevD.

Signed-off-by: Robert Nelson <robertcnelson@gmail.com>
---
 arch/arm/boot/dts/ti/omap/Makefile | 1 +
 1 file changed, 1 insertion(+)

diff --git a/arch/arm/boot/dts/ti/omap/Makefile b/arch/arm/boot/dts/ti/omap/Makefile
index 55cab3e8a05c..62de820c9b2a 100644
--- a/arch/arm/boot/dts/ti/omap/Makefile
+++ b/arch/arm/boot/dts/ti/omap/Makefile
@@ -190,6 +190,7 @@ dtb-$(CONFIG_SOC_TI81XX) += \
 # Enable support for device-tree overlays
 DTC_FLAGS_am335x-bone += -@
 DTC_FLAGS_am335x-boneblack += -@
+DTC_FLAGS_am335x-boneblack-revd += -@
 DTC_FLAGS_am335x-boneblack-wireless += -@
 DTC_FLAGS_am335x-bonegreen += -@
 DTC_FLAGS_am335x-bonegreen-wireless += -@

-- 
2.55.0

Re: [PATCH 1/3] dt-bindings: omap: Add BeagleBone Black RevD

[sashiko-bot]

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] The new `beagle,am335x-bone-black-revd` compatible string is placed in a 2-item constraint block, structurally preventing the use of standard BeagleBone fallback strings.
--

commit 17e0af4d26654f2aa0193ef1f9c56643b10d76e4
Author: Robert Nelson <robertcnelson@gmail.com>

dt-bindings: omap: Add BeagleBone Black RevD

This commit adds the compatible string for the BeagleBone Black RevD to
the TI OMAP device tree binding schema.

> diff --git a/Documentation/devicetree/bindings/arm/ti/omap.yaml b/Documentation/devicetree/bindings/arm/ti/omap.yaml
> --- a/Documentation/devicetree/bindings/arm/ti/omap.yaml
> +++ b/Documentation/devicetree/bindings/arm/ti/omap.yaml
> @@ -104,6 +104,7 @@ properties:
>        - description: TI AM33 based platform
>          items:
>            - enum:
> +              - beagle,am335x-bone-black-revd

[Severity: Medium]
Does placing this compatible string in this specific block prevent the use
of standard BeagleBone fallback strings?

Because this block under properties.compatible.oneOf is configured for exactly
two items, it restricts the compatible property to just this new string and
ti,am33xx. This structurally prohibits including standard BeagleBone fallback
strings, such as ti,am335x-bone-black and ti,am335x-bone.

Attempting to define a standard 3-item or 4-item compatible string hierarchy
for the RevD board in the device tree might fail dt_binding_check. Could this
cause ecosystem interoperability issues if it forces the omission of fallbacks
needed for U-Boot quirks and userspace board identification?

>                - compulab,cm-t335
>                - moxa,uc-8100-me-t
>                - novatech,am335x-lxm

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260901-v7-3-rc1-beaglebone-black-revd-v1-0-f521950b777a@gmail.com?part=1

Re: [PATCH 2/3] arm: dts: omap: Add support for BeagleBone Black RevD

[sashiko-bot]

Thank you for your contribution! Sashiko AI review found 7 potential issue(s) to consider:
- [High] Hardware/Driver mismatch: The BeagleBone Black physically routes 16-bit video data, but the DT and bridge driver are configured for a 24-bit bus, leading to severely corrupted video output.
- [Medium] The IT66122 bridge interrupt is incorrectly configured as edge-falling instead of level-low, which can lead to missed interrupts.
- [Medium] The board compatible string is missing standard fallback identifiers, breaking userspace board detection.
- [Low] The new board compatible string 'beagle,am335x-bone-black-revd' is not documented in the Devicetree bindings.
- [Low] Stale gpio-line-names entry masks the HDMI reset pin (GPIO1_9) as 'NC' (Not Connected).
- [Low] The lcdc endpoint node uses a unit address without a matching reg property, causing dtc warnings.
- [Low] A stale comment incorrectly references the removed TDA19988 HDMI framer node.
--

commit d7b1924005badde2a155d4ba4a4cb12a5f9be451
Author: Robert Nelson <robertcnelson@gmail.com>

arm: dts: omap: Add support for BeagleBone Black RevD

The BeagleBoard.org BeagleBone Black RevD and Industrial (00D0/EID0) are
redesigns of the BeagleBone Black Rev C3. They feature an IT66122 HDMI PHY to
replace the EOL NXP TDA19988. Additionally, these models include a larger eMMC
capacity to address the limited availability of 4GB modules.

> diff --git a/arch/arm/boot/dts/ti/omap/am335x-boneblack-ite-hdmi.dtsi b/arch/arm/boot/dts/ti/omap/am335x-boneblack-ite-hdmi.dtsi
> new file mode 100644
> index 0000000000000..77dd7d9aa57d9
> --- /dev/null
> +++ b/arch/arm/boot/dts/ti/omap/am335x-boneblack-ite-hdmi.dtsi
> @@ -0,0 +1,184 @@

[ ... ]

> +&lcdc {
> +	status = "okay";
> +	pinctrl-names = "default";
> +	pinctrl-0 = <&nxp_hdmi_bonelt_pins>;
> +
> +	/* If you want to get 24 bit RGB and 16 BGR mode instead of
> +	 * current 16 bit RGB and 24 BGR modes, set the propety
> +	 * below to "crossed" and uncomment the video-ports -property
> +	 * in tda19988 node.
> +	 */

[Severity: Low]
Is this comment still accurate? The comment instructs to uncomment a property
in the tda19988 node, but the Rev D board replaced this chip with the IT66122.

> +	blue-and-red-wiring = "straight";
> +
> +	port {
> +		lcdc_0: endpoint@0 {

[Severity: Low]
Does this node need a matching reg property? The node uses a unit address
(endpoint@0) but lacks a corresponding reg = <0>; property, which can
trigger devicetree compiler unit_address_vs_reg warnings.

> +			remote-endpoint = <&it66122_in>;
> +		};
> +	};
> +};
> +
> +&i2c0 {
> +	it66122: bridge-hdmi@4c {
> +		compatible = "ite,it66122";
> +		reg = <0x4c>;
> +		pinctrl-names = "default";
> +		pinctrl-0 = <&hdmi_gpio_pins_default>;
> +		vcn33-supply = <&vmmcsd_fixed>;
> +		vcn18-supply = <&it66122_vcn18_fixed>;
> +		vrf12-supply = <&it66122_vcn12_fixed>;
> +		reset-gpios = <&gpio1 9 GPIO_ACTIVE_LOW>;
> +		interrupt-parent = <&gpio1>;
> +		interrupts = <25 IRQ_TYPE_EDGE_FALLING>;

[Severity: Medium]
Should this interrupt trigger type be level-low instead of edge-falling?

I2C bridge chips like the IT66122 use active-low, open-drain interrupts.
If configured as edge-falling, a second interrupt condition occurring while
the line is already low won't generate a new falling edge. Because the kernel
uses a threaded interrupt handler for this device, this can race with the
clearing of the first event and lead to missed interrupts.

> +		#sound-dai-cells = <0>;
> +
> +		ports {
> +			#address-cells = <1>;
> +			#size-cells = <0>;
> +
> +			port@0 {
> +				reg = <0>;
> +
> +				it66122_in: endpoint {
> +					bus-width = <24>;

[Severity: High]
Does this bus-width configuration mismatch the physical hardware?

The BeagleBone Black routes only 16 LCD data pins (LCD_DATA0 to LCD_DATA15)
for the display, as pins 16-23 are reserved for eMMC. This can be seen in
the pinmux setup in nxp_hdmi_bonelt_pins.

However, configuring the IT66122 endpoint for a 24-bit bus causes the
bridge driver to request a 24-bit input format. The bridge will then read
floating or eMMC data on its upper 8 bits, which leads to severely corrupted
video output on HDMI.

> +					remote-endpoint = <&lcdc_0>;
> +				};
> +			};

[ ... ]

> diff --git a/arch/arm/boot/dts/ti/omap/am335x-boneblack-revd.dts b/arch/arm/boot/dts/ti/omap/am335x-boneblack-revd.dts
> new file mode 100644
> index 0000000000000..fe9536d5f55ea
> --- /dev/null
> +++ b/arch/arm/boot/dts/ti/omap/am335x-boneblack-revd.dts
> @@ -0,0 +1,166 @@

[ ... ]

> +/ {
> +	model = "TI AM335x BeagleBone Black Rev D";
> +	compatible = "beagle,am335x-bone-black-revd", "ti,am33xx";

[Severity: Medium]
Are the standard BeagleBone fallback identifiers intentionally omitted?

This compatible string omits standard fallbacks like "ti,am335x-bone-black"
and "ti,am335x-bone" used by all other variants. Without them, existing
userspace tools, cape managers, and distributions will fail to detect the
board and apply BeagleBone-specific quirks.

[Severity: Low]
Also, has the new board compatible string "beagle,am335x-bone-black-revd"
been documented in the Devicetree bindings? Omitting it from the bindings
will produce validation warnings during devicetree checks.

> +};
> +
> +&gpio0 {

[ ... ]

> +&gpio1 {
> +	gpio-line-names =
> +		"P8_25 [mmc1_dat0]",
> +		"[mmc1_dat1]",
> +		"P8_5 [mmc1_dat2]",
> +		"P8_6 [mmc1_dat3]",
> +		"P8_23 [mmc1_dat4]",
> +		"P8_22 [mmc1_dat5]",
> +		"P8_3 [mmc1_dat6]",
> +		"P8_4 [mmc1_dat7]",
> +		"NC",
> +		"NC",

[Severity: Low]
Is this "NC" label accurate for GPIO1_9?

The am335x-boneblack-ite-hdmi.dtsi file routes the IT66122 bridge's
active-low reset to GPIO1_9. Retaining the old "NC" (Not Connected)
label masks the HDMI reset pin from userspace tools like libgpiod.

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260901-v7-3-rc1-beaglebone-black-revd-v1-0-f521950b777a@gmail.com?part=2

Re: [PATCH 1/3] dt-bindings: omap: Add BeagleBone Black RevD

[Conor Dooley]

[-- Attachment #1: Type: text/plain, Size: 1040 bytes --]

On Tue, Sep 01, 2026 at 04:42:21PM -0500, Robert Nelson wrote:
> Document the beagle,am335x-bone-black-revd compatible string in the
> appropriate place within the omap family binding file.
> 
> Signed-off-by: Robert Nelson <robertcnelson@gmail.com>

Acked-by: Conor Dooley <conor.dooley@microchip.com>
pw-bot: not-applicable

> ---
>  Documentation/devicetree/bindings/arm/ti/omap.yaml | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/Documentation/devicetree/bindings/arm/ti/omap.yaml b/Documentation/devicetree/bindings/arm/ti/omap.yaml
> index f694dcbf2348..9666c455628d 100644
> --- a/Documentation/devicetree/bindings/arm/ti/omap.yaml
> +++ b/Documentation/devicetree/bindings/arm/ti/omap.yaml
> @@ -104,6 +104,7 @@ properties:
>        - description: TI AM33 based platform
>          items:
>            - enum:
> +              - beagle,am335x-bone-black-revd
>                - compulab,cm-t335
>                - moxa,uc-8100-me-t
>                - novatech,am335x-lxm
> 
> -- 
> 2.55.0
> 

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]