[PATCH v3 06/14] Documentation: drm/bridge: add document for analogix_dp
Russell King - ARM Linux
linux at arm.linux.org.uk
Tue Aug 25 02:29:39 PDT 2015
On Tue, Aug 25, 2015 at 11:12:48AM +0200, Thierry Reding wrote:
> On Mon, Aug 24, 2015 at 09:48:27AM -0500, Rob Herring wrote:
> > It goes beyond bindings IMO. The use of the component framework or not
> > has been at the whim of driver writers as well. It is either used or
> > private APIs are created. I'm using components and my need for it
> > boils down to passing the struct drm_device pointer to the encoder.
> > Other components like panels and bridges have different ways to attach
> > to the DRM driver.
> I certainly support unification, but it needs to be reasonable. There
> are cases where a different structure for the binding work better than
> another and I think this always needs to be evaluated on a case by case
It can't be a case-by-case basis.
The TDA998x encoder/connector is going to be component only. This is
a generic chip, which can be attached to the output of any parallel
RGB+sync+clock bus. In other words, it could appear anywhere.
Are you really saying that we need to support multiple schemes of
attaching the driver to DRM? That's totally insane IMHO.
The problem with the drm_encoder_slave stuff is that you can't sanely
attach of-nodes to the drm-created i2c device. Yes, you can parse
them from the DT file as a sub-node of the upper device, but that
then goes against the principle of the I2C bindings, which is to
list the I2C devices as a child below the I2C adapter node. If you
try and put the DT node there, then the OF code will create the I2C
device for you, and the drm_encoder_slave stuff won't have the
control it needs to communicate through the wrapped i2c_driver
So, tda998x is going component-only, as that's the _only_ sane solution
Now, what happens when some other DRM driver wants to use the tda998x
driver, and its bindings are not compatible with the component helpers?
They're pretty much stuck up the creek without a paddle.
Case by case doesn't work unless you're talking about truely isolated
hardware where no one shares anything.
FTTC broadband for 0.8mile line: currently at 10.5Mbps down 400kbps up
according to speedtest.net.
More information about the dri-devel