[GIT PULL] RISC-V Sophgo Devicetrees for v6.17 (v2)

Chen Wang unicorn_wang at outlook.com
Tue Jul 22 19:25:55 PDT 2025


On 2025/7/23 4:17, Arnd Bergmann wrote:
> On Wed, Jul 16, 2025, at 02:31, Chen Wang wrote:
>> Hey Arnd,
>>
>> Please pull this dt changes for RISC-V/Sophgo. This PR is the
>> replacement of the old one [1].
>>
> Hi Chen,
>
> I just tried to pull this but still see a few issues that I hope
> you can improve first:
>
>> The following changes since commit 347e9f5043c89695b01e66b3ed111755afcf1911:
>>
>>     Linux 6.16-rc6 (2025-07-13 14:25:58 -0700)
>>
>> are available in the Git repository at:
>>
>>     https://github.com/sophgo/linux.git tags/riscv-sophgo-dt-for-v6.17
> You have based the branch on linux-6.16-rc6, but my own branch is
> based on -rc3, so pulling this introduces a backmerge of hundreds
> of upstream commits, which I would like to avoid.
>
> Please rebase on top of -rc1 if possible.
>
>> ----------------------------------------------------------------
>> RISC-V Devicetrees for v6.17
>>
>> Sophgo:
>>
>> For CV18xx serials:
>> - Add rtcsys device node.
>> - Add reset device node.
>> - Add ethernet device node.
>> - Add support for Duo Module 01 Evaluation Board.
>>     This board uses SG2000(old codename CV181xH),
>>     which is dual-arch, RISC-V and ARM64. This
>>     patch add the support for ARM64.
>> - Enable ethernet device for Huashan Pi.
>> - Remove warning for mdio node.
> For the commit log, I don't like lists that simply repeat
> the one-line messages from the shortlog. You can leave this
> part for now if it takes too long to rewrite, but next time
> try to write full sentences describing the contents overall
> as you did with the Duo Module, but don't list each
> added device node separately.
>
>> ----------------------------------------------------------------
>> Alexander Sverdlin (7):
>>         riscv: dts: sophgo: cv18xx: Add RTCSYS device node
>>         dt-bindings: soc: sophgo: Move SoCs/boards from riscv into soc,
>> add SG2000
>>         arm64: dts: sophgo: Add initial SG2000 SoC device tree
>>         arm64: dts: sophgo: Add Duo Module 01
>>         arm64: dts: sophgo: Add Duo Module 01 Evaluation Board
>>         arm64: Add SOPHGO SOC family Kconfig support
>>         arm64: defconfig: Enable rudimentary Sophgo SG2000 support
> It's ok to mix riscv and arm64 commits in one branch, but the SG2000
> series from Alexander should really be a separate branch. The way
> I organize the soc tree, I have one branch for dts (and binding)
> changes on existing SoCs, but separate branches for defconfig changes,
> drivers/{soc,firmware,reset,...} etc.
>
> Since the arm64 contents touch both Kconfig and defconfig files,
> I would like to see them in one branch that combines the sg2000
> dts/defconfig/Kconfig changes and their prerequisites, so I
> can add that to my special "newsoc" branch that contains similar
> commits for the newly added pxa1908, cix-p1 and andes-qilai SoCs.
>
>        Arnd

Hi, Arnd,

According to your request, I have rebuilt two branches for PR (temporary):
https://github.com/sophgo/linux/tree/temp-riscv-sophgo-dt-for-next
https://github.com/sophgo/linux/tree/temp-arm-sophgo-dt-for-next

Please check whether it meets your requirements. Both branches are based 
on v6.16-rc1. If there is no problem, I will submit PRs using these two 
branches respectively.

It should be noted that about the commit "610f943a66be dt-bindings: soc: 
sophgo: Move SoCs/boards from riscv into soc, add SG2000" on 
temp-riscv-sophgo-dt-for-next. This change was originally made for 
SG2000/ARM, moving sophgo.yaml from the riscv directory to soc/sophgo 
for sharing between riscv and arm. Because this file will also be 
involved in subsequent changes for riscv, I placed it in 
temp-riscv-sophgo-dt-for-next.

Regards,

Chen





More information about the linux-riscv mailing list