From: Tony Lindgren <tony@atomide.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: devicetree@vger.kernel.org, Jyri Sarha <jsarha@ti.com>,
Peter Ujfalusi <peter.ujfalusi@ti.com>,
Tomi Valkeinen <tomi.valkeinen@ti.com>,
Thierry Reding <thierry.reding@gmail.com>,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 1/3] ARM: dts: am437x-gp/epos-evm: fix panel compatible
Date: Wed, 11 Dec 2019 08:51:52 -0800 [thread overview]
Message-ID: <20191211165152.GB43123@atomide.com> (raw)
In-Reply-To: <20191202130129.GG4929@pendragon.ideasonboard.com>
* Laurent Pinchart <laurent.pinchart@ideasonboard.com> [191202 13:02]:
> Hi Tomi,
>
> Thank you for the patch.
>
> On Thu, Nov 14, 2019 at 11:39:48AM +0200, Tomi Valkeinen wrote:
> > The LCD panel on AM4 GP EVMs and ePOS boards seems to be
> > osd070t1718-19ts. The current dts files say osd057T0559-34ts. Possibly
> > the panel has changed since the early EVMs, or there has been a mistake
> > with the panel type.
> >
> > Update the DT files accordingly.
> >
> > Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ti.com>
>
> Acked-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Applying this one into fixes thanks.
Regards,
Tony
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-12-12 8:56 UTC|newest]
Thread overview: 39+ 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 ` Tomi Valkeinen
2019-11-14 9:39 ` [PATCH 1/3] ARM: dts: am437x-gp/epos-evm: fix panel compatible Tomi Valkeinen
2019-11-14 9:39 ` Tomi Valkeinen
2019-12-02 13:01 ` Laurent Pinchart
2019-12-11 16:51 ` Tony Lindgren [this message]
2019-11-14 9:39 ` [PATCH 2/3] ARM: dts: am437x-gp/epos-evm: drop unused panel timings Tomi Valkeinen
2019-11-14 9:39 ` 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-11-14 9:39 ` 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
2019-11-27 12:59 ` [PATCH 0/3] drm/omap: fix am4 evm lcd Tomi Valkeinen
2019-11-27 12:59 ` 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=20191211165152.GB43123@atomide.com \
--to=tony@atomide.com \
--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 \
/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).