Re: [PATCH RFC] regmap: maple: Switch to use irq-safe locking

From: Mark Brown <broonie@kernel.org>
To: Cristian Ciocaltea <cristian.ciocaltea@collabora.com>
Cc: "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	"Heiko Stübner" <heiko@sntech.de>,
	"Andy Yan" <andy.yan@rock-chips.com>,
	kernel@collabora.com, linux-kernel@vger.kernel.org,
	linux-rockchip@lists.infradead.org
Subject: Re: [PATCH RFC] regmap: maple: Switch to use irq-safe locking
Date: Wed, 14 Aug 2024 20:25:06 +0100	[thread overview]
Message-ID: <408477bf-2f00-46cd-b962-cb2d17bde8ae@sirena.org.uk> (raw)
In-Reply-To: <4a8c9f85-3785-4cbd-be9b-dc6da9bd7324@sirena.org.uk>

[-- Attachment #1.1: Type: text/plain, Size: 831 bytes --]

On Wed, Aug 14, 2024 at 08:04:07PM +0100, Mark Brown wrote:

> My first thought here is that if we've got a regmap using spinlocks for
> the regmap lock and a maple tree cache we should arrange things so that
> the maple tree lock is used for the regmap's lock.  That would however
> involve some unpleasant abstraction violation, and possibly some macro
> fun since we'd need to elide the locking from the cache itself when
> using the same lock at the regmap level.  I think that's going to be a
> case of choosing the least unpleasant option.

Actually I think that modulo issues with devices that disable regmap
level locking entirely or use hwspinlocks we can persuade the cache to
always use the regmap level lock, even for mutexes, which might clean up
the code a bit and would avoid the double locking for the common case.

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

[-- Attachment #2: Type: text/plain, Size: 170 bytes --]

_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip