All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Heiko Stübner" <heiko@sntech.de>
To: Chukun Pan <amadeus@jmu.edu.cn>, Krzysztof Kozlowski <krzk@kernel.org>
Cc: 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,
	robh@kernel.org, ziyao@disroot.org
Subject: Re: [PATCH 1/1] arm64: dts: rockchip: enable SCMI clk for RK3528 SoC
Date: Thu, 06 Mar 2025 14:57:00 +0100	[thread overview]
Message-ID: <3008437.usQuhbGJ8B@diego> (raw)
In-Reply-To: <b57e0930-c9a3-4c44-a740-a5623d6904ba@kernel.org>

Am Donnerstag, 6. März 2025, 14:54:04 MEZ schrieb Krzysztof Kozlowski:
> On 06/03/2025 14:51, Heiko Stübner wrote:
> > Am Donnerstag, 6. März 2025, 14:40:02 MEZ schrieb Chukun Pan:
> >> Hi,
> >>
> >>> That sram is part of the soc (and has an mmio-address), so I'd think
> >>> it should live inside the soc node?
> >>
> >> But soc ranges starts from 0xfe000000, I don't know whether to change it.
> >> And all other nodes are 0xf..., except this sram.
> >> Any suggestions would be greatly appreciated.
> > 
> > darn ... I didn't realize that this is not sram, but main memory :-)
> 
> 
> Heh, I think carving out reserved blocks from the main RAM and calling
> it a SRAM is a stretch.

yep, hence going with the reserved memory instead
and not trying to call it sram :-)

And I just saw rk3576 has the same issue, only that there
the mmio area is sitting before the main memory address space




WARNING: multiple messages have this Message-ID (diff)
From: "Heiko Stübner" <heiko@sntech.de>
To: Chukun Pan <amadeus@jmu.edu.cn>, Krzysztof Kozlowski <krzk@kernel.org>
Cc: 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,
	robh@kernel.org, ziyao@disroot.org
Subject: Re: [PATCH 1/1] arm64: dts: rockchip: enable SCMI clk for RK3528 SoC
Date: Thu, 06 Mar 2025 14:57:00 +0100	[thread overview]
Message-ID: <3008437.usQuhbGJ8B@diego> (raw)
In-Reply-To: <b57e0930-c9a3-4c44-a740-a5623d6904ba@kernel.org>

Am Donnerstag, 6. März 2025, 14:54:04 MEZ schrieb Krzysztof Kozlowski:
> On 06/03/2025 14:51, Heiko Stübner wrote:
> > Am Donnerstag, 6. März 2025, 14:40:02 MEZ schrieb Chukun Pan:
> >> Hi,
> >>
> >>> That sram is part of the soc (and has an mmio-address), so I'd think
> >>> it should live inside the soc node?
> >>
> >> But soc ranges starts from 0xfe000000, I don't know whether to change it.
> >> And all other nodes are 0xf..., except this sram.
> >> Any suggestions would be greatly appreciated.
> > 
> > darn ... I didn't realize that this is not sram, but main memory :-)
> 
> 
> Heh, I think carving out reserved blocks from the main RAM and calling
> it a SRAM is a stretch.

yep, hence going with the reserved memory instead
and not trying to call it sram :-)

And I just saw rk3576 has the same issue, only that there
the mmio area is sitting before the main memory address space



_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip

  reply	other threads:[~2025-03-06 14:05 UTC|newest]

Thread overview: 26+ 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 ` Chukun Pan
2025-03-06 13:10 ` [PATCH 1/1] " Chukun Pan
2025-03-06 13:10   ` Chukun Pan
2025-03-06 13:29   ` Heiko Stübner
2025-03-06 13:29     ` Heiko Stübner
2025-03-06 13:40     ` Chukun Pan
2025-03-06 13:40       ` Chukun Pan
2025-03-06 13:45       ` Krzysztof Kozlowski
2025-03-06 13:45         ` Krzysztof Kozlowski
2025-03-06 14:20         ` Chukun Pan
2025-03-06 14:20           ` Chukun Pan
2025-03-06 14:25           ` Heiko Stübner
2025-03-06 14:25             ` Heiko Stübner
2025-03-06 14:50             ` Chukun Pan
2025-03-06 14:50               ` Chukun Pan
2025-03-06 13:51       ` Heiko Stübner
2025-03-06 13:51         ` Heiko Stübner
2025-03-06 13:54         ` Krzysztof Kozlowski
2025-03-06 13:54           ` Krzysztof Kozlowski
2025-03-06 13:57           ` Heiko Stübner [this message]
2025-03-06 13:57             ` Heiko Stübner
2025-03-06 14:54   ` Jonas Karlman
2025-03-06 14:54     ` Jonas Karlman
2025-03-06 14:54   ` Sudeep Holla
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=3008437.usQuhbGJ8B@diego \
    --to=heiko@sntech.de \
    --cc=amadeus@jmu.edu.cn \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --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 \
    --cc=robh@kernel.org \
    --cc=ziyao@disroot.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.