Hi Krzysztof, On 2018-06-18 19:42, Krzysztof Kozlowski wrote: > The decon, decon_tv and dsi nodes have only one child port so > address/size mappings are not necessary. This fixes DTC warnings like: > > Warning (graph_child_address): /soc/decon@13800000/ports: > graph node has single child node 'port@0', #address-cells/#size-cells are not necessary > > Signed-off-by: Krzysztof Kozlowski <krzk@xxxxxxxxxx> Works fine with current Exynos DRM Decon/MIC/DSI drivers. Tested-by: Marek Szyprowski <m.szyprowski@xxxxxxxxxxx> > --- > arch/arm64/boot/dts/exynos/exynos5433-tm2-common.dtsi | 6 +----- > arch/arm64/boot/dts/exynos/exynos5433.dtsi | 12 ++---------- > 2 files changed, 3 insertions(+), 15 deletions(-) > > diff --git a/arch/arm64/boot/dts/exynos/exynos5433-tm2-common.dtsi b/arch/arm64/boot/dts/exynos/exynos5433-tm2-common.dtsi > index a1e3194b7483..0a15ee513f5c 100644 > --- a/arch/arm64/boot/dts/exynos/exynos5433-tm2-common.dtsi > +++ b/arch/arm64/boot/dts/exynos/exynos5433-tm2-common.dtsi > @@ -321,11 +321,7 @@ > status = "okay"; > > ports { > - #address-cells = <1>; > - #size-cells = <0>; > - > - port@0 { > - reg = <0>; > + port { > tv_to_hdmi: endpoint { > remote-endpoint = <&hdmi_to_tv>; > }; > diff --git a/arch/arm64/boot/dts/exynos/exynos5433.dtsi b/arch/arm64/boot/dts/exynos/exynos5433.dtsi > index 3a9b4c4b9c63..e4367fd39120 100644 > --- a/arch/arm64/boot/dts/exynos/exynos5433.dtsi > +++ b/arch/arm64/boot/dts/exynos/exynos5433.dtsi > @@ -850,11 +850,7 @@ > iommu-names = "m0", "m1"; > > ports { > - #address-cells = <1>; > - #size-cells = <0>; > - > - port@0 { > - reg = <0>; > + port { > decon_to_mic: endpoint { > remote-endpoint = > <&mic_to_decon>; > @@ -914,11 +910,7 @@ > #size-cells = <0>; > > ports { > - #address-cells = <1>; > - #size-cells = <0>; > - > - port@0 { > - reg = <0>; > + port { > dsi_to_mic: endpoint { > remote-endpoint = <&mic_to_dsi>; > }; Best regards -- Marek Szyprowski, PhD Samsung R&D Institute Poland -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html