On 7/28/26 7:29 AM, Julien Stephan wrote: > The mt8188 SoC provides an HDMI encoder and PHY fed through the DPI1 > interface attached to the vdosys1 display data path. > > Compared to the kernel, the following U-Boot specific properties are > added to the hdmi node: > - a "memory-region" phandle to the framebuffer reserved-memory region > - phandles to all the components of the pipeline, since U-Boot has no > DRM framework to walk the graph > > Signed-off-by: Julien Stephan <[email protected]> > --- > arch/arm/dts/mt8188-u-boot.dtsi | 21 +++++++++++++++++++++ > 1 file changed, 21 insertions(+) > > diff --git a/arch/arm/dts/mt8188-u-boot.dtsi b/arch/arm/dts/mt8188-u-boot.dtsi > index 923e52522de..26a2bddd24e 100644 > --- a/arch/arm/dts/mt8188-u-boot.dtsi > +++ b/arch/arm/dts/mt8188-u-boot.dtsi > @@ -79,3 +79,24 @@ > &mmc0 { > bootph-pre-ram; > }; > + > +&hdmi { > + /* U-Boot specific: the framebuffer lives in this reserved region */ > + memory-region = <&framebuffer>;
As in the previous patch, this could be in mt8390-genio-common.dtsi. > + > + /* > + * U-Boot specific: U-Boot has no DRM framework, so the video > + * driver locates the components of the display pipeline directly > + * through these phandles. > + */ > + mediatek,dpi1 = <&dpi1>; > + mediatek,vdosys1 = <&vdosys1_pipeline>; > + mediatek,merge3 = <&merge3>; > + mediatek,merge5 = <&merge5>; > + mediatek,mixer = <ðdr0>; > + mediatek,mutex1 = <&mutex1>; > + mediatek,padding4 = <&padding4>; > + mediatek,padding5 = <&padding5>; > + mediatek,rdma4 = <&vdo1_rdma4>; > + mediatek,rdma5 = <&vdo1_rdma5>; I see that the upstream device tree has aliases for a lot of these phandles. In the U-Boot driver, could we look up by alias instead of adding these properties? > +}; >
