From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Sebastian Reichel <sre@kernel.org>
Cc: Tomi Valkeinen <tomi.valkeinen@ti.com>,
Thierry Reding <thierry.reding@gmail.com>,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 0/6] omapdrm: drm_bridge and drm_panel support
Date: Mon, 11 Feb 2019 09:46:15 +0200 [thread overview]
Message-ID: <20190211074615.GA4526@pendragon.ideasonboard.com> (raw)
In-Reply-To: <20190209120514.3ozlkcd3cjab5s3x@earth.universe>
Hi Sebastian,
On Sat, Feb 09, 2019 at 01:05:14PM +0100, Sebastian Reichel wrote:
> On Fri, Jan 11, 2019 at 03:34:19AM +0200, Laurent Pinchart wrote:
> > On Thursday, 20 December 2018 14:17:27 EET Sebastian Reichel wrote:
> >> On Mon, Dec 10, 2018 at 03:06:17AM +0200, Laurent Pinchart wrote:
> >>> This patch series hooks up support for drm_bridge and drm_panel in the
> >>> omapdrm driver.
> >>>
> >>> [...]
> >>
> >> The series is
> >>
> >> Reviewed-by: Sebastian Reichel <sebastian.reichel@collabora.com>
> >>
> >> At the same time it is tested to break display on Droid 4. I don't
> >> know the exact reason yet. Debugging this is annoyingly hard, since
> >> the patches for manual display update still have not been merged
> >> making the testing process cumbersome.
> >
> > Is it this series that breaks display on Droid 4, or was it broken already ?
> > I've pushed all pending omapdrm patches to
> >
> > git://linuxtv.org/pinchartl/media.git omapdrm/bridge/next
> >
> > with the three fixes from Tomi at the bottom of the branch, and this series at
> > the top.
> >
> > I think the omapdrm/dss drivers are now in a shape that can let us consider
> > upstreaming DSI support. The real challenge will be to do so in a way
> > compatible with drm_bridge and drm_panel.
>
> The main issue was the removal of pipe->display in this patchset.
> I suggest to remove the entry to avoid accidental usage.
Very good point. New patch on its way.
--
Regards,
Laurent Pinchart
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2019-02-11 7:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-10 1:06 [PATCH 0/6] omapdrm: drm_bridge and drm_panel support Laurent Pinchart
2018-12-10 1:06 ` [PATCH 1/6] drm/panel: simple: Add OSD070T1718-19TS panel support Laurent Pinchart
2018-12-10 1:06 ` [PATCH 2/6] drm/omap: Add support for drm_bridge Laurent Pinchart
2018-12-10 1:06 ` [PATCH 3/6] drm/omap: Add support for drm_panel Laurent Pinchart
2018-12-10 1:06 ` [PATCH 4/6] drm/omap: Whitelist DT nodes to fixup with omapdss, prefix Laurent Pinchart
2018-12-10 1:06 ` [PATCH 5/6] drm/omap: Remove TFP410 and DVI connector drivers Laurent Pinchart
2018-12-10 1:06 ` [PATCH 6/6] drm/omap: Remove panel-dpi driver Laurent Pinchart
2018-12-20 12:17 ` [PATCH 0/6] omapdrm: drm_bridge and drm_panel support Sebastian Reichel
2018-12-20 12:49 ` Tomi Valkeinen
2019-01-11 1:34 ` Laurent Pinchart
2019-02-09 12:05 ` Sebastian Reichel
2019-02-11 7:46 ` Laurent Pinchart [this message]
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=20190211074615.GA4526@pendragon.ideasonboard.com \
--to=laurent.pinchart@ideasonboard.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=sre@kernel.org \
--cc=thierry.reding@gmail.com \
--cc=tomi.valkeinen@ti.com \
/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