Re: Re: Re: [PATCH net-next v9 6/6] riscv: dts: eswin: eic7700-hifive-premier-p550: enable Ethernet controller

[李志 <lizhi2@eswincomputing.com>]

> -----Original Messages-----
> From: "Andrew Lunn" <andrew@lunn.ch>
> Send time:Thursday, 02/07/2026 21:22:34
> To: 李志 <lizhi2@eswincomputing.com>
> Cc: sashiko-reviews@lists.linux.dev, conor+dt@kernel.org, robh@kernel.org, devicetree@vger.kernel.org, "Min Lin" <linmin@eswincomputing.com>
> Subject: Re: Re: [PATCH net-next v9 6/6] riscv: dts: eswin: eic7700-hifive-premier-p550: enable Ethernet controller
> 
> > Hi Andrew,
> > 
> > One question before I prepare the next revision.
> > 
> > As discussed previously, the DTS patch was included only to provide the overall
> > Ethernet design context during the review of the binding and driver patches:
> > 
> > https://lore.kernel.org/lkml/64bf6b40-b947-4ffa-8d48-4d6341931327@lunn.ch/
> > 
> > For the next revision, would it be acceptable to drop the DTS patch from this
> > series and post only the binding and driver patches? The complete DTS
> > enablement is planned to be submitted later as a separate series after the
> > binding and driver have been merged.
> 
> What normally happens is that I give an Acked-by: or a Reviewed-by:
> for the DT patch, and you submit it for merging via the DT Maintainer.
> Everything then meets up in linux-next.
> 
> Why do you need to do this later? Why not now?
> 

There is an another seperate DT patch series
[https://lore.kernel.org/all/20260615122016.1110206-1-pinkesh.vaghela@einfochips.com/]
which is under review.
It also introduces DT nodes for reset, clock, pinctrl, HSP power domain.

Therefore, our planned steps are as follows:
1. In the next net-next v10​ patch series, drop the DTS patches, and submit only
   the bindings and driver.
2. Wait for Pinkesh’s DT patch series​ to be merged.
3. Once the HSPCRG patch series​
   [https://lore.kernel.org/all/20260605060730.1605-1-dongxuyang@eswincomputing.com/]
   is merged, submit a new DT patch series​ to extend ESWIN EIC7700 SoC support​
   for all HSP modules—including USB, eMMC, SD, and Ethernet, since they are all
   under the HSP bus node eventhough ethernet doese not depend on HSPCRG patch.