On Wed, Apr 15, 2020 at 12:53:02PM -0700, Stephen Boyd wrote: > Quoting Douglas Anderson (2020-04-15 08:48:40) > > Allow people to specify to use a GPIO for hot-plug-detect. Add an > > example. > > > > NOTE: The current patch adding support for hpd-gpios to the Linux > > driver for hpd-gpios only adds enough support to the driver so that > > the bridge can use one of its own GPIOs. The bindings, however, are > > written generically. > > > > Signed-off-by: Douglas Anderson <dianders@xxxxxxxxxxxx> > > --- > > > > .../bindings/display/bridge/ti,sn65dsi86.yaml | 10 +++++++++- > > 1 file changed, 9 insertions(+), 1 deletion(-) > > > > diff --git a/Documentation/devicetree/bindings/display/bridge/ti,sn65dsi86.yaml b/Documentation/devicetree/bindings/display/bridge/ti,sn65dsi86.yaml > > index 8cacc6db33a9..554bfd003000 100644 > > --- a/Documentation/devicetree/bindings/display/bridge/ti,sn65dsi86.yaml > > +++ b/Documentation/devicetree/bindings/display/bridge/ti,sn65dsi86.yaml > > @@ -60,6 +60,10 @@ properties: > > const: 1 > > description: See ../../pwm/pwm.yaml for description of the cell formats. > > > > + hpd-gpios: > > + maxItems: 1 > > + description: If present use the given GPIO for hot-plug-detect. > > Shouldn't this go in the panel node? And the panel driver should get the > gpio and poll it after powering up the panel? Presumably that's why we > have the no-hpd property in the simple panel binding vs. putting it here > in the bridge. Same question really, I think this belongs to the panel (or connector) node indeed. -- Regards, Laurent Pinchart
