[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <cover.1761753288.git.dan.carpenter@linaro.org>
Date: Wed, 29 Oct 2025 20:27:00 +0300
From: Dan Carpenter <dan.carpenter@...aro.org>
To: Lee Jones <lee@...nel.org>
Cc: Arnd Bergmann <arnd@...db.de>, Conor Dooley <conor+dt@...nel.org>,
	devicetree@...r.kernel.org,
	Krzysztof Kozlowski <krzk+dt@...nel.org>,
	linux-kernel@...r.kernel.org, Rob Herring <robh@...nel.org>,
	André Draszik <andre.draszik@...aro.org>,
	Peter Griffin <peter.griffin@...aro.org>
Subject: [PATCH 0/2] mfd: syscon: introduce no-auto-mmio DT property
Most syscons are accessed via MMMIO and created automatically.  But one
example of a syscon that isn't is in drivers/soc/samsung/exynos-pmu.c
where the syscon can only be accessed via the secure partition.  We are
looking at upstreaming a different driver where the syscon will be
accessed via SCMI.
Normally, syscons are accessed by doing something like
syscon_regmap_lookup_by_phandle_args() but that function will
automatically create an MMIO syscon if one hasn't been registered.  So
the ordering becomes a problem.  The exynos-pmu.c driver solves this
but it's a bit awkward and it would be even trickier if there were
several drivers accessing the same syscon.
Dan Carpenter (2):
  dt-bindings: mfd: syscon: introduce no-auto-mmio property for syscons
  mfd: syscon: Don't auto create "no-auto-mmio" syscons
 Documentation/devicetree/bindings/mfd/syscon.yaml |  4 ++++
 drivers/mfd/syscon.c                              | 10 ++++++++--
 2 files changed, 12 insertions(+), 2 deletions(-)
-- 
2.51.0
Powered by blists - more mailing lists
 
