From: "Heiko Stübner" <heiko@sntech.de>
To: krzk@kernel.org, Chukun Pan <amadeus@jmu.edu.cn>
Cc: amadeus@jmu.edu.cn, conor+dt@kernel.org,
devicetree@vger.kernel.org, krzk+dt@kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-rockchip@lists.infradead.org,
Jonas Karlman <jonas@kwiboo.se>
Subject: Re: [PATCH 1/1] arm64: dts: rockchip: enable SCMI clk for RK3528 SoC
Date: Thu, 06 Mar 2025 15:25:36 +0100 [thread overview]
Message-ID: <24848438.6Emhk5qWAg@diego> (raw)
In-Reply-To: <20250306142008.389243-1-amadeus@jmu.edu.cn>
Am Donnerstag, 6. März 2025, 15:20:08 MEZ schrieb Chukun Pan:
> Hi,
>
> >> Any suggestions would be greatly appreciated.
> > Where is the SRAM located? Inside the SoC or is it carved out external
> > ROM/RAM?
>
> It is located in the SoC.
> "Embedded Memory" Area:
> BootROM | PMU_SRAM (8KB) | SYSTEM_SRAM (64KB) | OTP
are you really sure about that?
Looking at Jonas' recent rk3528 u-boot series [0]
0x0 _to_ 0xfc000000 is the SDRAM memory area
so 0x10f000 is a carveout of the main sdram.
Heiko
[0] https://lists.denx.de/pipermail/u-boot/2025-January/578393.html
next prev parent reply other threads:[~2025-03-06 14:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-06 13:10 [PATCH 0/1] arm64: dts: rockchip: enable SCMI clk for RK3528 SoC Chukun Pan
2025-03-06 13:10 ` [PATCH 1/1] " Chukun Pan
2025-03-06 13:29 ` Heiko Stübner
2025-03-06 13:40 ` Chukun Pan
2025-03-06 13:45 ` Krzysztof Kozlowski
2025-03-06 14:20 ` Chukun Pan
2025-03-06 14:25 ` Heiko Stübner [this message]
2025-03-06 14:50 ` Chukun Pan
2025-03-06 13:51 ` Heiko Stübner
2025-03-06 13:54 ` Krzysztof Kozlowski
2025-03-06 13:57 ` Heiko Stübner
2025-03-06 14:54 ` Jonas Karlman
2025-03-06 14:54 ` Sudeep Holla
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=24848438.6Emhk5qWAg@diego \
--to=heiko@sntech.de \
--cc=amadeus@jmu.edu.cn \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jonas@kwiboo.se \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.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).