Hi Hoegeun, On 14.04.2017 07:19, Hoegeun Kwon wrote: > The Samsung s6e3ha2 edge is a 5.65" 1600x2560 AMOLED panel connected > using MIPI-DSI interfaces. As I wrote in discussion about s6e3ha2, there is no edge version of s6e3ha2, it is just different panel: s6e3hf2, or more precisely IC driver. [1]: https://lkml.org/lkml/2017/1/9/159 > > Signed-off-by: Hoegeun Kwon <hoegeun.kwon@xxxxxxxxxxx> > --- > .../bindings/display/panel/samsung,s6e3ha2-e.txt | 28 ++++++++++++++++++++++ > 1 file changed, 28 insertions(+) > create mode 100644 Documentation/devicetree/bindings/display/panel/samsung,s6e3ha2-e.txt > > diff --git a/Documentation/devicetree/bindings/display/panel/samsung,s6e3ha2-e.txt b/Documentation/devicetree/bindings/display/panel/samsung,s6e3ha2-e.txt > new file mode 100644 > index 0000000..09c65f6 > --- /dev/null > +++ b/Documentation/devicetree/bindings/display/panel/samsung,s6e3ha2-e.txt > @@ -0,0 +1,28 @@ > +Samsung S6E3HA2 5.65" 1600x2560 AMOLED panel > + > +Required properties: > + - compatible: "samsung,s6e3ha2-e" I think "samsung,s6e3hf2" should be then used, I guess it could be even simpler to just add new compatible string to samsung,s6e3ha2.txt binding with some comments, as these panels are of the same family. Regards Andrzej > + - reg: the virtual channel number of a DSI peripheral > + - vdd3-supply: I/O voltage supply > + - vci-supply: voltage supply for analog circuits > + - reset-gpios: a GPIO spec for the reset pin (active low) > + - enable-gpios: a GPIO spec for the panel enable pin (active high) > + > +Optional properties: > + - te-gpios: a GPIO spec for the tearing effect synchronization signal > + gpio pin (active high) > + > +Example: > +&dsi { > + ... > + > + panel@0 { > + compatible = "samsung,s6e3ha2-e"; > + reg = <0>; > + vdd3-supply = <&ldo27_reg>; > + vci-supply = <&ldo28_reg>; > + reset-gpios = <&gpg0 0 GPIO_ACTIVE_LOW>; > + enable-gpios = <&gpf1 5 GPIO_ACTIVE_HIGH>; > + te-gpios = <&gpf1 3 GPIO_ACTIVE_HIGH>; > + }; > +}; -- 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
