linux-kernel - Re: [PATCH v2] i2c: ocores: set IACK bit after core is enabled

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

Message-Id: <171892558671.2178094.6404949110171049934.b4-ty@kernel.org>
Date: Fri, 21 Jun 2024 01:19:46 +0200
From: Andi Shyti <andi.shyti@...nel.org>
To: Markus Elfring <Markus.Elfring@....de>, 
 Peter Korsgaard <peter@...sgaard.com>, Andrew Lunn <andrew@...n.ch>, 
 Thomas Gleixner <tglx@...utronix.de>, linux-i2c@...r.kernel.org, 
 linux-kernel@...r.kernel.org, Grygorii Tertychnyi <grembeter@...il.com>
Cc: Grygorii Tertychnyi <grygorii.tertychnyi@...ca-geosystems.com>, 
 bsp-development.geo@...ca-geosystems.com, stable@...r.kernel.org
Subject: Re: [PATCH v2] i2c: ocores: set IACK bit after core is enabled

Hi

On Mon, 20 May 2024 17:39:32 +0200, Grygorii Tertychnyi wrote:
> Setting IACK bit when core is disabled does not clear the "Interrupt Flag"
> bit in the status register, and the interrupt remains pending.
> 
> Sometimes it causes failure for the very first message transfer, that is
> usually a device probe.
> 
> Hence, set IACK bit after core is enabled to clear pending interrupt.
> 
> [...]

Applied to i2c/i2c-host-next on

git://git.kernel.org/pub/scm/linux/kernel/git/local tree

Thank you,
Andi

Patches applied
===============
[1/1] i2c: ocores: set IACK bit after core is enabled
      commit: 5a72477273066b5b357801ab2d315ef14949d402