<html><body><p>
<pre>
Hi, Angelo:
On Wed, 2024-06-05 at 13:15 +0200, AngeloGioacchino Del Regno wrote:
> Il 05/06/24 03:38, CK Hu (胡俊光) ha scritto:
> > Hi, Angelo:
> >
> > On Tue, 2024-05-21 at 09:57 +0200, AngeloGioacchino Del Regno wrote:
> > > Document OF graph on MMSYS/VDOSYS: this supports up to three DDP paths
> > > per HW instance (so potentially up to six displays for multi-vdo SoCs).
> > >
> > > The MMSYS or VDOSYS is always the first component in the DDP pipeline,
> > > so it only supports an output port with multiple endpoints - where each
> > > endpoint defines the starting point for one of the (currently three)
> > > possible hardware paths.
> > >
> > > Reviewed-by: Rob Herring (Arm) <robh@kernel.org>
> > > Reviewed-by: Alexandre Mergnat <amergnat@baylibre.com>
> > > Tested-by: Alexandre Mergnat <amergnat@baylibre.com>
> > > Signed-off-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
> > > ---
> > > .../bindings/arm/mediatek/mediatek,mmsys.yaml | 28 +++++++++++++++++++
> > > 1 file changed, 28 insertions(+)
> > >
> > > diff --git a/Documentation/devicetree/bindings/arm/mediatek/mediatek,mmsys.yaml b/Documentation/devicetree/bindings/arm/mediatek/mediatek,mmsys.yaml
> > > index b3c6888c1457..0ef67ca4122b 100644
> > > --- a/Documentation/devicetree/bindings/arm/mediatek/mediatek,mmsys.yaml
> > > +++ b/Documentation/devicetree/bindings/arm/mediatek/mediatek,mmsys.yaml
> > > @@ -93,6 +93,34 @@ properties:
> > > '#reset-cells':
> > > const: 1
> > >
> > > + port:
> > > + $ref: /schemas/graph.yaml#/properties/port
> > > + description:
> > > + Output port node. This port connects the MMSYS/VDOSYS output to
> > > + the first component of one display pipeline, for example one of
> > > + the available OVL or RDMA blocks.
> > > + Some MediaTek SoCs support multiple display outputs per MMSYS.
> >
> > This patch looks good to me. Just want to share another information for you.
> > Here is an example that mmsys/vdosys could point to the display interface node.
> >
> > vdosys0: syscon@1c01a000 {
> > mmsys-display-interface = <&dsi0>, <&dsi1>, <&dp_intf0>;
> > };
> >
> > vdosys1: syscon@1c100000 {
> > mmsys-display-interface = <&dp_intf1>;
> > };
> >
> > There is no conflict that mmsys/vdosys point to first component of one display pipeline or point to display interface.
> > Both could co-exist.
> >
>
> Hey CK,
>
> yes, this could be an alternative to the OF graphs, and I'm sure that it'd work,
> even though this kind of solution would still require partial hardcoding of the
> display paths up until mmsys-display-interface (so, up until DSI0, or DSI1, etc).
>
> The problem with a solution like this is that, well, even though it would work,
> even if we ignore the suboptimal partial hardcoding, OF graphs are something
> generic, while the mmsys-display-interface would be a MediaTek specific/custom
> property.
>
> In the end, reusing generic kernel apis/interfaces/etc is always preferred
> compared to custom solutions, especially in this case, in which the generic
> stuff is on-par (or actually, depending purely on personal opinions, superior).
>
> As for the two to co-exist, I'm not sure that this is actually needed, as the
> OF graphs are already (at the end of the graph) pointing to the display interface.
>
> In any case, just as a reminder: if there will be any need to add any custom
> MediaTek specific properties later, it's ok and we can do that at any time.
The alternative solution is using OF graphs to point display interface and use MediaTek specific property to first component:
vdosys0: syscon@1c01a000 {
ports {
port@0 {
endpoint {
remote-endpoint = <&dsi0_endpoint>;
};
};
port@1 {
endpoint {
remote-endpoint = <&dsi1_endpoint>;
};
};
port@2 {
endpoint {
remote-endpoint = <&dp_intf0_endpoint>;
};
};
};
display-first-component = <&ovl0>;
};
And I agree to it's better to keep only OF graphs property, so it would be
vdosys0: syscon@1c01a000 {
ports {
port@0 {
endpoint {
remote-endpoint = <&dsi0_endpoint>;
};
};
port@1 {
endpoint {
remote-endpoint = <&dsi1_endpoint>;
};
};
port@2 {
endpoint {
remote-endpoint = <&dp_intf0_endpoint>;
}
;
};
};
};
Maybe we could use OF graphs for both first component and display interface and drop using MediaTek specific property.
Regards,
CK
>
> Cheers!
> Angelo
>
> > Regards,
> > CK
> >
> > > + properties:
> > > + endpoint@0:
> > > + $ref: /schemas/graph.yaml#/properties/endpoint
> > > + description: Output to the primary display pipeline
> > > +
> > > + endpoint@1:
> > > + $ref: /schemas/graph.yaml#/properties/endpoint
> > > + description: Output to the secondary display pipeline
> > > +
> > > + endpoint@2:
> > > + $ref: /schemas/graph.yaml#/properties/endpoint
> > > + description: Output to the tertiary display pipeline
> > > +
> > > + anyOf:
> > > + - required:
> > > + - endpoint@0
> > > + - required:
> > > + - endpoint@1
> > > + - required:
> > > + - endpoint@2
> > > +
> > > required:
> > > - compatible
> > > - reg
>
>
</pre>
</p></body></html><!--type:text--><!--{--><pre>************* MEDIATEK Confidentiality Notice ********************
The information contained in this e-mail message (including any
attachments) may be confidential, proprietary, privileged, or otherwise
exempt from disclosure under applicable laws. It is intended to be
conveyed only to the designated recipient(s). Any use, dissemination,
distribution, printing, retaining or copying of this e-mail (including its
attachments) by unintended recipient(s) is strictly prohibited and may
be unlawful. If you are not an intended recipient of this e-mail, or believe
that you have received this e-mail in error, please notify the sender
immediately (by replying to this e-mail), delete any and all copies of
this e-mail (including any attachments) from your system, and do not
disclose the content of this e-mail to any other person. Thank you!
</pre><!--}-->