From: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
To: "daniel.vetter@ffwll.ch" <daniel.vetter@ffwll.ch>
Cc: "daniel.vetter@intel.com" <daniel.vetter@intel.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH] drm/arcpgu: remove drm_encoder_slave
Date: Wed, 17 Jan 2018 13:55:55 +0000 [thread overview]
Message-ID: <1516197355.3547.36.camel@synopsys.com> (raw)
In-Reply-To: <20180117134347.27582-1-daniel.vetter@ffwll.ch>
Hi Daniel,
On Wed, 2018-01-17 at 14:43 +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.
>
> 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.
As of today we use either use adv7511 encoder or dw-hdmi.
And I guess proposed change is OK for both bridge versions, rigth?
-Alexey
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-01-17 14:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-17 13:43 [PATCH] drm/arcpgu: remove drm_encoder_slave Daniel Vetter
2018-01-17 13:53 ` Daniel Vetter
2018-01-17 14:02 ` Laurent Pinchart
2018-01-17 13:55 ` Alexey Brodkin [this message]
2018-01-17 14:03 ` Daniel Vetter
2018-01-17 14:17 ` Daniel Vetter
2018-01-30 9:15 ` Daniel Vetter
2018-01-30 16:44 ` Alexey Brodkin
2018-01-30 17:07 ` Daniel Vetter
2018-01-30 19:06 ` Alexey Brodkin
2018-01-20 1:59 ` kbuild test robot
2018-01-20 4:17 ` kbuild test robot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1516197355.3547.36.camel@synopsys.com \
--to=alexey.brodkin@synopsys.com \
--cc=daniel.vetter@ffwll.ch \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox