| Message ID | 20220325171511.23493-2-granquet@baylibre.com |
|---|---|
| State | Superseded |
| Headers | show |
| Series | drm/mediatek: Add mt8195 DisplayPort driver | expand |
On 25/03/2022 18:14, Guillaume Ranquet wrote: > From: Markus Schneider-Pargmann <msp@baylibre.com> > > DP_INTF is similar to DPI but does not have the exact same feature set > or register layouts. > > DP_INTF is the sink of the display pipeline that is connected to the > DisplayPort controller and encoder unit. It takes the same clocks as > DPI. > > Signed-off-by: Markus Schneider-Pargmann <msp@baylibre.com> > Signed-off-by: Guillaume Ranquet <granquet@baylibre.com> > Reviewed-by: Rob Herring <robh@kernel.org> This is v1, how did you get Rob's review already? > --- > .../bindings/display/mediatek/mediatek,dpi.yaml | 11 ++++++----- > 1 file changed, 6 insertions(+), 5 deletions(-) > > diff --git a/Documentation/devicetree/bindings/display/mediatek/mediatek,dpi.yaml b/Documentation/devicetree/bindings/display/mediatek/mediatek,dpi.yaml > index dd2896a40ff0..53acf9a84f7f 100644 > --- a/Documentation/devicetree/bindings/display/mediatek/mediatek,dpi.yaml > +++ b/Documentation/devicetree/bindings/display/mediatek/mediatek,dpi.yaml > @@ -4,16 +4,16 @@ > $id: http://devicetree.org/schemas/display/mediatek/mediatek,dpi.yaml# > $schema: http://devicetree.org/meta-schemas/core.yaml# > > -title: mediatek DPI Controller Device Tree Bindings > +title: mediatek DPI/DP_INTF Controller Device Tree Bindings While at it, remove "Device Tree Bindings". It's about hardware. Please also rebase your tree as you use my old email address. Best regards, Krzysztof
On Fri, 25 Mar 2022 18:31, Krzysztof Kozlowski <krzk@kernel.org> wrote: >On 25/03/2022 18:14, Guillaume Ranquet wrote: >> From: Markus Schneider-Pargmann <msp@baylibre.com> >> >> DP_INTF is similar to DPI but does not have the exact same feature set >> or register layouts. >> >> DP_INTF is the sink of the display pipeline that is connected to the >> DisplayPort controller and encoder unit. It takes the same clocks as >> DPI. >> >> Signed-off-by: Markus Schneider-Pargmann <msp@baylibre.com> >> Signed-off-by: Guillaume Ranquet <granquet@baylibre.com> >> Reviewed-by: Rob Herring <robh@kernel.org> > >This is v1, how did you get Rob's review already? > Because this is not v1... I'm not really good at this... this is actually v9... I just didn't pay attention enough before sending the series. What's the standard thing to do? resend with the proper versionning? Sorry for the confusion, Guillaume. >> --- >> .../bindings/display/mediatek/mediatek,dpi.yaml | 11 ++++++----- >> 1 file changed, 6 insertions(+), 5 deletions(-) >> >> diff --git a/Documentation/devicetree/bindings/display/mediatek/mediatek,dpi.yaml b/Documentation/devicetree/bindings/display/mediatek/mediatek,dpi.yaml >> index dd2896a40ff0..53acf9a84f7f 100644 >> --- a/Documentation/devicetree/bindings/display/mediatek/mediatek,dpi.yaml >> +++ b/Documentation/devicetree/bindings/display/mediatek/mediatek,dpi.yaml >> @@ -4,16 +4,16 @@ >> $id: http://devicetree.org/schemas/display/mediatek/mediatek,dpi.yaml# >> $schema: http://devicetree.org/meta-schemas/core.yaml# >> >> -title: mediatek DPI Controller Device Tree Bindings >> +title: mediatek DPI/DP_INTF Controller Device Tree Bindings > >While at it, remove "Device Tree Bindings". It's about hardware. > > >Please also rebase your tree as you use my old email address. > >Best regards, >Krzysztof
On 25/03/2022 18:43, Guillaume Ranquet wrote: > On Fri, 25 Mar 2022 18:31, Krzysztof Kozlowski <krzk@kernel.org> wrote: >> On 25/03/2022 18:14, Guillaume Ranquet wrote: >>> From: Markus Schneider-Pargmann <msp@baylibre.com> >>> >>> DP_INTF is similar to DPI but does not have the exact same feature set >>> or register layouts. >>> >>> DP_INTF is the sink of the display pipeline that is connected to the >>> DisplayPort controller and encoder unit. It takes the same clocks as >>> DPI. >>> >>> Signed-off-by: Markus Schneider-Pargmann <msp@baylibre.com> >>> Signed-off-by: Guillaume Ranquet <granquet@baylibre.com> >>> Reviewed-by: Rob Herring <robh@kernel.org> >> >> This is v1, how did you get Rob's review already? >> > > Because this is not v1... I'm not really good at this... Don't worry, I made many more mistakes... > this is actually v9... > I just didn't pay attention enough before sending the series. > > What's the standard thing to do? resend with the proper versionning? Yes, please resend as v1 with cover-letter containing changelog. Anyway someone might scream that you spam his box (immediate resends are also not welcomed), but what to do. :) Best regards, Krzysztof
diff --git a/Documentation/devicetree/bindings/display/mediatek/mediatek,dpi.yaml b/Documentation/devicetree/bindings/display/mediatek/mediatek,dpi.yaml index dd2896a40ff0..53acf9a84f7f 100644 --- a/Documentation/devicetree/bindings/display/mediatek/mediatek,dpi.yaml +++ b/Documentation/devicetree/bindings/display/mediatek/mediatek,dpi.yaml @@ -4,16 +4,16 @@ $id: http://devicetree.org/schemas/display/mediatek/mediatek,dpi.yaml# $schema: http://devicetree.org/meta-schemas/core.yaml# -title: mediatek DPI Controller Device Tree Bindings +title: mediatek DPI/DP_INTF Controller Device Tree Bindings maintainers: - CK Hu <ck.hu@mediatek.com> - Jitao shi <jitao.shi@mediatek.com> description: | - The Mediatek DPI function block is a sink of the display subsystem and - provides 8-bit RGB/YUV444 or 8/10/10-bit YUV422 pixel data on a parallel - output bus. + The Mediatek DPI and DP_INTF function blocks are a sink of the display + subsystem and provides 8-bit RGB/YUV444 or 8/10/10-bit YUV422 pixel data on a + parallel output bus. properties: compatible: @@ -23,6 +23,7 @@ properties: - mediatek,mt8173-dpi - mediatek,mt8183-dpi - mediatek,mt8192-dpi + - mediatek,mt8195-dpintf reg: maxItems: 1 @@ -54,7 +55,7 @@ properties: $ref: /schemas/graph.yaml#/properties/port description: Output port node. This port should be connected to the input port of an - attached HDMI or LVDS encoder chip. + attached HDMI, LVDS or DisplayPort encoder chip. required: - compatible