devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Gabriel FERNANDEZ <gabriel.fernandez@foss.st.com>
To: "Clément Le Goffic" <legoffic.clement@gmail.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>,
	"Maxime Coquelin" <mcoquelin.stm32@gmail.com>,
	"Alexandre Torgue" <alexandre.torgue@foss.st.com>
Cc: linux-clk@vger.kernel.org, devicetree@vger.kernel.org,
	linux-stm32@st-md-mailman.stormreply.com,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org,
	"Clément Le Goffic" <clement.legoffic@foss.st.com>
Subject: Re: [PATCH v8 2/3] clk: stm32mp25: add firewall grant_access ops
Date: Tue, 30 Sep 2025 11:54:51 +0200	[thread overview]
Message-ID: <9852fdbf-c4bc-4087-a5c4-e65c3fefb724@foss.st.com> (raw)
In-Reply-To: <20250924-b4-rcc-upstream-v8-2-b32d46f71a38@gmail.com>


On 9/24/25 11:44, Clément Le Goffic wrote:
> From: Clément Le Goffic <clement.legoffic@foss.st.com>
>
> On STM32MP25, the RCC peripheral manages the secure level of resources
> that are used by other devices such as clocks.
> Declare this peripheral as a firewall controller.
>
> Signed-off-by: Clément Le Goffic <clement.legoffic@foss.st.com>
> Signed-off-by: Clément Le Goffic <legoffic.clement@gmail.com>
> ---

Hi Clément,

You can add

Reviewed-by: Gabriel Fernandez <gabriel.fernandez@foss.st.com>

Many Thanks!


>   drivers/clk/stm32/clk-stm32mp25.c | 40 ++++++++++++++++++++++++++++++++++++++-
>   1 file changed, 39 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/clk/stm32/clk-stm32mp25.c b/drivers/clk/stm32/clk-stm32mp25.c
> index 52f0e8a12926..af4bc06d703a 100644
> --- a/drivers/clk/stm32/clk-stm32mp25.c
> +++ b/drivers/clk/stm32/clk-stm32mp25.c
> @@ -4,8 +4,10 @@
>    * Author: Gabriel Fernandez <gabriel.fernandez@foss.st.com> for STMicroelectronics.
>    */
>   
> +#include <linux/bus/stm32_firewall.h>
>   #include <linux/bus/stm32_firewall_device.h>
>   #include <linux/clk-provider.h>
> +#include <linux/device.h>
>   #include <linux/io.h>
>   #include <linux/platform_device.h>
>   
> @@ -1602,6 +1604,11 @@ static int stm32_rcc_get_access(void __iomem *base, u32 index)
>   	return 0;
>   }
>   
> +static int stm32mp25_rcc_grant_access(struct stm32_firewall_controller *ctrl, u32 firewall_id)
> +{
> +	return stm32_rcc_get_access(ctrl->mmio, firewall_id);
> +}
> +
>   static int stm32mp25_check_security(struct device_node *np, void __iomem *base,
>   				    const struct clock_config *cfg)
>   {
> @@ -1970,6 +1977,7 @@ MODULE_DEVICE_TABLE(of, stm32mp25_match_data);
>   
>   static int stm32mp25_rcc_clocks_probe(struct platform_device *pdev)
>   {
> +	struct stm32_firewall_controller *rcc_controller;
>   	struct device *dev = &pdev->dev;
>   	void __iomem *base;
>   	int ret;
> @@ -1982,7 +1990,36 @@ static int stm32mp25_rcc_clocks_probe(struct platform_device *pdev)
>   	if (ret)
>   		return ret;
>   
> -	return stm32_rcc_init(dev, stm32mp25_match_data, base);
> +	ret = stm32_rcc_init(dev, stm32mp25_match_data, base);
> +	if (ret)
> +		return ret;
> +
> +	rcc_controller = devm_kzalloc(&pdev->dev, sizeof(*rcc_controller), GFP_KERNEL);
> +	if (!rcc_controller)
> +		return -ENOMEM;
> +
> +	rcc_controller->dev = dev;
> +	rcc_controller->mmio = base;
> +	rcc_controller->name = dev_driver_string(dev);
> +	rcc_controller->type = STM32_PERIPHERAL_FIREWALL;
> +	rcc_controller->grant_access = stm32mp25_rcc_grant_access;
> +
> +	platform_set_drvdata(pdev, rcc_controller);
> +
> +	ret = stm32_firewall_controller_register(rcc_controller);
> +	if (ret) {
> +		dev_err(dev, "Couldn't register as a firewall controller: %d\n", ret);
> +		return ret;
> +	}
> +
> +	return 0;
> +}
> +
> +static void stm32mp25_rcc_clocks_remove(struct platform_device *pdev)
> +{
> +	struct stm32_firewall_controller *rcc_controller = platform_get_drvdata(pdev);
> +
> +	stm32_firewall_controller_unregister(rcc_controller);
>   }
>   
>   static struct platform_driver stm32mp25_rcc_clocks_driver = {
> @@ -1991,6 +2028,7 @@ static struct platform_driver stm32mp25_rcc_clocks_driver = {
>   		.of_match_table = stm32mp25_match_data,
>   	},
>   	.probe = stm32mp25_rcc_clocks_probe,
> +	.remove = stm32mp25_rcc_clocks_remove,
>   };
>   
>   static int __init stm32mp25_clocks_init(void)
>

  reply	other threads:[~2025-09-30  9:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-24  9:44 [PATCH v8 0/3] Register the STM32MP25 RCC driver as an access controller Clément Le Goffic
2025-09-24  9:44 ` [PATCH v8 1/3] dt-bindings: stm32: stm32mp25: add `#access-controller-cells` property Clément Le Goffic
2025-09-24  9:44 ` [PATCH v8 2/3] clk: stm32mp25: add firewall grant_access ops Clément Le Goffic
2025-09-30  9:54   ` Gabriel FERNANDEZ [this message]
2025-09-24  9:44 ` [PATCH v8 3/3] arm64: dts: st: set RCC as an access-controller 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=9852fdbf-c4bc-4087-a5c4-e65c3fefb724@foss.st.com \
    --to=gabriel.fernandez@foss.st.com \
    --cc=alexandre.torgue@foss.st.com \
    --cc=clement.legoffic@foss.st.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=legoffic.clement@gmail.com \
    --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;
as well as URLs for NNTP newsgroup(s).