lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <499cf369-2ff7-47e9-a66b-1fce8b1bd4c3@foss.st.com>
Date: Fri, 14 Nov 2025 09:28:28 +0100
From: Alexandre TORGUE <alexandre.torgue@...s.st.com>
To: Patrice Chotard <patrice.chotard@...s.st.com>,
        Rob Herring
	<robh@...nel.org>,
        Krzysztof Kozlowski <krzk+dt@...nel.org>,
        Conor Dooley
	<conor+dt@...nel.org>,
        Maxime Coquelin <mcoquelin.stm32@...il.com>
CC: <devicetree@...r.kernel.org>, <linux-stm32@...md-mailman.stormreply.com>,
        <linux-arm-kernel@...ts.infradead.org>, <linux-kernel@...r.kernel.org>,
        <stable@...r.kernel.org>
Subject: Re: [PATCH v4] arm64: dts: st: Add memory-region-names property for
 stm32mp257f-ev1

Hi Patrice

On 10/31/25 15:07, Patrice Chotard wrote:
> In order to set the AMCR register, which configures the
> memory-region split between ospi1 and ospi2, we need to
> identify the ospi instance.
> 
> By using memory-region-names, it allows to identify the
> ospi instance this memory-region belongs to.
> 
> Fixes: cad2492de91c ("arm64: dts: st: Add SPI NOR flash support on stm32mp257f-ev1 board")
> Cc: stable@...r.kernel.org
> Signed-off-by: Patrice Chotard <patrice.chotard@...s.st.com>
> ---
> Changes in v4:
> - Rebase on v6.18-rc1
> - Link to v3: https://lore.kernel.org/r/20250811-upstream_fix_dts_omm-v3-1-c4186b7667cb@foss.st.com
> 
> Changes in v3:
> - Set again "Cc: <stable@...r.kernel.org>"
> - Link to v2: https://lore.kernel.org/r/20250811-upstream_fix_dts_omm-v2-1-00ff55076bd5@foss.st.com
> 
> Changes in v2:
> - Update commit message.
> - Use correct memory-region-names value.
> - Remove "Cc: <stable@...r.kernel.org>" tag as the fixed patch is not part of a LTS.
> - Link to v1: https://lore.kernel.org/r/20250806-upstream_fix_dts_omm-v1-1-e68c15ed422d@foss.st.com
> ---
>   arch/arm64/boot/dts/st/stm32mp257f-ev1.dts | 1 +
>   1 file changed, 1 insertion(+)
> 
> diff --git a/arch/arm64/boot/dts/st/stm32mp257f-ev1.dts b/arch/arm64/boot/dts/st/stm32mp257f-ev1.dts
> index 6e165073f732..bb6d6393d2e4 100644
> --- a/arch/arm64/boot/dts/st/stm32mp257f-ev1.dts
> +++ b/arch/arm64/boot/dts/st/stm32mp257f-ev1.dts
> @@ -266,6 +266,7 @@ &i2c8 {
>   
>   &ommanager {
>   	memory-region = <&mm_ospi1>;
> +	memory-region-names = "ospi1";
>   	pinctrl-0 = <&ospi_port1_clk_pins_a
>   		     &ospi_port1_io03_pins_a
>   		     &ospi_port1_cs0_pins_a>;
> 
> ---
> base-commit: 3a8660878839faadb4f1a6dd72c3179c1df56787
> change-id: 20250806-upstream_fix_dts_omm-c006b69042f1
> 
> Best regards,

Applied on stm32-next.

Regards
Alex

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ