linux-kernel - Re: (subset) [PATCH] mfd: da9063: Split chip variant reading in two bus transactions

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 for Android: free password hash cracker in your pocket

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

Message-Id: <175680081626.2184374.7626461049800985884.b4-ty@kernel.org>
Date: Tue, 02 Sep 2025 09:13:36 +0100
From: Lee Jones <lee@...nel.org>
To: Support Opensource <support.opensource@...semi.com>, 
 Lee Jones <lee@...nel.org>, linux-kernel@...r.kernel.org, 
 Jens Kehne <jens.kehne@...lent.com>
Subject: Re: (subset) [PATCH] mfd: da9063: Split chip variant reading in
 two bus transactions

On Mon, 04 Aug 2025 15:37:54 +0200, Jens Kehne wrote:
> We observed the initial probe of the da9063 failing in
> da9063_get_device_type in about 30% of boots on a Xilinx ZynqMP based
> board. The problem originates in da9063_i2c_blockreg_read, which uses
> a single bus transaction to turn the register page and then read a
> register. On the bus, this should translate to a write to register 0,
> followed by a read to the target register, separated by a repeated
> start. However, we found that after the write to register 0, the
> controller sometimes continues directly with the register address of
> the read request, without sending the chip address or a repeated start
> in between, which makes the read request invalid.
> 
> [...]

Applied, thanks!

[1/1] mfd: da9063: Split chip variant reading in two bus transactions
      commit: a0d1178ea4778fc1eb1691a97619ecdb8a3bda13

--
Lee Jones [李琼斯]