From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id BDD56421F1E for ; Tue, 3 Mar 2026 11:20:36 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1772536836; cv=none; b=bxiQ/pMxdm6PFLeIJZIOjGp96NClbGKbRwX7NvyCKRdh2v97iLbsyEfRePuGZJGre5d82IazY909As5TP3PqcTw3SVZQFbv0ePoPdq1qIRCk7mg/ClHHjpO2HPRLxr6AKReEoTuUStqQJTCwDg2j1w8Gij+bHngvESc1OHxRh64= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1772536836; c=relaxed/simple; bh=/RwD50GH/hYyKftLjql+S+aYYQU4loay/XrUCStvoWc=; h=From:To:Cc:In-Reply-To:References:Subject:Message-Id:Date: MIME-Version:Content-Type; b=Wtp685L+qkdKNv/n8IEDJVJNC1hARz9RpO5eVfQMM39YOnjwm2F6LrrJmwk5OvN7Qt0z6u2wffMi61fz8faMaXNTJa2gAsx4XOk7daYZo39YVRCt++8ts9I7/AnuADM6g++mBa478ThsdtsPx7hb1rwchrnVGtWmEd7k4JXhG3s= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=gsjIrfXm; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="gsjIrfXm" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 50057C19422; Tue, 3 Mar 2026 11:20:35 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1772536836; bh=/RwD50GH/hYyKftLjql+S+aYYQU4loay/XrUCStvoWc=; h=From:To:Cc:In-Reply-To:References:Subject:Date:From; b=gsjIrfXm1e6WDobZtqEBNK74IZwhPzj37cONWPU76Ojm3uJRKVUaLpd4ASXxp6EXV JmtyOSpaVYdYJFryWe0k989JjAUF/mJhoZ5wjNjJrmRWso6KOfaK5oee4mPXky98e1 4FOtcMPFZ/J2/qLoRts3vNO1vphszAI1sG7MWLdmJHMbrWKzqWzMLmffuN2ok9pGYy XfC6swAr+yPqWwz+P7t7clQaLMFki4JUjb6zahutYY5OC5P37Bx5WJBPa07enegCPu sAZ1Cd4/pozFnUNsvyZSXaVM+BpWN9Tcx/N7fJ/Nq6GYbkV0YXxkM8Q7/IqGeHEgfM U5EhBZ4vFPSfg== From: Mark Brown To: Liam Girdwood , Franz Schnyder Cc: Franz Schnyder , linux-kernel@vger.kernel.org, Francesco Dolcini In-Reply-To: <20260218102518.238943-1-fra.schnyder@gmail.com> References: <20260218102518.238943-1-fra.schnyder@gmail.com> Subject: Re: [PATCH v1 0/2] regulator: pf9453: Fix IRQ trigger and allow sharing Message-Id: <177253683506.23082.12747093717844453080.b4-ty@kernel.org> Date: Tue, 03 Mar 2026 11:20:35 +0000 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit X-Mailer: b4 0.15-dev-38bf1 On Wed, 18 Feb 2026 11:25:13 +0100, Franz Schnyder wrote: > The IRQ_B pin is an open-drain output. The datasheet specifies, that the > IRQ_B pin is pulled low when any unmasked interrupt bit status > is changed, and it is released high once the application processor reads > the INT1 register. As it specifies a level-low behavior, it should not > force a falling-edge interrupt. > > Remove the IRQF_TRIGGER_FALLING to not force the falling-edge interrupt > and instead rely on the flag from the device tree. > Set the IRQF_SHARED to be able to share the interrupt line with > other devices. > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next Thanks! [1/2] regulator: pf9453: Respect IRQ trigger settings from firmware commit: 2d85ecd6fb0eb2fee0ffa040ec1ddea57b09bc38 [2/2] regulator: pf9453: Allow shared IRQ commit: e84141846decb77d2826e553318a608b256804e5 All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to Linus during the next merge window (or sooner if it is a bug fix), however if problems are discovered then the patch may be dropped or reverted. You may get further e-mails resulting from automated or manual testing and review of the tree, please engage with people reporting problems and send followup patches addressing any issues that are reported if needed. If any updates are required or you are submitting further changes they should be sent as incremental updates against current git, existing patches will not be replaced. Please add any relevant lists and maintainers to the CCs when replying to this mail. Thanks, Mark