linux-kernel - Re: [PATCH v11 04/56] Input: atmel_mxt_ts - split large i2c transfers into blocks

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4b7fbb6d-4f64-6d23-38a0-636f144df6a7@mentor.com>
Date:   Tue, 30 Jun 2020 23:33:15 +0900
From:   "Wang, Jiada" <jiada_wang@...tor.com>
To:     Dmitry Torokhov <dmitry.torokhov@...il.com>
CC:     <nick@...anahar.org>, <jikos@...nel.org>,
        <benjamin.tissoires@...hat.com>, <bsz@...ihalf.com>,
        <linux-input@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
        <erosca@...adit-jv.com>, <Andrew_Gabbasov@...tor.com>
Subject: Re: [PATCH v11 04/56] Input: atmel_mxt_ts - split large i2c transfers
 into blocks

Hello Dmitry

On 2020/05/12 7:19, Dmitry Torokhov wrote:
> Hi Jiada, Nick,
> 
> On Thu, May 07, 2020 at 10:56:04PM -0700, Jiada Wang wrote:
>> From: Nick Dyer <nick.dyer@...ev.co.uk>
>>
>> On some firmware variants, the size of the info block exceeds what can
>> be read in a single transfer.
> 
> Is this limitation of the mXT controller or maybe it is issue with
> implementation of the particular i2c adapter and should be dealt with
> there?
> 
This patch was authored by Nick,
but I assume it is trying to address issue due to I2C adapter limitation
which following patch in this series is already doing
"Input: atmel_mxt_ts: Limit the max bytes transferred in an i2c transaction"

I will extend patch "Input: atmel_mxt_ts: Limit the max bytes 
transferred in an i2c transaction"
to also cover this case.

Thanks,
Jiada

> Thanks.
>