From: Krzysztof Kozlowski <krzk@kernel.org>
To: Gatien Chevallier <gatien.chevallier@foss.st.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>
Cc: devicetree@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-clk@vger.kernel.org
Subject: Re: [PATCH v2 1/9] dt-bindings: bus: document the RISAB firewall peripheral
Date: Fri, 13 Feb 2026 16:07:42 +0100 [thread overview]
Message-ID: <f45e77d7-0d0b-4236-a661-cc44d3460214@kernel.org> (raw)
In-Reply-To: <20260212-stm32_risab-v2-1-02ef2859b596@foss.st.com>
On 12/02/2026 11:10, Gatien Chevallier wrote:
> +
> + memory-region:
> + minItems: 1
> + maxItems: 32
> + description:
> + Phandle to nodes describing memory regions to be configured in the RISAB
> + by the trusted domain of at least a RISAB page size.
> + These regions cannot overlap. A region must be within st,mem-map range and
> + can be represented by one or more pages. RISAB has a 4kBytes page
> + granularity and each page can hold different access rights.
> +
> + st,mem-map:
> + $ref: /schemas/types.yaml#/definitions/uint32-array
> + description: Memory address range covered by the RISAB.
> + items:
> + - description: Memory range base address
> + - description: Memory range size
I did reply at v1 now. This is not a trivial device so should not be rushed.
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-02-13 15:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-12 10:10 [PATCH v2 0/9] drivers: bus: add RISAB dump debug driver Gatien Chevallier
2026-02-12 10:10 ` [PATCH v2 1/9] dt-bindings: bus: document the RISAB firewall peripheral Gatien Chevallier
2026-02-13 15:07 ` Krzysztof Kozlowski [this message]
2026-02-12 10:10 ` [PATCH v2 2/9] bus: add RISAB dump debug driver Gatien Chevallier
2026-02-12 10:10 ` [PATCH v2 3/9] bus: rifsc: use new CONFIG_STM32_FIREWALL_DEBUG switch Gatien Chevallier
2026-02-12 17:29 ` kernel test robot
2026-02-12 10:10 ` [PATCH v2 4/9] arm64: dts: st: add RISAB1/2/3/4/5/6 nodes to stm32mp251.dtsi Gatien Chevallier
2026-02-12 10:10 ` [PATCH v2 5/9] arm64: dts: st: add RISAB1/2/3/4/5/6 nodes to stm32mp231.dtsi Gatien Chevallier
2026-02-12 10:10 ` [PATCH v2 6/9] arm64: dts: st: enable all RISAB instances on the stm32mp257f-ev1 board Gatien Chevallier
2026-02-12 10:10 ` [PATCH v2 7/9] arm64: dts: st: enable all RISAB instances on the stm32mp257f-dk board Gatien Chevallier
2026-02-12 10:10 ` [PATCH v2 8/9] arm64: dts: st: enable all RISAB instances on the stm32mp235f-dk board Gatien Chevallier
2026-02-12 10:10 ` [PATCH v2 9/9] MAINTAINERS: add entries to maintained stm32 firewall files Gatien Chevallier
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=f45e77d7-0d0b-4236-a661-cc44d3460214@kernel.org \
--to=krzk@kernel.org \
--cc=alexandre.torgue@foss.st.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gatien.chevallier@foss.st.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=mturquette@baylibre.com \
--cc=robh@kernel.org \
--cc=sboyd@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