From: Chen Wang <unicorn_wang@outlook.com>
To: Conor Dooley <conor@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: Jisheng Zhang <jszhang@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Marc Zyngier <maz@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Palmer Dabbelt <palmer@dabbelt.com>,
Paul Walmsley <paul.walmsley@sifive.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Anup Patel <anup@brainfault.org>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-riscv@lists.infradead.org,
Inochi Amaoto <inochiama@outlook.com>,
chao.wei@sophgo.com, xiaoguang.xing@sophgo.com
Subject: Re: [PATCH 4/5] riscv: dts: sophgo: add initial CV1800B SoC device tree
Date: Wed, 4 Oct 2023 19:43:29 +0800 [thread overview]
Message-ID: <MA0P287MB0332BD2EFF6C43DC154EB03BFECBA@MA0P287MB0332.INDP287.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <20231004-caregiver-deserve-71849c94dcfb@spud>
在 2023/10/4 17:13, Conor Dooley 写道:
> On Wed, Oct 04, 2023 at 09:57:33AM +0200, Krzysztof Kozlowski wrote:
>> On 04/10/2023 09:23, Chen Wang wrote:
>>> 在 2023/9/30 20:39, Jisheng Zhang 写道:
>>>> Add initial device tree for the CV1800B RISC-V SoC by SOPHGO.
>>>>
>>>> Signed-off-by: Jisheng Zhang <jszhang@kernel.org>
>>>> ---
>>>> arch/riscv/boot/dts/sophgo/cv1800b.dtsi | 117 ++++++++++++++++++++++++
>>>> 1 file changed, 117 insertions(+)
>>>> create mode 100644 arch/riscv/boot/dts/sophgo/cv1800b.dtsi
>>> Hi, Jisheng, as far as I know, sg2042 and cv180x are now tracked by
>>> different people and even in sophgo, they are two independent
>>> projects(sg2042 is target for HPC and cv180x is target for embeded
>>> device). To facilitate future management and review, I recommend
>>> registering the maintainer information in two entries in MAINTAINERS.
>>> The example is as follows:
>>>
>>> ```
>>>
>>> SOPHGO CV180X DEVICETREES
>>> M: Jisheng Zhang <jszhang@kernel.org>
>>> F: arch/riscv/boot/dts/sophgo/cv1800b-milkv-duo.dts
>>> F: arch/riscv/boot/dts/sophgo/cv1800b.dtsi
>>>
>>> SOPHGO SG2042 DEVICETREES
>>> M: Chao Wei <chao.wei@sophgo.com>
>>> M: Chen Wang <unicornxw@gmail.com>
>>> S: Maintained
>>> F: arch/riscv/boot/dts/sophgo/Makefile
>>> F: arch/riscv/boot/dts/sophgo/sg2042-cpus.dtsi
>>> F: arch/riscv/boot/dts/sophgo/sg2042-milkv-pioneer.dts
>>> F: arch/riscv/boot/dts/sophgo/sg2042.dtsi
>>> F: Documentation/devicetree/bindings/riscv/sophgo.yaml
>>> ```
>>>
>>> For Makefile and sophgo.yaml such common files, just keep in sg2042
>>> entry should be fine.
>>>
>>> @Conor, what do you think?
>> We do no have usually per-board maintainer entries (with few
>> exceptions). I strongly prefer this one instead:
>>
>> https://lore.kernel.org/all/829b122da52482707b783dc3d93d3ff0179cb0ca.camel@perches.com/
> I don't like the suggestion here for a different reason! While I'm fine
> with having some per-board SoC maintainers, esp. since the cv1800 stuff
> is very different to the sg2042, I want to see someone step up to apply
> the patches for the whole arch/riscv/boot/dts/sophgo/ directory once more
> comfortable with the process, not reduce the entry to cover just the 64
> core SoC.
>
> Thanks,
> Conor.
Thanks, Conor and Krzystof. Agree with you, it would be better to keep
only one entry for arch/riscv/boot/dts/sophgo/ directory. I will discuss
with other people working on sophgo and specify a unified maintenance
task to maintain files under it.
next prev parent reply other threads:[~2023-10-04 11:43 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-30 12:39 [PATCH 0/5] Add Milk-V Duo board support Jisheng Zhang
2023-09-30 12:39 ` [PATCH 1/5] dt-bindings: interrupt-controller: Add SOPHGO CV1800B plic Jisheng Zhang
2023-10-01 11:25 ` Conor Dooley
2023-09-30 12:39 ` [PATCH 2/5] dt-bindings: timer: Add SOPHGO CV1800B clint Jisheng Zhang
2023-10-01 11:25 ` Conor Dooley
2023-09-30 12:39 ` [PATCH 3/5] dt-bindings: riscv: Add Milk-V Duo board compatibles Jisheng Zhang
2023-10-01 11:26 ` Conor Dooley
2023-10-04 6:40 ` Chen Wang
2023-09-30 12:39 ` [PATCH 4/5] riscv: dts: sophgo: add initial CV1800B SoC device tree Jisheng Zhang
2023-09-30 22:34 ` Inochi Amaoto
2023-10-01 11:34 ` Conor Dooley
2023-10-01 12:19 ` Inochi Amaoto
2023-10-01 12:22 ` Inochi Amaoto
2023-10-02 12:11 ` Conor Dooley
2023-10-02 12:09 ` Conor Dooley
2023-10-06 12:21 ` Jisheng Zhang
2023-10-02 12:19 ` Conor Dooley
2023-10-04 7:23 ` Chen Wang
2023-10-04 7:57 ` Krzysztof Kozlowski
2023-10-04 9:13 ` Conor Dooley
2023-10-04 11:43 ` Chen Wang [this message]
2023-09-30 12:39 ` [PATCH 5/5] riscv: dts: sophgo: add Milk-V Duo board " Jisheng Zhang
2023-10-04 6:50 ` Chen Wang
2023-09-30 14:18 ` [PATCH 0/5] Add Milk-V Duo board support Chen Wang
2023-10-02 12:10 ` Conor Dooley
2023-10-02 12:22 ` Conor Dooley
2023-10-03 2:32 ` Chen Wang
2023-10-03 7:56 ` Conor Dooley
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=MA0P287MB0332BD2EFF6C43DC154EB03BFECBA@MA0P287MB0332.INDP287.PROD.OUTLOOK.COM \
--to=unicorn_wang@outlook.com \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=chao.wei@sophgo.com \
--cc=conor+dt@kernel.org \
--cc=conor@kernel.org \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=inochiama@outlook.com \
--cc=jszhang@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=maz@kernel.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=robh+dt@kernel.org \
--cc=tglx@linutronix.de \
--cc=xiaoguang.xing@sophgo.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
all inboxes | Powered by JetHome®