| Message ID | 20200224232126.3385250-3-sebastian.reichel@collabora.com (mailing list archive) |
|---|---|
| State | New, archived |
| Headers | show |
| Series | drm/omap: Convert DSI code to use drm_mipi_dsi and drm_panel | expand |
Hi Sebastian, Thank you for the patch. On Tue, Feb 25, 2020 at 12:20:32AM +0100, Sebastian Reichel wrote: > Add Droid 4 specific compatible value in addition to the > generic one, so that we have the ability to add panel > specific quirks in the future. We need to document this compatible string in DT bindings, I don't think this is included in this series. Furthermore, could we use a compatible string that actually matches the panel vendor and model, instead of the device name ? > Signed-off-by: Sebastian Reichel <sebastian.reichel@collabora.com> > --- > arch/arm/boot/dts/motorola-mapphone-common.dtsi | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/arch/arm/boot/dts/motorola-mapphone-common.dtsi b/arch/arm/boot/dts/motorola-mapphone-common.dtsi > index a5e4ba7c8dab..622383ec6a75 100644 > --- a/arch/arm/boot/dts/motorola-mapphone-common.dtsi > +++ b/arch/arm/boot/dts/motorola-mapphone-common.dtsi > @@ -200,7 +200,7 @@ dsi1_out_ep: endpoint { > }; > > lcd0: panel@0 { > - compatible = "panel-dsi-cm"; > + compatible = "motorola,droid4-panel", "panel-dsi-cm"; > reg = <0>; > label = "lcd0"; > vddi-supply = <&lcd_regulator>;
* Laurent Pinchart <laurent.pinchart@ideasonboard.com> [200224 23:38]: > Hi Sebastian, > > Thank you for the patch. > > On Tue, Feb 25, 2020 at 12:20:32AM +0100, Sebastian Reichel wrote: > > Add Droid 4 specific compatible value in addition to the > > generic one, so that we have the ability to add panel > > specific quirks in the future. > > We need to document this compatible string in DT bindings, I don't think > this is included in this series. Furthermore, could we use a compatible > string that actually matches the panel vendor and model, instead of the > device name ? To me it seems there are multiple similar panels from various vendors in use for xt875/xt894/xt910/xt912 phones, I'm not sure if anybody has this list? Regards, Tony
Hi Laurent, On Tue, Feb 25, 2020 at 01:37:08AM +0200, Laurent Pinchart wrote: > Hi Sebastian, > > Thank you for the patch. Thanks for the review. > On Tue, Feb 25, 2020 at 12:20:32AM +0100, Sebastian Reichel wrote: > > Add Droid 4 specific compatible value in addition to the > > generic one, so that we have the ability to add panel > > specific quirks in the future. > > We need to document this compatible string in DT bindings, I don't think > this is included in this series. Correct, right now none of the extra compatible strings are documented in the binding file. E.g. "tpo,taal" is used by omap4-sdp and in the example section of the DT bindings. > Furthermore, could we use a compatible string that actually > matches the panel vendor and model, instead of the device name ? We don't know the Droid 4 panel vendor and/or model. For N950 "nokia,himalaya" is used, which is obviously also not the real vendor. But for N950 there is a good reason to use a N950 specific compatible anyways, since some pixels are covered by plastic. Maybe this can just be handled when the bindings file is converted to YAML? -- Sebastian > > > Signed-off-by: Sebastian Reichel <sebastian.reichel@collabora.com> > > --- > > arch/arm/boot/dts/motorola-mapphone-common.dtsi | 2 +- > > 1 file changed, 1 insertion(+), 1 deletion(-) > > > > diff --git a/arch/arm/boot/dts/motorola-mapphone-common.dtsi b/arch/arm/boot/dts/motorola-mapphone-common.dtsi > > index a5e4ba7c8dab..622383ec6a75 100644 > > --- a/arch/arm/boot/dts/motorola-mapphone-common.dtsi > > +++ b/arch/arm/boot/dts/motorola-mapphone-common.dtsi > > @@ -200,7 +200,7 @@ dsi1_out_ep: endpoint { > > }; > > > > lcd0: panel@0 { > > - compatible = "panel-dsi-cm"; > > + compatible = "motorola,droid4-panel", "panel-dsi-cm"; > > reg = <0>; > > label = "lcd0"; > > vddi-supply = <&lcd_regulator>; > > -- > Regards, > > Laurent Pinchart
On Tue, Feb 25, 2020 at 12:20:32AM +0100, Sebastian Reichel wrote: > Add Droid 4 specific compatible value in addition to the > generic one, so that we have the ability to add panel > specific quirks in the future. > Yes, exactly as explained in previous mail. Thanks. > Signed-off-by: Sebastian Reichel <sebastian.reichel@collabora.com> Acked-by: Sam Ravnborg <sam@ravnborg.org> > --- > arch/arm/boot/dts/motorola-mapphone-common.dtsi | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/arch/arm/boot/dts/motorola-mapphone-common.dtsi b/arch/arm/boot/dts/motorola-mapphone-common.dtsi > index a5e4ba7c8dab..622383ec6a75 100644 > --- a/arch/arm/boot/dts/motorola-mapphone-common.dtsi > +++ b/arch/arm/boot/dts/motorola-mapphone-common.dtsi > @@ -200,7 +200,7 @@ dsi1_out_ep: endpoint { > }; > > lcd0: panel@0 { > - compatible = "panel-dsi-cm"; > + compatible = "motorola,droid4-panel", "panel-dsi-cm"; > reg = <0>; > label = "lcd0"; > vddi-supply = <&lcd_regulator>; > -- > 2.25.0 > > _______________________________________________ > dri-devel mailing list > dri-devel@lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/dri-devel
Hi Tony, On Mon, Feb 24, 2020 at 03:47:59PM -0800, Tony Lindgren wrote: > * Laurent Pinchart <laurent.pinchart@ideasonboard.com> [200224 23:38]: > > On Tue, Feb 25, 2020 at 12:20:32AM +0100, Sebastian Reichel wrote: > > > Add Droid 4 specific compatible value in addition to the > > > generic one, so that we have the ability to add panel > > > specific quirks in the future. > > > > We need to document this compatible string in DT bindings, I don't think > > this is included in this series. Furthermore, could we use a compatible > > string that actually matches the panel vendor and model, instead of the > > device name ? > > To me it seems there are multiple similar panels from various > vendors in use for xt875/xt894/xt910/xt912 phones, I'm not sure > if anybody has this list? Are they all truly compatible ?
* Laurent Pinchart <laurent.pinchart@ideasonboard.com> [200227 22:12]: > Hi Tony, > > On Mon, Feb 24, 2020 at 03:47:59PM -0800, Tony Lindgren wrote: > > * Laurent Pinchart <laurent.pinchart@ideasonboard.com> [200224 23:38]: > > > On Tue, Feb 25, 2020 at 12:20:32AM +0100, Sebastian Reichel wrote: > > > > Add Droid 4 specific compatible value in addition to the > > > > generic one, so that we have the ability to add panel > > > > specific quirks in the future. > > > > > > We need to document this compatible string in DT bindings, I don't think > > > this is included in this series. Furthermore, could we use a compatible > > > string that actually matches the panel vendor and model, instead of the > > > device name ? > > > > To me it seems there are multiple similar panels from various > > vendors in use for xt875/xt894/xt910/xt912 phones, I'm not sure > > if anybody has this list? > > Are they all truly compatible ? Well that is still unknown. We know that x894 panel config works with xt875 at least. The panels are different looking the original dtb files. Best to use device specific compatibles like Sebastian is doing. If we ever get some real manufacturer and model data, we can add that. Regards, Tony
diff --git a/arch/arm/boot/dts/motorola-mapphone-common.dtsi b/arch/arm/boot/dts/motorola-mapphone-common.dtsi index a5e4ba7c8dab..622383ec6a75 100644 --- a/arch/arm/boot/dts/motorola-mapphone-common.dtsi +++ b/arch/arm/boot/dts/motorola-mapphone-common.dtsi @@ -200,7 +200,7 @@ dsi1_out_ep: endpoint { }; lcd0: panel@0 { - compatible = "panel-dsi-cm"; + compatible = "motorola,droid4-panel", "panel-dsi-cm"; reg = <0>; label = "lcd0"; vddi-supply = <&lcd_regulator>;
Add Droid 4 specific compatible value in addition to the generic one, so that we have the ability to add panel specific quirks in the future. Signed-off-by: Sebastian Reichel <sebastian.reichel@collabora.com> --- arch/arm/boot/dts/motorola-mapphone-common.dtsi | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)