linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Gatien CHEVALLIER <gatien.chevallier@foss.st.com>
To: "Clément Le Goffic" <legoffic.clement@gmail.com>,
	"Maxime Coquelin" <mcoquelin.stm32@gmail.com>,
	"Alexandre Torgue" <alexandre.torgue@foss.st.com>,
	"Michael Turquette" <mturquette@baylibre.com>,
	"Stephen Boyd" <sboyd@kernel.org>,
	"Rob Herring" <robh@kernel.org>,
	"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
	"Conor Dooley" <conor+dt@kernel.org>,
	"Gabriel Fernandez" <gabriel.fernandez@foss.st.com>,
	"Krzysztof Kozlowski" <krzk@kernel.org>,
	"Julius Werner" <jwerner@chromium.org>,
	"Will Deacon" <will@kernel.org>,
	"Mark Rutland" <mark.rutland@arm.com>,
	"Philipp Zabel" <p.zabel@pengutronix.de>,
	"Jonathan Corbet" <corbet@lwn.net>
Cc: linux-stm32@st-md-mailman.stormreply.com,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-clk@vger.kernel.org,
	devicetree@vger.kernel.org, linux-perf-users@vger.kernel.org,
	linux-doc@vger.kernel.org,
	"Clément Le Goffic" <clement.legoffic@foss.st.com>
Subject: Re: [PATCH v6 01/20] bus: firewall: move stm32_firewall header file in include folder
Date: Tue, 9 Sep 2025 14:25:38 +0200	[thread overview]
Message-ID: <9a46c8a8-1d25-410c-9fa2-267eb4040390@foss.st.com> (raw)
In-Reply-To: <20250909-b4-ddrperfm-upstream-v6-1-ce082cc801b5@gmail.com>



On 9/9/25 12:12, Clément Le Goffic wrote:
> From: Clément Le Goffic <clement.legoffic@foss.st.com>
> 
> Other driver than rifsc and etzpc can implement firewall ops, such as
> rcc.
> In order for them to have access to the ops and type of this framework,
> we need to get the `stm32_firewall.h` file in the include/ folder.
> 
> Signed-off-by: Clément Le Goffic <clement.legoffic@foss.st.com>
> Signed-off-by: Clément Le Goffic <legoffic.clement@gmail.com>
> ---
>   drivers/bus/stm32_etzpc.c                       | 3 +--
>   drivers/bus/stm32_firewall.c                    | 3 +--
>   drivers/bus/stm32_rifsc.c                       | 3 +--
>   {drivers => include/linux}/bus/stm32_firewall.h | 0
>   4 files changed, 3 insertions(+), 6 deletions(-)
> 
> diff --git a/drivers/bus/stm32_etzpc.c b/drivers/bus/stm32_etzpc.c
> index 7fc0f16960be..4918a14e507e 100644
> --- a/drivers/bus/stm32_etzpc.c
> +++ b/drivers/bus/stm32_etzpc.c
> @@ -5,6 +5,7 @@
>   
>   #include <linux/bitfield.h>
>   #include <linux/bits.h>
> +#include <linux/bus/stm32_firewall.h>
>   #include <linux/device.h>
>   #include <linux/err.h>
>   #include <linux/init.h>
> @@ -16,8 +17,6 @@
>   #include <linux/platform_device.h>
>   #include <linux/types.h>
>   
> -#include "stm32_firewall.h"
> -
>   /*
>    * ETZPC registers
>    */
> diff --git a/drivers/bus/stm32_firewall.c b/drivers/bus/stm32_firewall.c
> index 2fc9761dadec..ef4988054b44 100644
> --- a/drivers/bus/stm32_firewall.c
> +++ b/drivers/bus/stm32_firewall.c
> @@ -5,6 +5,7 @@
>   
>   #include <linux/bitfield.h>
>   #include <linux/bits.h>
> +#include <linux/bus/stm32_firewall.h>
>   #include <linux/bus/stm32_firewall_device.h>
>   #include <linux/device.h>
>   #include <linux/err.h>
> @@ -18,8 +19,6 @@
>   #include <linux/types.h>
>   #include <linux/slab.h>
>   
> -#include "stm32_firewall.h"
> -
>   /* Corresponds to STM32_FIREWALL_MAX_EXTRA_ARGS + firewall ID */
>   #define STM32_FIREWALL_MAX_ARGS		(STM32_FIREWALL_MAX_EXTRA_ARGS + 1)
>   
> diff --git a/drivers/bus/stm32_rifsc.c b/drivers/bus/stm32_rifsc.c
> index 4cf1b60014b7..643ddd0a5f54 100644
> --- a/drivers/bus/stm32_rifsc.c
> +++ b/drivers/bus/stm32_rifsc.c
> @@ -5,6 +5,7 @@
>   
>   #include <linux/bitfield.h>
>   #include <linux/bits.h>
> +#include <linux/bus/stm32_firewall.h>
>   #include <linux/device.h>
>   #include <linux/err.h>
>   #include <linux/init.h>
> @@ -16,8 +17,6 @@
>   #include <linux/platform_device.h>
>   #include <linux/types.h>
>   
> -#include "stm32_firewall.h"
> -
>   /*
>    * RIFSC offset register
>    */
> diff --git a/drivers/bus/stm32_firewall.h b/include/linux/bus/stm32_firewall.h
> similarity index 100%
> rename from drivers/bus/stm32_firewall.h
> rename to include/linux/bus/stm32_firewall.h
> 

Hi Clément,

Thank you for keeping up the work on this series.

As the firewall header is moved to a dedicated firewall directory,
maybe it would be coherent to create the same kind of directory
for the sources as non-buses drivers use it. I can test it on my
side if you're willing to make the change.

Sorry for the late comment.

Cheers,
Gatien

  reply	other threads:[~2025-09-09 12:25 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-09 10:12 [PATCH v6 00/20] Introduce STM32 DDR PMU for STM32MP platforms Clément Le Goffic
2025-09-09 10:12 ` [PATCH v6 01/20] bus: firewall: move stm32_firewall header file in include folder Clément Le Goffic
2025-09-09 12:25   ` Gatien CHEVALLIER [this message]
2025-09-10  7:47     ` Clément Le Goffic
2025-09-10  8:42       ` Gatien CHEVALLIER
2025-09-10  9:43         ` Clément Le Goffic
2025-09-10  9:52           ` Gatien CHEVALLIER
2025-09-09 10:12 ` [PATCH v6 02/20] dt-bindings: stm32: stm32mp25: add `#access-controller-cells` property Clément Le Goffic
2025-09-09 10:12 ` [PATCH v6 03/20] clk: stm32mp25: add firewall grant_access ops Clément Le Goffic
2025-09-09 10:12 ` [PATCH v6 04/20] arm64: dts: st: set rcc as an access-controller Clément Le Goffic
2025-09-09 10:12 ` [PATCH v6 05/20] dt-bindings: memory: factorise LPDDR props into SDRAM props Clément Le Goffic
2025-09-10  7:54   ` Krzysztof Kozlowski
2025-09-10  8:31     ` Clément Le Goffic
2025-09-10  8:41     ` Clément Le Goffic
2025-09-10  8:52       ` Krzysztof Kozlowski
2025-09-09 10:12 ` [PATCH v6 06/20] dt-bindings: memory: introduce DDR4 Clément Le Goffic
2025-09-09 10:12 ` [PATCH v6 07/20] dt-bindings: memory: factorise LPDDR channel binding into SDRAM channel Clément Le Goffic
2025-09-09 10:12 ` [PATCH v6 08/20] dt-binding: memory: add DDR4 channel compatible Clément Le Goffic
2025-09-09 10:12 ` [PATCH v6 09/20] dt-bindings: memory: SDRAM channel: standardise node name Clément Le Goffic
2025-09-09 10:12 ` [PATCH v6 10/20] arm64: dts: st: add LPDDR channel to stm32mp257f-dk board Clément Le Goffic
2025-09-09 10:12 ` [PATCH v6 11/20] arm64: dts: st: add DDR channel to stm32mp257f-ev1 board Clément Le Goffic
2025-09-09 10:12 ` [PATCH v6 12/20] dt-bindings: perf: stm32: introduce DDRPERFM dt-bindings Clément Le Goffic
2025-09-10  7:57   ` Krzysztof Kozlowski
2025-09-10  8:33     ` Clément Le Goffic
2025-09-10  7:57   ` Krzysztof Kozlowski
2025-09-10  8:34     ` Clément Le Goffic
2025-09-09 10:12 ` [PATCH v6 13/20] perf: stm32: introduce DDRPERFM driver Clément Le Goffic
2025-09-10  9:26   ` Jonathan Cameron
2025-09-11  9:56     ` Clément Le Goffic
2025-09-09 10:12 ` [PATCH v6 14/20] Documentation: perf: stm32: add ddrperfm support Clément Le Goffic
2025-09-09 10:12 ` [PATCH v6 15/20] MAINTAINERS: add myself as STM32 DDR PMU maintainer Clément Le Goffic
2025-09-09 10:12 ` [PATCH v6 16/20] ARM: dts: stm32: add ddrperfm on stm32mp131 Clément Le Goffic
2025-09-09 10:12 ` [PATCH v6 17/20] ARM: dts: stm32: add ddrperfm on stm32mp151 Clément Le Goffic
2025-09-09 10:12 ` [PATCH v6 18/20] arm64: dts: st: add ddrperfm on stm32mp251 Clément Le Goffic
2025-09-09 10:12 ` [PATCH v6 19/20] arm64: dts: st: support ddrperfm on stm32mp257f-dk Clément Le Goffic
2025-09-09 10:12 ` [PATCH v6 20/20] arm64: dts: st: support ddrperfm on stm32mp257f-ev1 Clément Le Goffic

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=9a46c8a8-1d25-410c-9fa2-267eb4040390@foss.st.com \
    --to=gatien.chevallier@foss.st.com \
    --cc=alexandre.torgue@foss.st.com \
    --cc=clement.legoffic@foss.st.com \
    --cc=conor+dt@kernel.org \
    --cc=corbet@lwn.net \
    --cc=devicetree@vger.kernel.org \
    --cc=gabriel.fernandez@foss.st.com \
    --cc=jwerner@chromium.org \
    --cc=krzk+dt@kernel.org \
    --cc=krzk@kernel.org \
    --cc=legoffic.clement@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=linux-stm32@st-md-mailman.stormreply.com \
    --cc=mark.rutland@arm.com \
    --cc=mcoquelin.stm32@gmail.com \
    --cc=mturquette@baylibre.com \
    --cc=p.zabel@pengutronix.de \
    --cc=robh@kernel.org \
    --cc=sboyd@kernel.org \
    --cc=will@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).