From: Conor Dooley <conor@kernel.org>
To: Conor Dooley <conor.dooley@microchip.com>
Cc: Daire McNamara <daire.mcnamara@microchip.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
linux-riscv@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] riscv: dts: microchip: fix memory node unit address for icicle
Date: Mon, 31 Oct 2022 19:55:00 +0000 [thread overview]
Message-ID: <Y2AoFCbQFGnWT48Y@spud> (raw)
In-Reply-To: <20221025195643.1215890-1-conor@kernel.org>
On Tue, Oct 25, 2022 at 08:56:44PM +0100, Conor Dooley wrote:
> From: Conor Dooley <conor.dooley@microchip.com>
>
> Evidently I forgot to update the unit address for the 38-bit cached
> memory node when I changed the address in the reg property..
> Update it to match.
>
> Fixes: 6c1193301791 ("riscv: dts: microchip: update memory configuration for v2022.10")
> Signed-off-by: Conor Dooley <conor.dooley@microchip.com>
Applied:
https://git.kernel.org/conor/c/d6105a8b7c160a73ae04054c8921eba80a294146
> ---
> arch/riscv/boot/dts/microchip/mpfs-icicle-kit.dts | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/riscv/boot/dts/microchip/mpfs-icicle-kit.dts b/arch/riscv/boot/dts/microchip/mpfs-icicle-kit.dts
> index ec7b7c2a3ce2..8ced67c3b00b 100644
> --- a/arch/riscv/boot/dts/microchip/mpfs-icicle-kit.dts
> +++ b/arch/riscv/boot/dts/microchip/mpfs-icicle-kit.dts
> @@ -37,7 +37,7 @@ ddrc_cache_lo: memory@80000000 {
> status = "okay";
> };
>
> - ddrc_cache_hi: memory@1000000000 {
> + ddrc_cache_hi: memory@1040000000 {
> device_type = "memory";
> reg = <0x10 0x40000000 0x0 0x40000000>;
> status = "okay";
> --
> 2.38.0
>
prev parent reply other threads:[~2022-10-31 19:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-25 19:56 [PATCH] riscv: dts: microchip: fix memory node unit address for icicle Conor Dooley
2022-10-31 19:55 ` Conor Dooley [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=Y2AoFCbQFGnWT48Y@spud \
--to=conor@kernel.org \
--cc=aou@eecs.berkeley.edu \
--cc=conor.dooley@microchip.com \
--cc=daire.mcnamara@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.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;
as well as URLs for NNTP newsgroup(s).