Received-SPF: pass (google.com: domain of linux-kernel+bounces-214474-linux.lists.archive=gmail.com@vger.kernel.org designates 139.178.88.99 as permitted sender) client-ip=139.178.88.99;
From: Lee Jones <lee@kernel.org>
To: Chen-Yu Tsai <wens@csie.org>, Andre Przywara <andre.przywara@arm.com>
Cc: Jernej Skrabec <jernej.skrabec@gmail.com>, linux-kernel@vger.kernel.org, 
 linux-sunxi@lists.linux.dev, Chris Morgan <macroalpha82@gmail.com>, 
 Ryan Walklin <ryan@testtoast.com>, 
 Philippe Simons <simons.philippe@gmail.com>
In-Reply-To: <20240613233104.17529-1-andre.przywara@arm.com>
References: <20240613233104.17529-1-andre.przywara@arm.com>
Subject: Re: (subset) [PATCH v3] mfd: axp20x: AXP717: Fix missing IRQ
 status registers range
Message-Id: <171835102238.2975804.6897127880257764523.b4-ty@kernel.org>
Date: Fri, 14 Jun 2024 08:43:42 +0100
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit

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 [李琼斯]