All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Zhuxu Ran" <zhuxu_ran@zohomail.com>
To: "Hiago De Franco" <hfranco@baylibre.com>,
	"Zhuxu Ran" <zhuxu_ran@zohomail.com>
Cc: <u-boot@lists.u-boot-project.org>,
	"Chao Wei" <chao.wei@sophgo.com>,
	"Chen Wang" <unicorn_wang@outlook.com>, "Yao Zi" <me@ziyao.cc>,
	"Lukasz Majewski" <lukma@denx.de>,
	"Tom Rini" <trini@konsulko.com>, "Peng Fan" <peng.fan@nxp.com>,
	"Jaehoon Chung" <jh80.chung@samsung.com>,
	"Stefan Roese" <stefan.roese@mailbox.org>,
	"Sumit Garg" <sumit.garg@kernel.org>,
	"Inochi Amaoto" <inochiama@gmail.com>,
	"Conor Dooley" <conor.dooley@microchip.com>,
	"Chen-Yu Yeh" <chenyou910331@gmail.com>,
	"Chen Wang" <chen.wang@linux.dev>,
	"Kongyang Liu" <seashell11234455@gmail.com>,
	"Leo Liang" <leo.liang@sifive.com>,
	"Thomas Bonnefille" <thomas.bonnefille@bootlin.com>,
	"Quentin Schulz" <quentin.schulz@cherry.de>,
	"Johan Jonker" <jbx6244@gmail.com>,
	"Casey Connolly" <casey.connolly@linaro.org>,
	"Varadarajan Narayanan" <varadarajan.narayanan@oss.qualcomm.com>,
	"Alexander Koch" <akoch@initse.com>,
	"Andreas Schwab" <schwab@suse.de>,
	"Junhui Liu" <junhui.liu@pigmoral.tech>,
	"Marek Vasut" <marex@nabladev.com>,
	"Sumit Garg" <sumit.garg@oss.qualcomm.com>,
	"Peter Robinson" <pbrobinson@gmail.com>,
	"Ilias Apalodimas" <ilias.apalodimas@linaro.org>
Subject: Re: [PATCH v4 08/11] riscv: milkv_duo_256m: Use upstream devicetree
Date: Thu, 24 Sep 2026 22:47:32 +0800	[thread overview]
Message-ID: <DLNMNDIIOCZK.3VA1P2AAK5ACA@zohomail.com> (raw)
In-Reply-To: <arUZwbtnDO9g3cUZ@hiagonb>

> I see that milkv_duo_256m_defconfig doesn't enable DM_MDIO, DM_MDIO_MUX
> or MDIO_MUX_MMIOREG, so nothing binds to the mdio-mux node.
>
> Note that the upstream gmac0 node uses phy-mode = "internal" and a
> phy-handle into the mdio mux, while the old local DT used phy-mode =
> "rmii".
>
> Can you check this? Have you tested the ethernet port on Duo 256M?

Hi Hiago,

Thanks for catching this. You are right that the upstream devicetree
requires the DM MDIO mux support.

My earlier Ethernet test passed, but the mdio-mux node was not bound,
so it did not verify the MDIO topology described by the upstream
devicetree.

After enabling CONFIG_DM_MDIO, CONFIG_DM_MDIO_MUX, and
CONFIG_MDIO_MUX_MMIOREG, the MMIO mux, the internal MDIO bus, and the
DesignWare MDIO bus are all probed. I tested this on the Milk-V Duo 256M
after a cold boot; the link negotiated at 100 Mbps full duplex, and both
DHCP and TFTP worked.

I will add these options to milkv_duo_256m_defconfig in the next revision.

-- 
Best regards,
Zhuxu Ran


  reply	other threads:[~2026-09-24 17:45 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20260922-milkv-duo-upstream-dts-v4-0-d45b74dfad36@zohomail.com>
2026-09-22 14:59 ` [PATCH v4 01/11] clk: sophgo: cv1800b: Add SoC-specific compatible strings Zhuxu Ran
2026-09-22 14:59 ` [PATCH v4 02/11] mmc: cv1800b: Add SG2002 compatible string Zhuxu Ran
2026-09-22 14:59 ` [PATCH v4 03/11] dt-bindings: soc: sophgo: add Milk-V Duo 256M board Zhuxu Ran
2026-09-22 14:59 ` [PATCH v4 04/11] riscv: dts: sophgo: cv180x: Add PWR_GPIO controller Zhuxu Ran
2026-09-22 14:59 ` [PATCH v4 05/11] riscv: dts: sophgo: Add Milk-V Duo 256M board support Zhuxu Ran
2026-09-22 14:59 ` [PATCH v4 06/11] riscv: milkv_duo: Use upstream devicetree Zhuxu Ran
2026-09-22 15:46 ` [PATCH v4 07/11] riscv: licheerv_nano: " Zhuxu Ran
2026-09-22 15:46 ` [PATCH v4 08/11] riscv: milkv_duo_256m: " Zhuxu Ran
2026-09-24 12:45   ` Hiago De Franco
2026-09-24 14:47     ` Zhuxu Ran [this message]
2026-09-22 15:46 ` [PATCH v4 09/11] rtc: cv1800: Add RTC and system reset support Zhuxu Ran
2026-09-23 17:51   ` Yao Zi
2026-09-24  4:05     ` Zhuxu Ran
2026-09-22 15:46 ` [PATCH v4 10/11] riscv: dts: sophgo: Drop local CV18xx devicetrees Zhuxu Ran
2026-09-22 15:46 ` [PATCH v4 11/11] clk: sophgo: cv1800b: Drop legacy compatible string Zhuxu Ran

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=DLNMNDIIOCZK.3VA1P2AAK5ACA@zohomail.com \
    --to=zhuxu_ran@zohomail.com \
    --cc=akoch@initse.com \
    --cc=casey.connolly@linaro.org \
    --cc=chao.wei@sophgo.com \
    --cc=chen.wang@linux.dev \
    --cc=chenyou910331@gmail.com \
    --cc=conor.dooley@microchip.com \
    --cc=hfranco@baylibre.com \
    --cc=ilias.apalodimas@linaro.org \
    --cc=inochiama@gmail.com \
    --cc=jbx6244@gmail.com \
    --cc=jh80.chung@samsung.com \
    --cc=junhui.liu@pigmoral.tech \
    --cc=leo.liang@sifive.com \
    --cc=lukma@denx.de \
    --cc=marex@nabladev.com \
    --cc=me@ziyao.cc \
    --cc=pbrobinson@gmail.com \
    --cc=peng.fan@nxp.com \
    --cc=quentin.schulz@cherry.de \
    --cc=schwab@suse.de \
    --cc=seashell11234455@gmail.com \
    --cc=stefan.roese@mailbox.org \
    --cc=sumit.garg@kernel.org \
    --cc=sumit.garg@oss.qualcomm.com \
    --cc=thomas.bonnefille@bootlin.com \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.u-boot-project.org \
    --cc=unicorn_wang@outlook.com \
    --cc=varadarajan.narayanan@oss.qualcomm.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 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.