From: Dan Carpenter <dan.carpenter@linaro.org>
To: Lee Jones <lee@kernel.org>
Cc: "Arnd Bergmann" <arnd@arndb.de>,
"Conor Dooley" <conor+dt@kernel.org>,
devicetree@vger.kernel.org,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
linux-kernel@vger.kernel.org, "Rob Herring" <robh@kernel.org>,
"André Draszik" <andre.draszik@linaro.org>,
"Peter Griffin" <peter.griffin@linaro.org>
Subject: [PATCH 0/2] mfd: syscon: introduce no-auto-mmio DT property
Date: Wed, 29 Oct 2025 20:27:00 +0300 [thread overview]
Message-ID: <cover.1761753288.git.dan.carpenter@linaro.org> (raw)
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
next reply other threads:[~2025-10-29 17:27 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-29 17:27 Dan Carpenter [this message]
2025-10-29 17:27 ` [PATCH 1/2] dt-bindings: mfd: syscon: introduce no-auto-mmio property for syscons Dan Carpenter
2025-10-29 17:33 ` Conor Dooley
2025-10-29 17:41 ` Dan Carpenter
2025-10-29 18:37 ` Conor Dooley
2025-10-29 18:47 ` Dan Carpenter
2025-10-29 22:00 ` Conor Dooley
2025-10-30 8:20 ` Krzysztof Kozlowski
2025-10-30 18:16 ` Rob Herring
2025-10-29 19:43 ` [PATCH 0/2] mfd: syscon: introduce no-auto-mmio DT property Arnd Bergmann
2025-10-30 7:33 ` Dan Carpenter
2025-10-30 8:33 ` Arnd Bergmann
2025-10-30 8:49 ` Dan Carpenter
2025-10-30 12:39 ` Dan Carpenter
2025-10-30 12:50 ` Chen-Yu Tsai
2025-10-30 13:09 ` Dan Carpenter
2025-10-30 14:10 ` Arnd Bergmann
2025-10-30 14:39 ` Chen-Yu Tsai
2025-10-30 18:21 ` Rob Herring
2025-10-30 12:59 ` Peter Griffin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cover.1761753288.git.dan.carpenter@linaro.org \
--to=dan.carpenter@linaro.org \
--cc=andre.draszik@linaro.org \
--cc=arnd@arndb.de \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peter.griffin@linaro.org \
--cc=robh@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).