devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alexandre TORGUE <alexandre.torgue@foss.st.com>
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>
Cc: <devicetree@vger.kernel.org>,
	<linux-stm32@st-md-mailman.stormreply.com>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>,
	"Conor Dooley" <conor.dooley@microchip.com>
Subject: Re: [PATCH v2 0/3] bus: rifsc: add stm32mp21 support and config dump debug entry
Date: Fri, 14 Nov 2025 09:51:16 +0100	[thread overview]
Message-ID: <01dbb151-148f-46af-b843-f96f99910ea6@foss.st.com> (raw)
In-Reply-To: <20251106-rifsc_debugfs-v2-0-f90e94ae756d@foss.st.com>

Hi Gatien

On 11/6/25 10:31, Gatien Chevallier wrote:
> The STM32MP21x platforms have a slightly different RIFSC. Add support
> for these platforms.
> 
> Also, the RIF is a complex firewall framework which can be tricky
> to debug. To facilitate the latter, add a debugfs entry that can
> be used to display the whole RIFSC firewall configuration at runtime.
> 
> Signed-off-by: Gatien Chevallier <gatien.chevallier@foss.st.com>
> ---
> Changes in v2:
> - Added Conor tag on bindings
> - Fixed coccinelle warning by using str_enabled_disabled() when
>    applicable
> - Link to v1: https://lore.kernel.org/r/20251104-rifsc_debugfs-v1-0-7ebdfbf8d33f@foss.st.com
> 
> ---
> Gatien Chevallier (3):
>        dt-bindings: bus: add stm32mp21 RIFSC compatible
>        arm64: dts: st: set RIFSC as an access controller on stm32mp21x platforms
>        bus: rifsc: add debugfs entry to dump the firewall configuration
> 
>   .../bindings/bus/st,stm32mp25-rifsc.yaml           |   8 +-
>   arch/arm64/boot/dts/st/stm32mp211.dtsi             |   4 +-
>   drivers/bus/stm32_rifsc.c                          | 597 ++++++++++++++++++++-
>   3 files changed, 602 insertions(+), 7 deletions(-)
> ---
> base-commit: 6146a0f1dfae5d37442a9ddcba012add260bceb0
> change-id: 20251104-rifsc_debugfs-5053ea033ce3
> 
> Best regards,

DT patch applied on stm32-next.

I'll send a dedicated PR for other patches to arm-soc tree.

regards
Alex


      parent reply	other threads:[~2025-11-14  9:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-06  9:31 [PATCH v2 0/3] bus: rifsc: add stm32mp21 support and config dump debug entry Gatien Chevallier
2025-11-06  9:31 ` [PATCH v2 1/3] dt-bindings: bus: add stm32mp21 RIFSC compatible Gatien Chevallier
2025-11-06  9:31 ` [PATCH v2 2/3] arm64: dts: st: set RIFSC as an access controller on stm32mp21x platforms Gatien Chevallier
2025-11-06  9:31 ` [PATCH v2 3/3] bus: rifsc: add debugfs entry to dump the firewall configuration Gatien Chevallier
2025-11-14  8:51 ` Alexandre TORGUE [this message]

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=01dbb151-148f-46af-b843-f96f99910ea6@foss.st.com \
    --to=alexandre.torgue@foss.st.com \
    --cc=conor+dt@kernel.org \
    --cc=conor.dooley@microchip.com \
    --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-kernel@vger.kernel.org \
    --cc=linux-stm32@st-md-mailman.stormreply.com \
    --cc=mcoquelin.stm32@gmail.com \
    --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).