From: "Arnd Bergmann" <arnd@arndb.de>
To: "Dario Binacchi" <dario.binacchi@amarulasolutions.com>,
linux-kernel@vger.kernel.org
Cc: "Amarula patchwork" <linux-amarula@amarulasolutions.com>,
"Alexandre Torgue" <alexandre.torgue@foss.st.com>,
"Conor Dooley" <conor+dt@kernel.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Maxime Coquelin" <mcoquelin.stm32@gmail.com>,
"Rob Herring" <robh+dt@kernel.org>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-stm32@st-md-mailman.stormreply.com
Subject: Re: [RFC PATCH] ARM: dts: stm32: fix SDRAM size on stm32f469-disco
Date: Sat, 09 Sep 2023 16:27:57 +0200 [thread overview]
Message-ID: <738c3b54-1f42-454a-90be-505ceba7544b@app.fastmail.com> (raw)
In-Reply-To: <20230904180513.923280-1-dario.binacchi@amarulasolutions.com>
On Mon, Sep 4, 2023, at 20:05, Dario Binacchi wrote:
> The board is equipped with a 128Mbit SDRAM.
> 128Mbit = 16 Mbyte = 16,777,216 bytes = 0x1000000.
>
> Fixes: 626e7ea00215 ("ARM: DT: stm32: move dma translation to board files")
> Link: https://www.st.com/en/evaluation-tools/32f469idiscovery.html
> Signed-off-by: Dario Binacchi <dario.binacchi@amarulasolutions.com>
>
> ---
>
> arch/arm/boot/dts/st/stm32f469-disco.dts | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/arm/boot/dts/st/stm32f469-disco.dts
> b/arch/arm/boot/dts/st/stm32f469-disco.dts
> index cbbd521bf010..f173a5892b7d 100644
> --- a/arch/arm/boot/dts/st/stm32f469-disco.dts
> +++ b/arch/arm/boot/dts/st/stm32f469-disco.dts
> @@ -84,7 +84,7 @@ vdd_dsi: vdd-dsi {
> };
>
> soc {
> - dma-ranges = <0xc0000000 0x0 0x10000000>;
> + dma-ranges = <0xc0000000 0x0 0x1000000>;
> };
The dma-ranges should be independent of the installed
memory, they usually reflect the addressing capabilities
of the bus, so this patch should not be needed.
Arnd
next prev parent reply other threads:[~2023-09-09 16:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-04 18:05 Dario Binacchi
2023-09-09 14:27 ` Arnd Bergmann [this message]
2023-09-10 14:31 ` Dario Binacchi
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=738c3b54-1f42-454a-90be-505ceba7544b@app.fastmail.com \
--to=arnd@arndb.de \
--cc=alexandre.torgue@foss.st.com \
--cc=conor+dt@kernel.org \
--cc=dario.binacchi@amarulasolutions.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-amarula@amarulasolutions.com \
--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+dt@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®