From: Leo Liang <ycliang@andestech.com>
To: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
Cc: Aurelien Jarno <aurelien@aurel32.net>,
Minda Chen <minda.chen@starfivetech.com>,
Rick Chen <rick@andestech.com>,
Lukasz Tekieli <tekieli.lukasz@gmail.com>,
Shiji Yang <yangshiji66@outlook.com>,
Shengyu Qu <wiagn233@outlook.com>,
Seung-Woo Kim <sw0312.kim@samsung.com>,
E Shattow <lucent@gmail.com>, <u-boot@lists.denx.de>,
Hal Feng <hal.feng@starfivetech.com>
Subject: Re: [PATCH v2 4/6] board: starfive: support Milk-V Mars board
Date: Thu, 28 Mar 2024 14:24:14 +0800 [thread overview]
Message-ID: <ZgUNDpJnA4eUB2Sf@swlinux02> (raw)
In-Reply-To: <5e0b3ac7-819a-4d34-abc9-083caef0b5cb@canonical.com>
Hi Heinrich,
On Wed, Mar 27, 2024 at 12:03:01PM +0100, Heinrich Schuchardt wrote:
> [EXTERNAL MAIL]
>
> On 24.03.24 16:00, Aurelien Jarno wrote:
> > On 2024-03-21 19:11, Heinrich Schuchardt wrote:
> > > The differences between the Milk-V Mars board and the VisionFive 2 board
> > > are small enough that we can support both using the same U-Boot build.
> > >
> > > * The model and compatible property are taken from proposed Linux patches.
> > > * The EEPROM is atmel,24c02 according to the vendor U-Boot.
> > > * The second Ethernet port is not available.
> >
> > From the device tree that have been submitted to the kernel [1] it seems
> > another difference is that there is a CD gpio for mmc1.
>
> Yes, the Mars board has
>
> cd-gpios = <&sysgpio 41 GPIO_ACTIVE_LOW>;
>
> while the VisionFive 2 has
>
> broken-cd;
>
> We could add the cd-gpios to the VF2 dts and then set broken-cd in
> spl_fdt_fixup_*().
>
> What I would really like to understand from the reviewers is if the
> approach with patching the device-tree is what we are targeting for.
>
> Or should we try to keep the device-trees in sync with Linux, package
> all JH7110 device-trees into the FIT image and in SPL choose the
> device-tree from the fit image and only patch the memory size.
>
> The device-tree for the Milk-V CM module differs a lot in GPIO routing.
> I am not sure that patching the VF2 device-tree is future proof.
I think we could patch the VF2 device-tree currently with this few differeces,
and create a new device tree for Milk-V Mars CM module if patching the VF2 device tree
is too much of an effort.
Does this sound reasonable ?
Do you have any preference over which scheme we should use ?
Best regards,
Leo
>
> Best regards
>
> Heinrich
>
>
> >
> > From the schematics, it also seems that the usb0 port is not in
> > peripheral mode, but in host mode. That said on the submitted kernel
> > device tree it seems simply disabled.
> >
> > Aurelien
> >
> > [1] https://lore.kernel.org/linux-kernel/20240131132600.4067-2-jszhang@kernel.org/T/
> >
>
next prev parent reply other threads:[~2024-03-28 6:24 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-21 18:11 [PATCH v2 0/6] riscv: add support for Milk-V Mars board Heinrich Schuchardt
2024-03-21 18:11 ` [PATCH v2 1/6] riscv: do not set default fdt for VisionFive 2 Heinrich Schuchardt
2024-03-27 9:01 ` Leo Liang
2024-03-21 18:11 ` [PATCH v2 2/6] eeprom: starfive: function get_product_id_from_eeprom() Heinrich Schuchardt
2024-03-27 9:13 ` Leo Liang
2024-03-21 18:11 ` [PATCH v2 3/6] riscv: set fdtfile on Milk-V Mars Heinrich Schuchardt
2024-03-28 3:35 ` Leo Liang
2024-03-21 18:11 ` [PATCH v2 4/6] board: starfive: support Milk-V Mars board Heinrich Schuchardt
2024-03-24 15:00 ` Aurelien Jarno
2024-03-27 11:03 ` Heinrich Schuchardt
2024-03-28 6:24 ` Leo Liang [this message]
2024-03-28 16:01 ` Heinrich Schuchardt
2024-04-01 15:28 ` Aurelien Jarno
2024-04-01 15:54 ` Heinrich Schuchardt
2024-04-02 1:19 ` Minda Chen
2024-03-28 5:24 ` Leo Liang
2024-03-21 18:11 ` [PATCH v2 5/6] riscv: starfive: avoid including common.h Heinrich Schuchardt
2024-03-28 3:09 ` Leo Liang
2024-03-21 18:11 ` [PATCH v2 6/6] doc: describe Milk-V Mars board Heinrich Schuchardt
2024-03-25 3:10 ` 回复: [PATCH v2 0/6] riscv: add support for " Minda Chen
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=ZgUNDpJnA4eUB2Sf@swlinux02 \
--to=ycliang@andestech.com \
--cc=aurelien@aurel32.net \
--cc=hal.feng@starfivetech.com \
--cc=heinrich.schuchardt@canonical.com \
--cc=lucent@gmail.com \
--cc=minda.chen@starfivetech.com \
--cc=rick@andestech.com \
--cc=sw0312.kim@samsung.com \
--cc=tekieli.lukasz@gmail.com \
--cc=u-boot@lists.denx.de \
--cc=wiagn233@outlook.com \
--cc=yangshiji66@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