mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Patrice CHOTARD <patrice.chotard@foss.st.com>
To: 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: <devicetree@vger.kernel.org>,
	<linux-stm32@st-md-mailman.stormreply.com>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>, <stable@vger.kernel.org>
Subject: Re: [PATCH v3] arm64: dts: st: Add memory-region-names property for stm32mp257f-ev1
Date: Fri, 19 Sep 2025 09:07:27 +0200	[thread overview]
Message-ID: <257e006b-daab-4eed-9e1e-189d1b7a3167@foss.st.com> (raw)
In-Reply-To: <20250811-upstream_fix_dts_omm-v3-1-c4186b7667cb@foss.st.com>


On 8/11/25 15:28, 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@vger.kernel.org
> Signed-off-by: Patrice Chotard <patrice.chotard@foss.st.com>
> ---
> Changes in v3:
> - Set again "Cc: <stable@vger.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@vger.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 2f561ad4066544445e93db78557bc4be1c27095a..7bd8433c1b4344bb5d58193a5e6314f9ae89e0a4 100644
> --- a/arch/arm64/boot/dts/st/stm32mp257f-ev1.dts
> +++ b/arch/arm64/boot/dts/st/stm32mp257f-ev1.dts
> @@ -197,6 +197,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: 038d61fd642278bab63ee8ef722c50d10ab01e8f
> change-id: 20250806-upstream_fix_dts_omm-c006b69042f1
> 
> Best regards,

Hi Krzysztof 

Do you have any additional remarks on this patch ?
I would like this patch to be part of next kernel v6.18.

Thanks
Patrice




      reply	other threads:[~2025-09-19  7:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-11 13:28 Patrice Chotard
2025-09-19  7:07 ` Patrice CHOTARD [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=257e006b-daab-4eed-9e1e-189d1b7a3167@foss.st.com \
    --to=patrice.chotard@foss.st.com \
    --cc=alexandre.torgue@foss.st.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --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 \
    --cc=stable@vger.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

all inboxes | Powered by JetHome®