Message ID | 20241103-th1520-gmac-v7-0-ef094a30169c@tenstorrent.com (mailing list archive) |
---|---|
Headers | show |
Series | Add the dwmac driver support for T-HEAD TH1520 SoC | expand |
On Sun, Nov 03, 2024 at 08:57:58AM -0800, Drew Fustini wrote: > This series adds support for dwmac gigabit ethernet in the T-Head TH1520 > RISC-V SoC used on boards like BeagleV Ahead and the LicheePi 4A. > > The gigabit ethernet on these boards does need pinctrl support to mux > the necessary pads. The pinctrl-th1520 driver, pinctrl binding, and > related dts patches are in linux-next. However, they are not yet in > net-next/main. > > Therefore, I am dropping the dts patch for v5 as it will not build on > net-next/main due to the lack of the padctrl0_apsys pin controller node > in next-next/main version th1520.dtsi. You should send the .dts patch to the Maintainer responsible for merging all the RISC-V DT patches, maybe via a sub Maintainer. All the different parts will then meet up in linux-next. Andrew
On Sun, Nov 03, 2024 at 07:12:24PM +0100, Andrew Lunn wrote: > On Sun, Nov 03, 2024 at 08:57:58AM -0800, Drew Fustini wrote: > > This series adds support for dwmac gigabit ethernet in the T-Head TH1520 > > RISC-V SoC used on boards like BeagleV Ahead and the LicheePi 4A. > > > > The gigabit ethernet on these boards does need pinctrl support to mux > > the necessary pads. The pinctrl-th1520 driver, pinctrl binding, and > > related dts patches are in linux-next. However, they are not yet in > > net-next/main. > > > > Therefore, I am dropping the dts patch for v5 as it will not build on > > net-next/main due to the lack of the padctrl0_apsys pin controller node > > in next-next/main version th1520.dtsi. > > You should send the .dts patch to the Maintainer responsible for > merging all the RISC-V DT patches, maybe via a sub Maintainer. All the > different parts will then meet up in linux-next. > > Andrew I am the maintainer for arch/riscv/boot/dts/thead. I'm planning to apply the dts patch to my for-next branch once this series with the binding and driver are applied to net-next. Thanks, Drew