Hi Daniel,
On Thu, Jul 11, 2019 at 09:37:26AM +0200, Daniel Vetter wrote:
> On Sun, Jul 07, 2019 at 09:07:52PM +0300, Laurent Pinchart wrote:
> > Hello,
> >
> > This patch series (nearly, see [1]) completes the rework of the omapdrm
> > driver to move to drm_bridge and drm_panel.
> >
> > What a
Hi Sebastian,
On Thu, Jul 11, 2019 at 01:59:23PM +0200, Sebastian Reichel wrote:
> On Thu, Jul 11, 2019 at 09:37:26AM +0200, Daniel Vetter wrote:
> > > [1] The only notable exception is the omapdrm-specific DSI panel driver
> > > that implements a large number of custom operations. This should be
Hi,
On Thu, Jul 11, 2019 at 09:37:26AM +0200, Daniel Vetter wrote:
> > [1] The only notable exception is the omapdrm-specific DSI panel driver
> > that implements a large number of custom operations. This should be
> > addressed separately.
>
> DSI tends to be fairly custom in all drivers, I thin
On Sun, Jul 07, 2019 at 09:07:52PM +0300, Laurent Pinchart wrote:
> Hello,
>
> This patch series (nearly, see [1]) completes the rework of the omapdrm
> driver to move to drm_bridge and drm_panel.
>
> What a journey. This work was started more than a year ago, and this
> last piece is perhaps the
Hello,
This patch series (nearly, see [1]) completes the rework of the omapdrm
driver to move to drm_bridge and drm_panel.
What a journey. This work was started more than a year ago, and this
last piece is perhaps the one that will generate the most bikeshedding
as it touches the DRM core. I'm br
