linux-kernel - Re: (subset) [PATCH v3] mfd: axp20x: AXP717: Fix missing IRQ status registers range

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: <171835102238.2975804.6897127880257764523.b4-ty@kernel.org>
Date: Fri, 14 Jun 2024 08:43:42 +0100
From: Lee Jones <lee@...nel.org>
To: Chen-Yu Tsai <wens@...e.org>, Andre Przywara <andre.przywara@....com>
Cc: Jernej Skrabec <jernej.skrabec@...il.com>, linux-kernel@...r.kernel.org, 
 linux-sunxi@...ts.linux.dev, Chris Morgan <macroalpha82@...il.com>, 
 Ryan Walklin <ryan@...ttoast.com>, 
 Philippe Simons <simons.philippe@...il.com>
Subject: Re: (subset) [PATCH v3] mfd: axp20x: AXP717: Fix missing IRQ
 status registers range

On Fri, 14 Jun 2024 00:31:04 +0100, Andre Przywara wrote:
> While we list the "IRQ status *and acknowledge*" registers as volatile
> in the MFD description, they are missing from the writable range array,
> so acknowledging any interrupts was met with an -EIO error.
> This error propagates up, leading to the whole AXP717 driver failing to
> probe, which is fatal to most systems using this PMIC, since most
> peripherals refer one of the PMIC voltage rails.
> This wasn't noticed on the initial submission, since the interrupt was
> completely missing at this point, but the DTs now merged describe the
> interrupt, creating the problem.
> 
> [...]

Applied, thanks!

[1/1] mfd: axp20x: AXP717: Fix missing IRQ status registers range
      commit: 569c5136baf12c3b8dd137ac356f2a7ceb38bdb5

--
Lee Jones [李琼斯]