From: Sam Ravnborg <sam@ravnborg.org>
To: Tomi Valkeinen <tomi.valkeinen@ti.com>
Cc: Thierry Reding <thierry.reding@gmail.com>,
devicetree@vger.kernel.org, Tony Lindgren <tony@atomide.com>,
dri-devel@lists.freedesktop.org, Jyri Sarha <jsarha@ti.com>,
Peter Ujfalusi <peter.ujfalusi@ti.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Subject: Re: [PATCH 3/3] drm/panel: simple: fix osd070t1718_19ts sync drive edge
Date: Sat, 22 Feb 2020 13:16:06 +0100 [thread overview]
Message-ID: <20200222121606.GB28287@ravnborg.org> (raw)
In-Reply-To: <b36c42ea-3162-7462-7a51-c7b63620404f@ti.com>
Hi Tomi.
> >>>> +++ b/drivers/gpu/drm/panel/panel-simple.c
> >>>> @@ -2397,7 +2397,8 @@ static const struct panel_desc osddisplays_osd070t1718_19ts = {
> >>>> .height = 91,
> >>>> },
> >>>> .bus_format = MEDIA_BUS_FMT_RGB888_1X24,
> >>>> - .bus_flags = DRM_BUS_FLAG_DE_HIGH | DRM_BUS_FLAG_PIXDATA_DRIVE_POSEDGE,
> >>>> + .bus_flags = DRM_BUS_FLAG_DE_HIGH | DRM_BUS_FLAG_PIXDATA_DRIVE_POSEDGE |
> >>>> + DRM_BUS_FLAG_SYNC_DRIVE_POSEDGE,
> >>>> .connector_type = DRM_MODE_CONNECTOR_DPI,
> >>>> };
> >>
> >> Can this be merged?
> >
> > I have lost the original mail.
> > Can you re-send or provide a patchwork pointer or similar.
> > Then I will apply.
>
> Here are lore and patchwork links. Note that the first two patches in the series have already been handled.
>
> https://lore.kernel.org/dri-devel/20191114093950.rT5m86Xh0-a9FZGq7JipQ3O3vldctJYcvRdhxUMGBVE@z/#t
>
> https://patchwork.freedesktop.org/series/69459/
Thanks for the pointers. It is now applied to drm-misc-next.
Sam
next prev parent reply other threads:[~2020-02-22 12:16 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-14 9:39 [PATCH 0/3] drm/omap: fix am4 evm lcd Tomi Valkeinen
2019-11-14 9:39 ` [PATCH 1/3] ARM: dts: am437x-gp/epos-evm: fix panel compatible Tomi Valkeinen
2019-12-02 13:01 ` Laurent Pinchart
2019-12-11 16:51 ` Tony Lindgren
2019-11-14 9:39 ` [PATCH 2/3] ARM: dts: am437x-gp/epos-evm: drop unused panel timings Tomi Valkeinen
2019-12-02 13:04 ` Laurent Pinchart
2019-12-11 16:53 ` Tony Lindgren
2019-12-12 9:37 ` Tomi Valkeinen
2019-12-12 20:35 ` Laurent Pinchart
2020-01-13 12:01 ` Tomi Valkeinen
2020-02-11 10:01 ` Tomi Valkeinen
2020-02-11 11:07 ` Laurent Pinchart
2020-02-11 11:08 ` Tomi Valkeinen
2020-02-11 11:10 ` Laurent Pinchart
2020-02-14 0:33 ` Sebastian Reichel
2020-02-11 12:54 ` Merlijn Wajer
2020-02-11 16:05 ` Tony Lindgren
2020-02-11 16:13 ` Tomi Valkeinen
2020-02-11 16:27 ` Tony Lindgren
2020-02-11 17:22 ` Tomi Valkeinen
2020-02-13 21:57 ` Sebastian Reichel
2019-11-14 9:39 ` [PATCH 3/3] drm/panel: simple: fix osd070t1718_19ts sync drive edge Tomi Valkeinen
2019-12-02 13:07 ` Laurent Pinchart
2020-01-13 12:04 ` Tomi Valkeinen
2020-02-10 8:15 ` Tomi Valkeinen
2020-02-14 21:39 ` Sam Ravnborg
2020-02-21 10:43 ` Tomi Valkeinen
2020-02-22 12:16 ` Sam Ravnborg [this message]
2019-11-27 12:59 ` [PATCH 0/3] drm/omap: fix am4 evm lcd Tomi Valkeinen
2019-11-27 15:45 ` Tony Lindgren
2019-11-28 7:03 ` Tomi Valkeinen
2019-12-02 13:13 ` Laurent Pinchart
2019-12-02 13:24 ` Adam Ford
2019-12-03 21:27 ` Laurent Pinchart
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=20200222121606.GB28287@ravnborg.org \
--to=sam@ravnborg.org \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jsarha@ti.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=peter.ujfalusi@ti.com \
--cc=thierry.reding@gmail.com \
--cc=tomi.valkeinen@ti.com \
--cc=tony@atomide.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;
as well as URLs for NNTP newsgroup(s).