From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Andrej Valek <andrej.valek@siemens.com>
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
kbuild-all@lists.01.org
Subject: Re: [PATCH v2] Input: st1232 - add support resolution reading
Date: Wed, 11 Nov 2020 17:53:48 -0800 [thread overview]
Message-ID: <20201112015348.GD1003057@dtor-ws> (raw)
In-Reply-To: <20201103073949.12198-1-andrej.valek@siemens.com>
On Tue, Nov 03, 2020 at 08:39:49AM +0100, Andrej Valek wrote:
> Hard-coding resolution for st1633 device was wrong. Some of LCDs like
> YTS700TLBC-02-100C has assembled Sitronix st1633 touchcontroller too. But
> the resolution is not 320x480 as was hard-coded.
> Add new function which reads correct resolution directly from register.
>
> Signed-off-by: Andrej Valek <andrej.valek@siemens.com>
Applied, thank you.
--
Dmitry
next prev parent reply other threads:[~2020-11-12 5:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-30 9:33 [PATCH] Input: st1232 - add support resolution reading Andrej Valek
2020-11-02 18:05 ` kernel test robot
2020-11-03 7:39 ` [PATCH v2] " Andrej Valek
2020-11-12 1:53 ` Dmitry Torokhov [this message]
2020-11-12 8:11 ` Valek, Andrej
2020-11-20 7:17 ` Valek, Andrej
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=20201112015348.GD1003057@dtor-ws \
--to=dmitry.torokhov@gmail.com \
--cc=andrej.valek@siemens.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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).