Hi Daniel,
On Tue, 2018-01-30 at 18:07 +0100, Daniel Vetter wrote:
On Tue, Jan 30, 2018 at 5:44 PM, Alexey Brodkin Alexey.Brodkin@synopsys.com wrote:
Hi Daniel,
On Tue, 2018-01-30 at 10:15 +0100, Daniel Vetter wrote:
On Wed, Jan 17, 2018 at 03:17:55PM +0100, Daniel Vetter wrote:
drm_encoder_slave is the old way to write bridge drivers, for i2c bridges only. It's deprecated, and definitely should not be used in new drivers. This has absolutely nothing to do with the new bridge driver infrastructure implemented by drm_bridge.
What's even strange is that arcpgu doesn't even use any of this, it really only wants a plain normal drm_encoder. Nuke all the surplus real estate.
v2: Actually git add after compile testing ...
v3: Clarify commit message and stop including drm_encoder_slave.h.
Cc: Laurent Pinchart laurent.pinchart@ideasonboard.com Cc: Alexey Brodkin abrodkin@synopsys.com Reviewed-by: Laurent Pinchart laurent.pinchart@ideasonboard.com Signed-off-by: Daniel Vetter daniel.vetter@intel.com
I assumed this is ok and applied it to drm-misc-next. -Daniel
Not sure but I still cannot see anything arcpgu-related here https://urldefense.proofpoint.com/v2/url?u=https-3A__cgit.freedesktop.org_dr... ViXO7breS55ytWkhpk5R81I&m=ZsFKo3w8gSf8Ul8_sl5RG8BACV1SwqgPV3wf6m4YtVM&s=f9P3-3L_o6CCd_1IQjGPNtAPAOtlO8rj2D2X8T5v_xw&e=
Am I looking at the wrong place?
Build test script got stuck, pushed for real now.
Thanks!
Gave it a try and it works perfectly fine. If it still makes any sense...
Acked-by: Alexey Brodkin abrodkin@synopsys.com