Hi Archit, On Thu, Jul 21, 2016 at 03:23:18PM +0530, Archit Taneja wrote: > Hi, > > On 07/20/2016 03:28 PM, Maxime Ripard wrote: > >Some boards have an entirely passive RGB to VGA bridge, based on either > >DACs or resistor ladders. > > > >Those might or might not have an i2c bus routed to the VGA connector in > >order to access the screen EDIDs. > > > >Add a bridge that doesn't do anything but expose the modes available on the > >screen, either based on the EDIDs if available, or based on the XGA > >standards. > > Our eventual aim is to separate out the connectors from the bridge > drivers wherever possible. In the future, a KMS driver using the > bridge would be responsible for establishing the links between > the bridge and encoder, and the encoder and connector. > > If in the future we remove the connector pieces from this driver > to create a separate generic VGA connector driver, we'll end up > with a bridge driver whose main functionality is to convert RGB > signals to VGA. The EDID parts would move to the VGA connector > driver. In your platform's case, there is no software needed > to translate RGB to VGA, but maybe in the future, we might need > to add an optional regulator in the driver to support another > platform. Therefore, the bridge driver would still be handy to > have. > > Keeping this in consideration, I think this driver (and the DT > binding) should be called "dumb-rgb-to-vga-bridge", or > "rgb-to-vga-bridge" since that's what the bridge HW primarily > does. That works for me. I'll change it and repost. Thanks! Maxime -- Maxime Ripard, Free Electrons Embedded Linux and Kernel engineering http://free-electrons.com
Attachment:
signature.asc
Description: PGP signature
