Re: [PATCH 2/2] arm64: dts: sophgo: add initial Milk-V Duo S board support

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