mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrei Lalaev <andrey.lalaev@gmail.com>
To: Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	 Conor Dooley <conor+dt@kernel.org>,
	Chen Wang <chen.wang@linux.dev>,
	 Inochi Amaoto <inochiama@gmail.com>,
	Paul Walmsley <pjw@kernel.org>,
	 Palmer Dabbelt <palmer@dabbelt.com>,
	Albert Ou <aou@eecs.berkeley.edu>,
	 Alexandre Ghiti <alex@ghiti.fr>, Yao Zi <me@ziyao.cc>
Cc: devicetree@vger.kernel.org, linux-riscv@lists.infradead.org,
	 sophgo@lists.linux.dev, linux-kernel@vger.kernel.org,
	 Andrei Lalaev <andrey.lalaev@gmail.com>
Subject: [PATCH 0/2] Do not reserve memory for coprocessor FW
Date: Mon, 21 Sep 2026 17:08:58 +0200	[thread overview]
Message-ID: <20260921-sophgo-remove-coprocessor-node-v1-0-ace29446b327@gmail.com> (raw)

Milk-V Duo and Duo-256M reserve a region for coprocessor FW at
the end of RAM. It is not correct because:
  - FSBL can be configured to load FW into a different region
  - if no firmware is loaded, the reserved memory is wasted

As explained in [1, 2], FSBL should reserve the region at runtime.

The latest FSBL can boot the system without coprocessor FW:
  FSBL Jb2829:g6f8962c394dd-dirty:2026-09-20T13:04:17+00:00
  st_on_reason=d0000
  st_off_reason=0
  P2S/0x1000/0xc00fa00.
  SD/0xaa00/0x1000/0x1000/0.P2E.
  cv181x DDR init.
  ddr_param[0]=0x0.
  pkg_type=5
  D1_3_2
  DDR3-2G-QFN
  Data rate=1866.
  DDR BIST PASS
  PLLS.
  PLLE.
  C2S/0x0/0x0/0x0.
  No C906L image.
  MS/0xba00/0x80000000/0x43e00.
  SD/0xba00/0x43e00/0x43e00/0.ME.
  L2/0x4f800.
  SD/0x4f800/0x200/0x200/0.L2/0x33334c42/0xcafe4b49/0x80200000/0x8c200/0x8c200
  SD/0x4f800/0x8c200/0x8c200/0.sys_switch_all_to_pll...
  Loader_2nd loaded.
  Use internal 32k

So it is safe to remove `coprocessor_rtos` nodes.

[1]: https://lore.kernel.org/sophgo/6e4b5c98-7d48-4629-a6a0-4d930327f9a0@sifive.com/
[2]: https://lore.kernel.org/sophgo/aqrhRic7Ww6fPhxg@pie/

Signed-off-by: Andrei Lalaev <andrey.lalaev@gmail.com>
---
Andrei Lalaev (2):
      riscv: dts: sophgo: cv1800b-milkv-duo: drop reserved memory node
      riscv: dts: sophgo: sg2002-milkv-duo256m: drop reserved memory node

 arch/riscv/boot/dts/sophgo/cv1800b-milkv-duo.dts    | 11 -----------
 arch/riscv/boot/dts/sophgo/sg2002-milkv-duo256m.dts | 11 -----------
 2 files changed, 22 deletions(-)
---
base-commit: 93f51579e7df248780214094418f205253383cc5
change-id: 20260921-sophgo-remove-coprocessor-node-4e6c59ab58d2

Best regards,
--  
Andrei Lalaev <andrey.lalaev@gmail.com>


             reply	other threads:[~2026-09-21 15:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-21 15:08 Andrei Lalaev [this message]
2026-09-21 15:08 ` [PATCH 1/2] riscv: dts: sophgo: cv1800b-milkv-duo: drop reserved memory node Andrei Lalaev
2026-09-21 15:09 ` [PATCH 2/2] riscv: dts: sophgo: sg2002-milkv-duo256m: " Andrei Lalaev

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=20260921-sophgo-remove-coprocessor-node-v1-0-ace29446b327@gmail.com \
    --to=andrey.lalaev@gmail.com \
    --cc=alex@ghiti.fr \
    --cc=aou@eecs.berkeley.edu \
    --cc=chen.wang@linux.dev \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=inochiama@gmail.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=me@ziyao.cc \
    --cc=palmer@dabbelt.com \
    --cc=pjw@kernel.org \
    --cc=robh@kernel.org \
    --cc=sophgo@lists.linux.dev \
    /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®