All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Valek, Andrej" <andrej.valek@siemens.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: "linux-input@vger.kernel.org" <linux-input@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"kbuild-all@lists.01.org" <kbuild-all@lists.01.org>
Subject: RE: [PATCH v2] Input: st1232 - add support resolution reading
Date: Fri, 20 Nov 2020 07:17:20 +0000	[thread overview]
Message-ID: <AM0PR10MB3971222411966A87E29A9F5C92FF0@AM0PR10MB3971.EURPRD10.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <DB8PR10MB3977BDD73A260EE7999DD76892E70@DB8PR10MB3977.EURPRD10.PROD.OUTLOOK.COM>

Hello again Dimitry,

I haven't received any response yet, so I will ask again.

I would like to know, the current status about my other patches for goodix and atmel input.
Are there any problems, or what I have to do, to be applied?

Thanks,
Andrej

> Hello Dimitry,
> 
> Thank you for that.
> What about the other patches?
>
> Regards,
> Andrej
>
>> -----Original Message-----
>> From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
>> Sent: Thursday, November 12, 2020 2:54 AM>
>> To: Valek, Andrej (ADV D EU SK SI-BP1) <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
>> 
>> 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

      parent reply	other threads:[~2020-11-20  7:17 UTC|newest]

Thread overview: 11+ 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-02 18:05   ` kernel test robot
2020-11-03  7:39   ` [PATCH v2] " Andrej Valek
2020-11-03  7:39     ` Andrej Valek
2020-11-12  1:53     ` Dmitry Torokhov
2020-11-12  1:53       ` Dmitry Torokhov
2020-11-12  8:11       ` Valek, Andrej
2020-11-12  8:11       ` Valek, Andrej
2020-11-20  7:17         ` Valek, Andrej
2020-11-20  7:17         ` Valek, Andrej [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=AM0PR10MB3971222411966A87E29A9F5C92FF0@AM0PR10MB3971.EURPRD10.PROD.OUTLOOK.COM \
    --to=andrej.valek@siemens.com \
    --cc=dmitry.torokhov@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.