linux-kernel - [PATCH v2 0/2] i2c:imx: Deliver a timely stop on slave side, fix recv

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-next>] [day] [month] [year] [list]

Message-Id: <20211112133956.655179-1-minyard@acm.org>
Date:   Fri, 12 Nov 2021 07:39:54 -0600
From:   minyard@....org
To:     Oleksij Rempel <o.rempel@...gutronix.de>
Cc:     Pengutronix Kernel Team <kernel@...gutronix.de>,
        linux-i2c@...r.kernel.org, linux-kernel@...r.kernel.org,
        Corey Minyard <minyard@....org>
Subject: [PATCH v2 0/2] i2c:imx: Deliver a timely stop on slave side, fix recv

I was working on an application that needs the stop condition
immediately.  So this adds a timer after each byte is received/sent and
if the bus is idle at the timeout, send the stop.

Also, I noticed when you use the i2c-slave-eeprom, if you read some data
and then read some data again, the last byte of the first read will be
the first byte of the second read.  This is because i2c-slave-eeprom
expects a read-ahead.  That's what the documentation says, at least.

Thanks to Uwe Kleine-König and Oleksij Rempel for reviewing.

-corey

Changes since v1:

* Added a comment on the hrtimer cancel on why the return value didn't
  need to be checked.

* Combine the hrtimer patch into the main timer patch.