@@ -0,0 +1,26 @@+Generic MIPI DSI Command Mode Panel+=================> ++Required properties:+- compatible: "panel-dsi-cm"++Optional properties:+- label: a symbolic name for the panel+- gpios: panel reset gpio and TE gpio++Required nodes:+- Video port for DSI input++Example+-------++lcd0: display {+ compatible = "tpo,taal", "panel-dsi-cm";+ label = "lcd0";++ gpios = <&gpio4 6 GPIO_ACTIVE_HIGH>; /* 102, reset */
If the panel uses a TE GPIO but no reset GPIO, do you plan to express this
with a "hole" for the reset GPIO ? e.g. something like
gpios = <0>, <&gpio4 6 GPIO_ACTIVE_HIGH>;
Wouldn't it be better to split the gpios property into "reset-gpios" and "te-
gpios" ?
If the panel uses a TE GPIO but no reset GPIO, do you plan to express this
with a "hole" for the reset GPIO ? e.g. something like
gpios = <0>, <&gpio4 6 GPIO_ACTIVE_HIGH>;
Yes.
Wouldn't it be better to split the gpios property into "reset-gpios" and "te-
gpios" ?
Yes, I can change it. I don't have a strong preference.
I've gotten similar comments for other bindings also, so I guess the
preferred way is to use named "-gpios" properties for everything except
the case where you really have multiple gpios with the same purpose?
The gpio binding documentation doesn't give much guidance on this.
Tomi
If the panel uses a TE GPIO but no reset GPIO, do you plan to express this
with a "hole" for the reset GPIO ? e.g. something like
gpios = <0>, <&gpio4 6 GPIO_ACTIVE_HIGH>;
Yes.
quoted
Wouldn't it be better to split the gpios property into "reset-gpios" and
"te- gpios" ?
Yes, I can change it. I don't have a strong preference.
I've gotten similar comments for other bindings also, so I guess the
preferred way is to use named "-gpios" properties for everything except
the case where you really have multiple gpios with the same purpose?
That's my understanding, yes.
The gpio binding documentation doesn't give much guidance on this.