From: Oliver Graute <oliver.graute@kococonnector.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Carlis <zhangxuezhi1@yulong.com>,
dri-devel@lists.freedesktop.org, linux-fbdev@vger.kernel.org,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] fbtft: fb_st7789v: added reset on init_display()
Date: Thu, 10 Feb 2022 09:49:40 +0100 [thread overview]
Message-ID: <20220210084940.GE10212@optiplex> (raw)
In-Reply-To: <YRaJDyYquuklht6C@kroah.com>
On 13/08/21, Greg KH wrote:
> On Fri, Aug 13, 2021 at 02:54:30PM +0200, Oliver Graute wrote:
> > On 13/08/21, Greg KH wrote:
> > > On Fri, Aug 13, 2021 at 08:25:10AM +0200, Oliver Graute wrote:
> > > > staging: fbtft: fb_st7789v: reset display before initialization
> > >
> > > What is this line here, and why is this not your subject line instead?
> >
> > I'll put the line as subject instead.
> >
> > > > In rare cases the display is flipped or mirrored. This was observed more
> > > > often in a low temperature environment. A clean reset on init_display()
> > > > should help to get registers in a sane state.
> > > >
> > > > Signed-off-by: Oliver Graute <oliver.graute@kococonnector.com>
> > >
> > > What commit does this fix?
> >
> > this is a fix for a rare behavior of the fb_st7789v display. Not a
> > bugfix for a specific commit.
>
> So if it has always been broken, list the commit where the code was
> added to the kernel, as this should be backported to the stable kernels,
> right?
ok thx, will list the commit and add stable@vger.kernel.org to cc
thx,
Oliver
prev parent reply other threads:[~2022-02-10 9:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-13 6:25 [PATCH v1] fbtft: fb_st7789v: added reset on init_display() Oliver Graute
2021-08-13 8:20 ` Greg KH
2021-08-13 12:54 ` Oliver Graute
2021-08-13 15:00 ` Greg KH
2022-02-10 8:49 ` Oliver Graute [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=20220210084940.GE10212@optiplex \
--to=oliver.graute@kococonnector.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=zhangxuezhi1@yulong.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).