From: Sam Ravnborg <sam@ravnborg.org>
To: Adam Ford <aford173@gmail.com>
Cc: Fabio Estevam <festevam@gmail.com>,
David Airlie <airlied@linux.ie>,
Tomi Valkeinen <tomi.valkeinen@ti.com>,
Adam Ford-BE <aford@beaconembedded.com>,
stable <stable@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
Thierry Reding <thierry.reding@gmail.com>,
DRI mailing list <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH] drm/panel-simple: fix connector type for LogicPD Type28 Display
Date: Sun, 21 Jun 2020 08:22:19 +0200 [thread overview]
Message-ID: <20200621062219.GE74146@ravnborg.org> (raw)
In-Reply-To: <CAHCN7x+=xjFTy6J4Ej61U2jXTez2rLrt=KtEOzbvV7Tzq6XoPQ@mail.gmail.com>
Hi Adam.
On Mon, Jun 15, 2020 at 09:53:45AM -0500, Adam Ford wrote:
> On Mon, Jun 15, 2020 at 9:46 AM Fabio Estevam <festevam@gmail.com> wrote:
> >
> > On Mon, Jun 15, 2020 at 10:19 AM Adam Ford <aford173@gmail.com> wrote:
> > >
> > > The LogicPD Type28 display used by several Logic PD products has not
> > > worked since v5.5.
> >
> > Maybe you could tell which commit exactly and then put a Fixes tag?
>
> I honestly don't know. I reached out to the omap mailing list,
> because I noted this issue. Tomi V from TI responded with a link that
> he posted which fixes this for another display.
>
> https://www.mail-archive.com/dri-devel@lists.freedesktop.org/msg312208.html
>
> I tested that patch and it worked for a different LCD, so I did the
> same thing to the Logic PD Type 28 display as well.
>
> My patch and commit message were modeled after his, and his commit
> CC's stable with a note about being required for v5.5+
>
> I added him to the CC list, so maybe he knows which hash needs to be
> referenced from a fixes tag. I was hoping to not have to go back and
> bisect if it's not required, but I will if necessary.
git blame is your friend - the panel was added here:
0d35408afbeb6 (Adam Ford 2019-10-16 08:51:45 -0500 2469) static const struct panel_desc logicpd_type_28 = {
0d35408afbeb6 (Adam Ford 2019-10-16 08:51:45 -0500 2470) .modes = &logicpd_type_28_mode,
0d35408afbeb6 (Adam Ford 2019-10-16 08:51:45 -0500 2471) .num_modes = 1,
0d35408afbeb6 (Adam Ford 2019-10-16 08:51:45 -0500 2472) .bpc = 8,
0d35408afbeb6 (Adam Ford 2019-10-16 08:51:45 -0500 2473) .size = {
0d35408afbeb6 (Adam Ford 2019-10-16 08:51:45 -0500 2474) .width = 105,
0d35408afbeb6 (Adam Ford 2019-10-16 08:51:45 -0500 2475) .height = 67,
0d35408afbeb6 (Adam Ford 2019-10-16 08:51:45 -0500 2476) },
So this gives us fllowing fixes info:
Fixes: 0d35408afbeb ("drm/panel: simple: Add Logic PD Type 28 display support")
Cc: Adam Ford <aford173@gmail.com>
Cc: Sam Ravnborg <sam@ravnborg.org>
Cc: Thierry Reding <thierry.reding@gmail.com>
Cc: dri-devel@lists.freedesktop.org
Cc: <stable@vger.kernel.org> # v5.6+
I have adjusted the changelog to say 5.6 and applied to drm-misc-fixes
Sam
prev parent reply other threads:[~2020-06-21 6:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-15 13:19 Adam Ford
2020-06-15 14:45 ` Fabio Estevam
2020-06-15 14:53 ` Adam Ford
2020-06-16 12:30 ` Tomi Valkeinen
2020-06-21 6:22 ` Sam Ravnborg [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=20200621062219.GE74146@ravnborg.org \
--to=sam@ravnborg.org \
--cc=aford173@gmail.com \
--cc=aford@beaconembedded.com \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=festevam@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.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
all inboxes | Powered by JetHome®