From: Dan Carpenter <dan.carpenter@linaro.org>
To: Conor Dooley <conor@kernel.org>
Cc: Lee Jones <lee@kernel.org>, Rob Herring <robh@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: Wed, 29 Oct 2025 20:41:51 +0300 [thread overview]
Message-ID: <aQJR36s0cY34cLrr@stanley.mountain> (raw)
In-Reply-To: <20251029-ambiance-snooper-43dc00dcee68@spud>
On Wed, Oct 29, 2025 at 05:33:48PM +0000, Conor Dooley wrote:
> 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.
>
> "System controller node represents a register region containing a set
> of miscellaneous registers."
>
> If this isn't actually a register region, but is instead an interface
> provided by SCMI or whatever "secure partition" is (optee?), why is the
> syscon compatible being used for the device in the first place?
In the case that I'm looking at, it really is a syscon. So right now
we're upstreaming it and it's an MMIO syscon. Very straight forward.
But later, I guess, they want to have a new firmware which will only let
you access the same registers through SCMI.
regards,
dan carpenter
next prev parent reply other threads:[~2025-10-29 17:41 UTC|newest]
Thread overview: 21+ 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 [this message]
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 17:27 ` [PATCH 2/2] mfd: syscon: Don't auto create "no-auto-mmio" syscons Dan Carpenter
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=aQJR36s0cY34cLrr@stanley.mountain \
--to=dan.carpenter@linaro.org \
--cc=conor+dt@kernel.org \
--cc=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.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