ARM: dts: imx: fix ldb related CHECK_DTBS warnings
Subsystems (6)
v3 cover ARM: dts: imx: fix ldb related CHECK_DTBS warnings
Fix ldb related CHECK_DTBS warnings
---
Changes in v3:
- add ranges
- collect rob's acked-by tags
- Link to v2: https://patch.msgid.link/[email protected]
Changes in v2:
- Remove status = disabled at binding example
- collect rob's reviewed-by tags.
- Link to v1: https://patch.msgid.link/[email protected]
---
Frank Li (4):
dt-bindings: display: bridge: ldb: allow a single reg for fsl,imx6sx-ldb
dt-bindings: soc: imx-iomuxc-gpr: allow bridge@18 as child node
dt-bindings: display: lcdif: Allow display0 child node for i.MX6UL
ARM: dts: imx6ul-tx6ul: rename disp0 to display0
.../bindings/display/bridge/fsl,ldb.yaml | 23 ++++---- .../devicetree/bindings/display/fsl,lcdif.yaml | 1 + .../bindings/soc/imx/fsl,imx-iomuxc-gpr.yaml | 62 ++++++++++++++++++++++ arch/arm/boot/dts/nxp/imx/imx6ul-tx6ul.dtsi | 2 +- 4 files changed, 78 insertions(+), 10 deletions(-)
---
base-commit: 6c94b38b83a04c43ea49004275f0391404051093
change-id: 20260708-arm_dts_ldb-9ca4c548dded
Best regards,
Signature · 1 line
Frank Li <[email protected]>
PATCH v3 1/4 dt-bindings: display: bridge: ldb: allow a single reg for fsl,imx6sx-ldb
From: Frank Li <[email protected]>
The i.MX6SX LDB only provides a single register region for the LDB block, while other supported LDB variants require two register regions.
Update the binding schema to allow a single reg entry for fsl,imx6sx-ldb while keeping the existing constraints unchanged for the other compatible strings.
Fix below DTB_CHECK warings:
arch/arm/boot/dts/nxp/imx/imx6sx-nitrogen6sx.dtb: bridge@18 (fsl,imx6sx-ldb): reg: [[24, 4]] is too short
---
Related two theads:
- https://lore.kernel.org/imx/[email protected]/
Mixing the addressable and non-addressable child nodes is allowed according to discussion [1].
--- .../bindings/display/bridge/fsl,ldb.yaml | 23 +++++++++++++--------- 1 file changed, 14 insertions(+), 9 deletions(-)
Documentation/devicetree/bindings/display/bridge/fsl,ldb.yaml +14 -9
@@ -28,9 +28,11 @@ properties: const: ldb reg: + minItems: 1 maxItems: 2 reg-names: + minItems: 1 items: - const: ldb - const: lvds
@@ -83,15 +85,6 @@ allOf: ports: properties: port@2: false - - if: - not: - properties: - compatible: - contains: - const: fsl,imx6sx-ldb - then: - required: - - reg-names - if: properties:
@@ -100,7 +93,19 @@ allOf: const: fsl,imx6sx-ldb then: properties: + reg: + maxItems: 1 + reg-names: + maxItems: 1 nxp,enable-termination-resistor: false + else: + required: + - reg-names + properties: + reg: + minItems: 2 + reg-names: + minItems: 2 additionalProperties: false
Signature · 1 line
2.43.0
PATCH v3 2/4 dt-bindings: soc: imx-iomuxc-gpr: allow bridge@18 as child node
In reply to [email protected]From: Frank Li <[email protected]>
The legacy i.MX6SX (>15 year) SoC imx-iomuxc-gpr contains one LDB_CTRL register. Allow the LVDS Display Bridge(LDB) child node under imx-iomuxc-gpr.
Fix below CHECK_DTBS warnings:
arch/arm/boot/dts/nxp/imx/imx6sx-nitrogen6sx.dtb: syscon@20e4000 (fsl,imx6sx-iomuxc-gpr): '#address-cells', '#size-cells', 'bridge@18' do not match any of the regexes: '^ipu[12]_csi[01]_mux$', '^pinctrl-[0-9]+$
---
change in v3
- add ranges
changes in v2
- remote status = "disabled" in example
--- .../bindings/soc/imx/fsl,imx-iomuxc-gpr.yaml | 62 ++++++++++++++++++++++ 1 file changed, 62 insertions(+)
Documentation/devicetree/bindings/soc/imx/fsl,imx-iomuxc-gpr.yaml +62 -0
@@ -47,10 +47,23 @@ properties: reg: maxItems: 1 + '#address-cells': + const: 1 + + '#size-cells': + const: 1 + + ranges: true + mux-controller: type: object $ref: /schemas/mux/reg-mux.yaml + bridge@18: + type: object + $ref: /schemas/display/bridge/fsl,ldb.yaml# + unevaluatedProperties: false + patternProperties: "^ipu[12]_csi[01]_mux$": type: object
@@ -67,6 +80,19 @@ allOf: patternProperties: '^ipu[12]_csi[01]_mux$': false + - if: + properties: + compatible: + not: + contains: + const: fsl,imx6sx-iomuxc-gpr + then: + properties: + bridge@18: false + '#address-cells': false + '#size-cells': false + ranges: false + additionalProperties: false required:
@@ -87,4 +113,40 @@ examples: }; }; + - | + #include <dt-bindings/clock/imx6sx-clock.h> + + syscon@20e4000 { + compatible = "fsl,imx6sx-iomuxc-gpr", "fsl,imx6q-iomuxc-gpr", "syscon", "simple-mfd"; + reg = <0x020e4000 0x4000>; + #address-cells = <1>; + #size-cells = <1>; + ranges; + + bridge@18 { + compatible = "fsl,imx6sx-ldb"; + reg = <0x18 0x4>; + clocks = <&clks IMX6SX_CLK_LDB_DI0>; + clock-names = "ldb"; + + ports { + #address-cells = <1>; + #size-cells = <0>; + + port@0 { + reg = <0>; + + endpoint { + }; + }; + + port@1 { + reg = <1>; + + endpoint { + }; + }; + }; + }; + }; ...
Signature · 1 line
2.43.0
Re: [PATCH v3 2/4] dt-bindings: soc: imx-iomuxc-gpr: allow bridge@18 as child node
Quoted 14 lines · On Thu, 23 Jul 2026 15:14:16 -0400, [email protected] wrote:
From: Frank Li <[email protected]>
The legacy i.MX6SX (>15 year) SoC imx-iomuxc-gpr contains one
LDB_CTRLregister. Allow the LVDS Display Bridge(LDB) child node under imx-iomuxc-gpr.Fix below
CHECK_DTBSwarnings:
arch/arm/boot/dts/nxp/imx/imx6sx-nitrogen6sx.dtb: syscon@20e4000 (fsl,imx6sx-iomuxc-gpr): '#address-cells', '#size-cells', 'bridge@18' do not match any of the regexes: '^ipu[12]_csi[01]_mux$', '^pinctrl-[0-9]+$Signed-off-by Frank Li <[email protected]>---
change in v3
- add ranges
Quoted 6 lines
changes in v2
- remote status = "disabled" in example--- .../bindings/soc/imx/fsl,imx-iomuxc-gpr.yaml | 62 ++++++++++++++++++++++ 1 file changed, 62 insertions(+)
PATCH v3 3/4 dt-bindings: display: lcdif: Allow display0 child node for i.MX6UL
In reply to [email protected]From: Frank Li <[email protected]>
The legacy i.MX6UL LCDIF binding uses a display0 child node to describe the attached display. Update the binding schema to allow this child node for fsl,imx6ul-lcdif.
Fixes the following CHECK_DTBS warning:
arch/arm/boot/dts/nxp/imx/imx6ul-tx6ul-0010.dtb: lcdif@21c8000 (fsl,imx6ul-lcdif): 'disp0' does not match any of the regexes: '^pinctrl-[0-9]+$'
A follow-up patch renames the child node from disp0 to display0 to match the updated binding.
---
sashiko report problem and allow dma/dma-names for i.MX6ul. which should be fine for this kinds of old platform.
Ideally it should use port. but platform is too old to avoid break back compatiblity and leave as it. Needn't complex if-else branch.
--- Documentation/devicetree/bindings/display/fsl,lcdif.yaml | 1 + 1 file changed, 1 insertion(+)
Documentation/devicetree/bindings/display/fsl,lcdif.yaml +1 -0
@@ -182,6 +182,7 @@ allOf: contains: enum: - fsl,imx28-lcdif + - fsl,imx6ul-lcdif then: properties: dmas: false
Signature · 1 line
2.43.0
PATCH v3 4/4 ARM: dts: imx6ul-tx6ul: rename disp0 to display0
In reply to [email protected]From: Frank Li <[email protected]>
Change node name disp0 to display0 to match binding define.
Fix the following CHECK_DTBS warning:
arch/arm/boot/dts/nxp/imx/imx6ul-tx6ul-0010.dtb: lcdif@21c8000 (fsl,imx6ul-lcdif): 'disp0' does not match any of the regexes: '^pinctrl-[0-9]+$'
--- arch/arm/boot/dts/nxp/imx/imx6ul-tx6ul.dtsi | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
arch/arm/boot/dts/nxp/imx/imx6ul-tx6ul.dtsi +1 -1
@@ -369,7 +369,7 @@ &lcdif { display = <&display>; status = "okay"; - display: disp0 { + display: display0 { bits-per-pixel = <32>; bus-width = <24>; status = "okay";
Signature · 1 line
2.43.0
[email protected]
AppliedFrom: Frank Li <[email protected]>
Quoted 1 line · On Thu, 23 Jul 2026 15:14:14 -0400, [email protected] wrote:
Fix ldb related
CHECK_DTBSwarnings
Applied to imx/dt-intend, thanks!
[1/4] dt-bindings: display: bridge: ldb: allow a single reg for fsl,imx6sx-ldb
commit: 26b2c52685c146b65f354b0623b0044626c35494
[2/4] dt-bindings: soc: imx-iomuxc-gpr: allow bridge@18 as child node
commit: 58627dbbd8e8ea7f4429b69b15b1c443681bf05a
[3/4] dt-bindings: display: lcdif: Allow display0 child node for i.MX6UL
commit: 17c5e5980b6fe3be98b21c046adf2aaa62006f0dI picked two imx display binding doc changes, if anyone have conern, let me know.
[4/4] ARM: dts: imx6ul-tx6ul: rename disp0 to display0
commit: 955326b06028ae72e1a46b23c2d3db749e9be47c
Best regards,
--
Frank Li <[email protected]>