From: Joshua Milas <josh.milas@gmail.com>
To: Inochi Amaoto <inochiama@gmail.com>
Cc: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
unicorn_wang@outlook.com, alexander.sverdlin@gmail.com,
rabenda.cn@gmail.com, thomas.bonnefille@bootlin.com,
chao.wei@sophgo.com, devicetree@vger.kernel.org,
sophgo@lists.linux.dev, josh.milas@gmail.com
Subject: Re: [PATCH 2/2] arm64: dts: sophgo: add initial Milk-V Duo S board support
Date: Thu, 2 Oct 2025 21:11:14 -0400 [thread overview]
Message-ID: <aN8isoQpdENTrxNJ@sleek> (raw)
In-Reply-To: <nkzpfylhxyqf5u3bjlokhe4udgcxohbaanhwuofjzatan3iwio@45ljfquf5sui>
Hi Inochi,
> Small suggestion: please ensure the pinctrl is correct, different
> board may require different configuration.
Is there a certain way to do that? I have been checking it against
the board schematic [1]. It shows that it is using UART0 on the
pins defined in pinctrl-sg2000.h.
Link: https://github.com/milkv-duo/duo-files/blob/main/duo-s/hardware/duo_s_SCH_v1.1.pdf
> I suggest adding all the support devices instead of a minimum one.
> Like ethernet, wifi, bluetooth.
> In the next cycle, there should be a patch for adding USB device node,
> as the driver is already merged. I also hope you can take it.
Lets do it! I tried adding the following but could not get some items working:
* emmc from 'sg2000-milkv-duo-module-01.dtsi'
* sdhci1 from 'sg2000-milkv-duo-module-01.dtsi'
* mdio
* gmac0
* dmac
* saradc
* i2c*
* spi*
I pulled the following logs of interest:
---
...
[ 0.647426] faux_driver regulatory: no of_node; not parsing pinctrl DT
...
[ 0.732380] serial8250 serial8250: no of_node; not parsing pinctrl DT
...
[ 2.418965] sophgo-cv1800-rtc cv1800b-rtc.0.auto: no of_node; not parsing pinctrl DT
[ 2.427695] alarmtimer alarmtimer.1.auto: no of_node; not parsing pinctrl DT
...
[ 2.441722] sophgo-cv1800-rtc cv1800b-rtc.0.auto: hctosys: unable to read the hardware clock
...
[ 2.525580] SPI driver fb_st7789v has no spi_device_id for sitronix,st7789v
...
[ 2.555363] faux_driver snd-soc-dummy: no of_node; not parsing pinctrl DT
...
[ 2.767235] mmc1: Failed to initialize a non-removable card
...
[ 2.900631] dw-apb-uart 4140000.serial: forbid DMA for kernel console
...
[ 13.058020] stmmaceth 4070000.ethernet: IRQ eth_wake_irq not found
[ 13.086915] stmmaceth 4070000.ethernet: IRQ eth_lpi not found
[ 13.096993] stmmaceth 4070000.ethernet: IRQ sfty not found
[ 13.105407] stmmaceth 4070000.ethernet: Hash table entries set to unexpected value 0
[ 13.115751] stmmaceth 4070000.ethernet: dt configuration failed
[ 13.127832] platform 3009800.mdio-mux: deferred probe pending: mdio-mux-mmioreg: failed to register mdio-mux bus /soc/mdio-mux@3009800
[ 13.142739] platform 4070000.ethernet: deferred probe pending: (reason unknown)
[ 13.152434] platform 4000000.i2c: deferred probe pending: (reason unknown)
[ 13.161898] platform 4010000.i2c: deferred probe pending: (reason unknown)
[ 13.171078] platform 4020000.i2c: deferred probe pending: (reason unknown)
[ 13.180353] platform 4030000.i2c: deferred probe pending: (reason unknown)
[ 13.189629] platform 4040000.i2c: deferred probe pending: (reason unknown)
[ 13.198817] platform 3020000.gpio: deferred probe pending: gpio-dwapb: Cannot get reset descriptor
[ 13.210208] platform 3021000.gpio: deferred probe pending: gpio-dwapb: Cannot get reset descriptor
[ 13.221737] platform 3022000.gpio: deferred probe pending: gpio-dwapb: Cannot get reset descriptor
[ 13.233111] platform 3023000.gpio: deferred probe pending: gpio-dwapb: Cannot get reset descriptor
[ 13.244422] platform 4150000.serial: deferred probe pending: (reason unknown)
[ 13.253971] platform 4160000.serial: deferred probe pending: (reason unknown)
[ 13.263513] platform 4170000.serial: deferred probe pending: (reason unknown)
[ 13.274037] platform 41c0000.serial: deferred probe pending: (reason unknown)
---
I believe I have the correct drivers enabled for everything. I'm figuring there
is some pinctrl configuration ('PIN_ETH_*'?) I have to add to the device tree
but unsure what it would look like.
Thanks for the feedback,
- Joshua Milas
next prev parent reply other threads:[~2025-10-03 1:11 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-27 17:36 [PATCH 0/2] Add initial Milk-V Duo S board support Joshua Milas
2025-09-27 17:36 ` [PATCH 1/2] dt-bindings: soc: sophgo: add Milk-V Duo S board compatibles Joshua Milas
2025-09-28 4:09 ` E Shattow
2025-09-27 17:36 ` [PATCH 2/2] arm64: dts: sophgo: add initial Milk-V Duo S board support Joshua Milas
2025-09-28 4:09 ` E Shattow
2025-09-28 10:20 ` Alexander Sverdlin
2025-10-03 1:34 ` Joshua Milas
2025-09-29 23:45 ` Inochi Amaoto
2025-09-29 23:54 ` Inochi Amaoto
2025-09-30 5:03 ` Alexander Sverdlin
2025-10-01 6:46 ` Inochi Amaoto
2025-10-09 1:52 ` Joshua Milas
2025-10-11 6:14 ` Alexander Sverdlin
2025-10-03 1:11 ` Joshua Milas [this message]
2025-10-05 3:39 ` Inochi Amaoto
2025-10-09 1:58 ` Joshua Milas
2025-10-05 12:07 ` Inochi Amaoto
2025-09-29 2:14 ` [PATCH 0/2] Add " Rob Herring (Arm)
2025-09-29 6:41 ` Chen Wang
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=aN8isoQpdENTrxNJ@sleek \
--to=josh.milas@gmail.com \
--cc=alexander.sverdlin@gmail.com \
--cc=chao.wei@sophgo.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=inochiama@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=rabenda.cn@gmail.com \
--cc=robh@kernel.org \
--cc=sophgo@lists.linux.dev \
--cc=thomas.bonnefille@bootlin.com \
--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;
as well as URLs for NNTP newsgroup(s).