From: Michael Opdenacker <michael.opdenacker@bootlin.com>
To: Jisheng Zhang <jszhang@kernel.org>,
Inochi Amaoto <inochiama@outlook.com>
Cc: michael.opdenacker@bootlin.com, Conor Dooley <conor@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Chen Wang <unicorn_wang@outlook.com>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
devicetree@vger.kernel.org, linux-riscv@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] riscv: dts: sophgo: add initial Milk-V Duo S board device tree
Date: Thu, 11 Apr 2024 10:35:55 +0200 [thread overview]
Message-ID: <5fdda638-21ba-4fa7-b666-33cf2fd69dda@bootlin.com> (raw)
In-Reply-To: <ZhZo0iJFSn1te-6d@xhacker>
Hi Jisheng,
On 4/10/24 at 12:24, Jisheng Zhang wrote:
> setting the correct bus-width is necessary for better performance
> no-1-8-v can be removed, but it doesn't harm anything because
> the board doesn't supply 1.8v
>
> no-mmc and no-sdio to make the probe a bit quicker
Many thanks for your advice!
However, whether I apply these changes or not,
git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git is now broken
for me:
Error: arch/riscv/boot/dts/sophgo/sg2000-milkv-duos.dts:32.1-8 Label or
path sdhci0 not found
I was previously testing with linux-next, but it's now broken too,
though in a different way:
[ 1.306811] /dev/root: Can't open blockdev
[ 1.311200] VFS: Cannot open root device "/dev/mmcblk0p2" or
unknown-block(0,0): error -6
Shall I submit my updates anyway?
Cheers
Michael.
--
Michael Opdenacker, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2024-04-11 8:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-09 6:45 [PATCH] riscv: dts: sophgo: add initial Milk-V Duo S board device tree michael.opdenacker
2024-04-09 7:17 ` Inochi Amaoto
2024-04-09 7:52 ` Michael Opdenacker
2024-04-09 12:13 ` Conor Dooley
2024-04-09 12:27 ` Inochi Amaoto
2024-04-09 12:30 ` Inochi Amaoto
2024-04-09 13:08 ` Michael Opdenacker
2024-04-10 1:24 ` Inochi Amaoto
2024-04-10 10:24 ` Jisheng Zhang
2024-04-11 8:35 ` Michael Opdenacker [this message]
2024-04-11 16:14 ` Conor Dooley
2024-04-09 9:47 ` Krzysztof Kozlowski
2024-04-09 13:38 ` Rob Herring
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=5fdda638-21ba-4fa7-b666-33cf2fd69dda@bootlin.com \
--to=michael.opdenacker@bootlin.com \
--cc=aou@eecs.berkeley.edu \
--cc=conor+dt@kernel.org \
--cc=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=inochiama@outlook.com \
--cc=jszhang@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=robh@kernel.org \
--cc=unicorn_wang@outlook.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