From: Rob Herring <robh@kernel.org>
To: Dan Carpenter <dan.carpenter@linaro.org>
Cc: Lee Jones <lee@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: mfd: syscon: introduce no-auto-mmio property for syscons
Date: Thu, 30 Oct 2025 13:16:43 -0500 [thread overview]
Message-ID: <20251030181643.GA130921-robh@kernel.org> (raw)
In-Reply-To: <230cf12861a4f0b9effc72522444d3e28c1de2c9.1761753288.git.dan.carpenter@linaro.org>
On Wed, Oct 29, 2025 at 08:27:05PM +0300, Dan Carpenter wrote:
> Generally, syscons are created automatically and accessed direclty via
> MMIO however sometimes syscons might only be accessible from the secure
> partition or through SCMI etc. Introduce the no-auto-mmio property to
> tell the operating system that the syscon needs to be handled manually.
>
> Signed-off-by: Dan Carpenter <dan.carpenter@linaro.org>
> ---
> Documentation/devicetree/bindings/mfd/syscon.yaml | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/mfd/syscon.yaml b/Documentation/devicetree/bindings/mfd/syscon.yaml
> index 657c38175fba..a0ad12ae0bee 100644
> --- a/Documentation/devicetree/bindings/mfd/syscon.yaml
> +++ b/Documentation/devicetree/bindings/mfd/syscon.yaml
> @@ -245,6 +245,10 @@ properties:
> resets:
> maxItems: 1
>
> + no-auto-mmio:
> + type: boolean
> + description: Prevents the syscon from being created automatically
"syscon" literally means "have Linux create a regmap for me". If you
don't want that, don't use the "syscon" compatible. Really, I wish we'd
never added it in the first place.
Rob
next prev parent reply other threads:[~2025-10-30 18:16 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-29 17:27 [PATCH 0/2] mfd: syscon: introduce no-auto-mmio DT property Dan Carpenter
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 [this message]
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=20251030181643.GA130921-robh@kernel.org \
--to=robh@kernel.org \
--cc=conor+dt@kernel.org \
--cc=dan.carpenter@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.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).