Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
From:   Mark Brown <broonie@kernel.org>
To:     Vladimir Oltean <vladimir.oltean@nxp.com>
Cc:     Mark Brown <broonie@kernel.org>,
        Rasmus Villemoes <linux@rasmusvillemoes.dk>,
        Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
        linux-kernel@vger.kernel.org, Thomas Gleixner <tglx@linutronix.de>,
        Lee Jones <lee.jones@linaro.org>, Biwen Li <biwen.li@nxp.com>,
        Marc Zyngier <maz@kernel.org>,
        "Rafael J. Wysocki" <rafael@kernel.org>,
        Hou Zhiqiang <Zhiqiang.Hou@nxp.com>,
        Arnd Bergmann <arnd@arndb.de>
Subject: Re: (subset) [PATCH 0/2] Use raw spinlocks in the ls-extirq driver
Date:   Thu, 26 Aug 2021 13:51:09 +0100
Message-Id: <162998211486.33598.9715111275111133802.b4-ty@kernel.org>
In-Reply-To: <20210825205041.927788-1-vladimir.oltean@nxp.com>
References: <20210825205041.927788-1-vladimir.oltean@nxp.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk

On Wed, 25 Aug 2021 23:50:39 +0300, Vladimir Oltean wrote:
> The ls-extirq irqchip driver accesses regmap inside its implementation
> of the struct irq_chip :: irq_set_type method, and currently regmap
> only knows to lock using normal spinlocks. But the method above wants
> raw spinlock context, so this isn't going to work and triggers a
> "[ BUG: Invalid wait context ]" splat.
> 
> The best we can do given the arrangement of the code is to patch regmap
> and the syscon driver: regmap to support raw spinlocks, and syscon to
> request them on behalf of its ls-extirq consumer.
> 
> [...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.git for-next

Thanks!

[1/2] regmap: teach regmap to use raw spinlocks if requested in the config
      commit: 67021f25d95292d285dd213c58401642b98eaf24

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