On Mon, Feb 4, 2019 at 2:26 PM Vasily Khoruzhick <[email protected]> wrote: > > On Mon, Feb 4, 2019 at 12:23 PM Rob Herring <[email protected]> wrote: > > > > simple-panel would probably work if you stuck in some mostly compatible > > > string and provided a ddc-i2c-bus property in the device tree node. The > > > generic-ish fallback case could be implemented by providing a fallback > > > compatible string (we used to have "simple-panel", which I think would > > > still be adequate for this I suppose) and adding a dummy descriptor in > > > the driver, perhaps one with pre-defined delays that could be adjusted > > > to work for all cases, or they could just be 0. At least that way we'd > > > be explicitly documenting that we support this as a fallback. > > > > I'd like something more specific than 'simple-panel' that at least > > implies it has EDID and whatever else we think it should imply. > > > > Looking into this a bit more, why don't we just do a connector here? > > eDP has a standard connector (with power). It's just like other > > connectors, but with power and no hotplug. If someone does their own > > interface, then they should do their own connector or panel binding. > > Where do we put backlight in this case?
In the connector node. You'd need a backlight supply, 'backlight-enable-gpios' and backlight phandle to pwm-backlight node. Rob -- You received this message because you are subscribed to the Google Groups "linux-sunxi" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
