From: <Conor.Dooley@microchip.com>
To: <conor@kernel.org>, <Padmarao.Begari@microchip.com>
Cc: <u-boot@lists.denx.de>, <jagan@amarulasolutions.com>,
<rick@andestech.com>, <ycliang@andestech.com>,
<bmeng.cn@gmail.com>, <Cyril.Jean@microchip.com>,
<Valentina.FernandezAlanis@microchip.com>,
<Nagasuresh.Relli@microchip.com>
Subject: Re: [PATCH v2 1/4] riscv: dts: Update memory configuration
Date: Tue, 25 Oct 2022 19:50:42 +0000 [thread overview]
Message-ID: <10d8749c-6546-df72-155d-d16579ab448c@microchip.com> (raw)
In-Reply-To: <Y1PSP4O6R7jwjObl@spud>
On 22/10/2022 12:21, Conor Dooley wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>
> On Fri, Oct 21, 2022 at 12:29:19PM +0530, Padmarao Begari wrote:
>> In the v2022.10 Icicle reference design, the seg registers are going to be
>
> Hey Padmarao,
> Since the release was done the other day I think that this should be
> s/are going to be/have been
>
>> changed, resulting in a required change to the memory map.
>> A small 4MB reservation is made at the end of 32-bit DDR to provide some
>> memory for the HSS to use, so that it can cache its payload between
>> reboots of a specific context.
>>
>> Co-developed-by: Conor Dooley <conor.dooley@microchip.com>
>> Signed-off-by: Conor Dooley <conor.dooley@microchip.com>
>> Signed-off-by: Padmarao Begari <padmarao.begari@microchip.com>
>> Reviewed-by: Conor Dooley <conor.dooley@microchip.com>
>> ---
>> arch/riscv/dts/microchip-mpfs-icicle-kit.dts | 70 ++++----------------
>> 1 file changed, 14 insertions(+), 56 deletions(-)
>>
>> diff --git a/arch/riscv/dts/microchip-mpfs-icicle-kit.dts b/arch/riscv/dts/microchip-mpfs-icicle-kit.dts
>> index 287ef3d23b..876c475069 100644
>> --- a/arch/riscv/dts/microchip-mpfs-icicle-kit.dts
>> +++ b/arch/riscv/dts/microchip-mpfs-icicle-kit.dts
>> @@ -1,6 +1,6 @@
>> // SPDX-License-Identifier: (GPL-2.0+ OR MIT)
>> /*
>> - * Copyright (C) 2021 Microchip Technology Inc.
>> + * Copyright (C) 2021-2022 Microchip Technology Inc.
>> * Padmarao Begari <padmarao.begari@microchip.com>
>> */
>>
>> @@ -28,70 +28,28 @@
>> timebase-frequency = <RTCCLK_FREQ>;
>> };
>
> FWIW I think we should add the compatible that the linux dt has,
> signifying that this memory layout is compatible with the v2022.10
> release and later (w/ appropriate line-wrapping ofc):
> compatible = "microchip,mpfs-icicle-reference-rtlv2210", "microchip,mpfs-icicle-kit", "microchip,mpfs";
>
> Other than that:
> Reviewed-by: Conor Dooley <conor.dooley@microchip.com>
>
>>
>> - reserved-memory {
>> - ranges;
>> - #size-cells = <2>;
>> - #address-cells = <2>;
>> -
>> - fabricbuf0: fabricbuf@0 {
>> - compatible = "shared-dma-pool";
>> - reg = <0x0 0xae000000 0x0 0x2000000>;
>> - label = "fabricbuf0-ddr-c";
>> - };
>> -
>> - fabricbuf1: fabricbuf@1 {
>> - compatible = "shared-dma-pool";
>> - reg = <0x0 0xc0000000 0x0 0x8000000>;
>> - label = "fabricbuf1-ddr-nc";
>> - };
>> -
>> - fabricbuf2: fabricbuf@2 {
>> - compatible = "shared-dma-pool";
>> - reg = <0x0 0xd8000000 0x0 0x8000000>;
>> - label = "fabricbuf2-ddr-nc-wcb";
>> - };
>> - };
>> -
>> - udmabuf0 {
>> - compatible = "ikwzm,u-dma-buf";
>> - device-name = "udmabuf-ddr-c0";
>> - minor-number = <0>;
>> - size = <0x0 0x2000000>;
>> - memory-region = <&fabricbuf0>;
>> - sync-mode = <3>;
>> - };
>> -
>> - udmabuf1 {
>> - compatible = "ikwzm,u-dma-buf";
>> - device-name = "udmabuf-ddr-nc0";
>> - minor-number = <1>;
>> - size = <0x0 0x8000000>;
>> - memory-region = <&fabricbuf1>;
>> - sync-mode = <3>;
>> - };
>> -
>> - udmabuf2 {
>> - compatible = "ikwzm,u-dma-buf";
>> - device-name = "udmabuf-ddr-nc-wcb0";
>> - minor-number = <2>;
>> - size = <0x0 0x8000000>;
>> - memory-region = <&fabricbuf2>;
>> - sync-mode = <3>;
>> - };
>> -
>> ddrc_cache_lo: memory@80000000 {
>> device_type = "memory";
>> - reg = <0x0 0x80000000 0x0 0x2e000000>;
>> - clocks = <&clkcfg CLK_DDRC>;
>> + reg = <0x0 0x80000000 0x0 0x40000000>;
>> status = "okay";
>> };
>>
>> ddrc_cache_hi: memory@1000000000 {
Sorry for not noticing prior, but this should bee changed too to match
the reg property shouldn't it..
>> device_type = "memory";
>> - reg = <0x10 0x0 0x0 0x40000000>;
>> - clocks = <&clkcfg CLK_DDRC>;
>> + reg = <0x10 0x40000000 0x0 0x40000000>;
>> status = "okay";
>> };
>> +
>> + reserved-memory {
>> + #address-cells = <2>;
>> + #size-cells = <2>;
>> + ranges;
>> +
>> + hss_payload: region@BFC00000 {
>> + reg = <0x0 0xBFC00000 0x0 0x400000>;
>> + no-map;
>> + };
>> + };
>> };
>>
>> &uart1 {
>> --
>> 2.25.1
>>
next prev parent reply other threads:[~2022-10-25 19:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-21 6:59 [PATCH v2 0/4] Update Microchip PolarFire SoC Padmarao Begari
2022-10-21 6:59 ` [PATCH v2 1/4] riscv: dts: Update memory configuration Padmarao Begari
2022-10-22 11:21 ` Conor Dooley
2022-10-25 19:50 ` Conor.Dooley [this message]
2022-10-26 6:05 ` Padmarao.Begari
2022-10-26 6:04 ` Padmarao.Begari
2022-10-21 6:59 ` [PATCH v2 2/4] riscv: dts: Add QSPI NAND device node Padmarao Begari
2022-10-22 11:27 ` Conor Dooley
2022-10-21 6:59 ` [PATCH v2 3/4] spi: Add Microchip PolarFire SoC QSPI driver Padmarao Begari
2022-10-22 11:46 ` Conor Dooley
2022-10-26 6:13 ` Padmarao.Begari
2022-10-21 6:59 ` [PATCH v2 4/4] riscv: Update Microchip MPFS Icicle Kit support Padmarao Begari
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=10d8749c-6546-df72-155d-d16579ab448c@microchip.com \
--to=conor.dooley@microchip.com \
--cc=Cyril.Jean@microchip.com \
--cc=Nagasuresh.Relli@microchip.com \
--cc=Padmarao.Begari@microchip.com \
--cc=Valentina.FernandezAlanis@microchip.com \
--cc=bmeng.cn@gmail.com \
--cc=conor@kernel.org \
--cc=jagan@amarulasolutions.com \
--cc=rick@andestech.com \
--cc=u-boot@lists.denx.de \
--cc=ycliang@andestech.com \
/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