From: Dmitry Osipenko <digetx@gmail.com>
To: "Wang, Jiada" <jiada_wang@mentor.com>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: nick@shmanahar.org, linux-input@vger.kernel.org,
linux-kernel@vger.kernel.org, andy.shevchenko@gmail.com,
erosca@de.adit-jv.com, Andrew_Gabbasov@mentor.com
Subject: Re: [PATCH v4 1/1] Input: atmel_mxt_ts - implement I2C retries
Date: Tue, 15 Sep 2020 20:40:10 +0300 [thread overview]
Message-ID: <e4acf85a-e9cb-8c6a-1161-65617d93649d@gmail.com> (raw)
In-Reply-To: <b451e91a-ed9f-51cb-1765-e68867e0a86f@mentor.com>
15.09.2020 18:55, Wang, Jiada пишет:
...
>> Jiada, will you be able to re-work this patch? Please note that the new
>> "atmel,mXT1386" DT compatible needs to be added into the
>> atmel,maxtouch.txt binding.
>
> Yes, I can re-work this patch, and add one more change to dts-binding.
>
> to summarize long discussion in this thread,
> I think what I need to do are:
> 1) since the change will be different from current one, I will need to
> start a new patch
> 2) call mxt_wake() in mxt_probe() and mxt_resume()
in mxt_initialize(), mxt_load_fw() and mxt_start()
> 3) update atmel,maxtouch.txt binding
>
> please correct me if I am wrong.
sounds good
prev parent reply other threads:[~2020-09-15 18:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-12 0:55 [PATCH v4 1/1] Input: atmel_mxt_ts - implement I2C retries Jiada Wang
2020-09-13 8:43 ` Andy Shevchenko
2020-09-13 12:57 ` Dmitry Osipenko
2020-09-14 13:49 ` Andy Shevchenko
2020-09-14 15:26 ` Dmitry Osipenko
2020-09-14 15:50 ` Andy Shevchenko
2020-09-14 16:28 ` Dmitry Osipenko
2020-09-13 16:56 ` Dmitry Torokhov
2020-09-14 17:29 ` Dmitry Osipenko
2020-09-14 19:33 ` Dmitry Torokhov
2020-09-14 19:36 ` Dmitry Torokhov
2020-09-14 21:33 ` Dmitry Osipenko
2020-09-14 22:32 ` Dmitry Torokhov
2020-09-15 1:13 ` Rob Herring
2020-09-15 15:55 ` Wang, Jiada
2020-09-15 17:40 ` Dmitry Osipenko [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=e4acf85a-e9cb-8c6a-1161-65617d93649d@gmail.com \
--to=digetx@gmail.com \
--cc=Andrew_Gabbasov@mentor.com \
--cc=andy.shevchenko@gmail.com \
--cc=dmitry.torokhov@gmail.com \
--cc=erosca@de.adit-jv.com \
--cc=jiada_wang@mentor.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nick@shmanahar.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).