linux-kernel - Re: [PATCH v10 43/55] dt-bindings: input: atmel: support to set max bytes transferred

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: <008d019c-2de7-4fe4-0c22-2668312f808b@gmail.com>
Date:   Tue, 7 Apr 2020 17:47:07 +0300
From:   Dmitry Osipenko <digetx@...il.com>
To:     "Wang, Jiada" <jiada_wang@...tor.com>, nick@...anahar.org,
        dmitry.torokhov@...il.com, jikos@...nel.org,
        benjamin.tissoires@...hat.com, bsz@...ihalf.com
Cc:     linux-input@...r.kernel.org, linux-kernel@...r.kernel.org,
        erosca@...adit-jv.com, Andrew_Gabbasov@...tor.com
Subject: Re: [PATCH v10 43/55] dt-bindings: input: atmel: support to set max
 bytes transferred

07.04.2020 12:27, Wang, Jiada пишет:
..
>> Is this a software (firmware) limitation which varies from version to
>> version?
>>
> 
> the timeout issue trying to be addressed in this patch is from software,
> one of our board a Serializer/Deserializer bridge exists between the SoC
> (imx6) and the Atmel touch controller.
> imx6 i2c controller driver has a timeout value(100ms) for each i2c
> transaction,
> Large i2c read transaction failed to complete within this timeout value
> and therefore imx6 i2c controller driver aborts the transaction
> and returns failure.
> 
> Therefore this patch was created to split the large i2c transaction into
> smaller chunks which can complete
> within the timeout defined by i2c controller driver.

Isn't it possible to use the max_read/write_len of the generic struct
i2c_adapter_quirks for limiting the transfer size?

BTW, it looks like the i.MX I2C driver doesn't specify the
i2c_adapter_quirks, which probably needs to be fixed.