From: Dmitry Osipenko <digetx@gmail.com>
To: "Wang, Jiada" <jiada_wang@mentor.com>,
"nick@shmanahar.org" <nick@shmanahar.org>,
"dmitry.torokhov@gmail.com" <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>,
"erosca@de.adit-jv.com" <erosca@de.adit-jv.com>,
"Gabbasov, Andrew" <Andrew_Gabbasov@mentor.com>
Subject: Re: [PATCH 1/1] Input: atmel_mxt_ts - allow specification of firmware file name
Date: Sun, 16 Aug 2020 19:31:50 +0300 [thread overview]
Message-ID: <affa0525-2543-b121-2793-b8dc022e98f1@gmail.com> (raw)
In-Reply-To: <a0af72eb-11d9-cab1-c79a-0c42c3eb0e19@mentor.com>
12.08.2020 13:11, Wang, Jiada пишет:
>> Have you decided to abandon the patch which allowed to specify firmware
>> name in a device tree?
>>
> In v11 patch-set, there is a patch allows user to specify config file
> name via device-tree and sysfs, I will drop device-tree part, since
> Dmitry Torokhov commented he would like to change the behavior of
> firmware loading during boot time,
> but I will keep sysfs interface part, which is similar to this patch but
> for configuration file.
Okay!
BTW, looking forward to the "I2C retrying" patch, which is needed for
the mxt1386 controller. The Acer A500 device-tree has been merged into
upstream, but some pieces are still missing in the kernel which are
needed to get that device fully functional, the mxt1386 controller
support is one of those pieces.
prev parent reply other threads:[~2020-08-16 16:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-31 7:57 [PATCH 1/1] Input: atmel_mxt_ts - allow specification of firmware file name Jiada Wang
2020-08-09 20:11 ` Dmitry Osipenko
2020-08-12 10:11 ` Wang, Jiada
2020-08-16 16:31 ` 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=affa0525-2543-b121-2793-b8dc022e98f1@gmail.com \
--to=digetx@gmail.com \
--cc=Andrew_Gabbasov@mentor.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).