From: Jiada Wang <jiada_wang@mentor.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: <nick@shmanahar.org>, <linux-input@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <george_davis@mentor.com>
Subject: Re: [PATCH v1 04/63] Input: atmel_mxt_ts - split large i2c transfers into blocks
Date: Thu, 22 Aug 2019 14:24:39 +0900 [thread overview]
Message-ID: <4f9aaee0-c3de-3ad4-4c66-333afd92240e@mentor.com> (raw)
In-Reply-To: <20190816171837.GG121898@dtor-ws>
Hi Dmitry
On 2019/08/17 2:18, Dmitry Torokhov wrote:
> On Fri, Aug 16, 2019 at 05:28:53PM +0900, Jiada Wang wrote:
>> From: Nick Dyer <nick.dyer@itdev.co.uk>
>>
>> On some firmware variants, the size of the info block exceeds what can
>> be read in a single transfer.
>>
>> Signed-off-by: Nick Dyer <nick.dyer@itdev.co.uk>
>> (cherry picked from ndyer/linux/for-upstream commit 74c4f5277cfa403d43fafc404119dc57a08677db)
>> [gdavis: Forward port and fix conflicts due to v4.14.51 commit
>> 960fe000b1d3 ("Input: atmel_mxt_ts - fix the firmware
>> update").]
>> Signed-off-by: George G. Davis <george_davis@mentor.com>
>> Signed-off-by: Jiada Wang <jiada_wang@mentor.com>
>> ---
>> drivers/input/touchscreen/atmel_mxt_ts.c | 27 +++++++++++++++++++++---
>> 1 file changed, 24 insertions(+), 3 deletions(-)
>>
>> diff --git a/drivers/input/touchscreen/atmel_mxt_ts.c b/drivers/input/touchscreen/atmel_mxt_ts.c
>> index 9b165d23e092..2d70ddf71cd9 100644
>> --- a/drivers/input/touchscreen/atmel_mxt_ts.c
>> +++ b/drivers/input/touchscreen/atmel_mxt_ts.c
>> @@ -40,7 +40,7 @@
>> #define MXT_OBJECT_START 0x07
>> #define MXT_OBJECT_SIZE 6
>> #define MXT_INFO_CHECKSUM_SIZE 3
>> -#define MXT_MAX_BLOCK_WRITE 256
>> +#define MXT_MAX_BLOCK_WRITE 255
>>
>> /* Object types */
>> #define MXT_DEBUG_DIAGNOSTIC_T37 37
>> @@ -659,6 +659,27 @@ static int __mxt_read_reg(struct i2c_client *client,
>> return ret;
>> }
>>
>> +static int mxt_read_blks(struct mxt_data *data, u16 start, u16 count, u8 *buf)
>
> Can we call this __mxt_read_reg() and the original read reg call
> __mxt_read_chunk()?
>
yes, I will update in v2 patch-set,
so that every call to __mxt_read_reg() in atmel driver,
can have the feature to split large size transfer.
Thanks,
Jiada
>> +{
>> + u16 offset = 0;
>> + int error;
>> + u16 size;
>> +
>> + while (offset < count) {
>> + size = min(MXT_MAX_BLOCK_WRITE, count - offset);
>> +
>> + error = __mxt_read_reg(data->client,
>> + start + offset,
>> + size, buf + offset);
>> + if (error)
>> + return error;
>> +
>> + offset += size;
>> + }
>> +
>> + return 0;
>> +}
>
> Thanks.
>
next prev parent reply other threads:[~2019-08-22 5:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-16 8:28 [PATCH v1 00/63] atmel_mxt_ts misc Jiada Wang
2019-08-16 8:28 ` [PATCH v1 01/63] Input: introduce input_mt_report_slot_inactive Jiada Wang
2019-08-16 17:12 ` Dmitry Torokhov
2019-08-21 9:13 ` Jiada Wang
2019-08-16 8:28 ` [PATCH v1 02/63] Input: atmel_mxt_ts - rework sysfs init/remove Jiada Wang
2019-08-16 8:28 ` [PATCH v1 03/63] Input: atmel_mxt_ts - only read messages in mxt_acquire_irq() when necessary Jiada Wang
2019-08-16 17:16 ` Dmitry Torokhov
2019-08-21 13:26 ` Jiada Wang
2019-08-21 17:54 ` Dmitry Torokhov
2019-08-22 3:37 ` Jiada Wang
2019-08-16 8:28 ` [PATCH v1 04/63] Input: atmel_mxt_ts - split large i2c transfers into blocks Jiada Wang
2019-08-16 17:18 ` Dmitry Torokhov
2019-08-22 5:24 ` Jiada Wang [this message]
2019-08-16 17:32 ` [PATCH v1 00/63] atmel_mxt_ts misc Dmitry Torokhov
2019-08-19 9:29 ` Jiada Wang
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=4f9aaee0-c3de-3ad4-4c66-333afd92240e@mentor.com \
--to=jiada_wang@mentor.com \
--cc=dmitry.torokhov@gmail.com \
--cc=george_davis@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
all inboxes | Powered by JetHome®