From: Conor Dooley <conor@kernel.org>
To: Chen Wang <unicorn_wang@outlook.com>
Cc: Inochi Amaoto <inochiama@outlook.com>,
Chao Wei <chao.wei@sophgo.com>,
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>,
Conor Dooley <conor.dooley@microchip.com>,
Jisheng Zhang <jszhang@kernel.org>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-riscv@lists.infradead.org
Subject: Re: [PATCH v4 0/7] Add Huashan Pi board support
Date: Sun, 3 Dec 2023 11:51:32 +0000 [thread overview]
Message-ID: <20231203-parabola-deploy-105940119261@spud> (raw)
In-Reply-To: <MA0P287MB033290A6C8B15202E31E43CCFE80A@MA0P287MB0332.INDP287.PROD.OUTLOOK.COM>
[-- Attachment #1: Type: text/plain, Size: 1342 bytes --]
On Sat, Dec 02, 2023 at 09:11:38AM +0800, Chen Wang wrote:
> As far as I know, sophgo's SoC product names all start with "sg", while
> products starting with "cv" come from CVITEK (another chip company). CVITEK
> was acquired by sophgo a year ago, so now many SOC product names that
> originally started with "cv" are being repackaged and changed to start with
> "sg".
>
> For the cv1800b adopted by Duo, Sophgo has made it clear that it will not
> change its codename.
>
> But I heard that for other products, such as the cv1812h used by Huashanpi,
> sophgo may change their names in the future, but sophgo has not officially
> confirmed it yet. Looks like sophgo themselves are still in the process of
> digesting cv's products, ;)
>
> Since we have just started to support cv1812h and have not done much work
> yet, I suggest not to merge this patch into the mainline, and wait until
> there is clear news before doing this to avoid introducing unnecessary
> modifications later.
If there are people who have the boards, I'd be inclined to make the
mainline kernel usable for them. Doing some renames or adding
compatibles down the road, if the SoC is actually rebranded, is not a big
deal. I'll leave it up to you guys as to what to do - it's only -rc4
today, so there's no impending doom.
Cheers,
Conor.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-12-03 11:51 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-18 23:18 [PATCH v4 0/7] Add Huashan Pi board support Inochi Amaoto
2023-10-18 23:18 ` [PATCH v4 1/7] dt-bindings: interrupt-controller: Add SOPHGO CV1812H plic Inochi Amaoto
2023-10-18 23:18 ` [PATCH v4 2/7] dt-bindings: timer: Add SOPHGO CV1812H clint Inochi Amaoto
2023-10-18 23:18 ` [PATCH v4 3/7] dt-bindings: riscv: Add SOPHGO Huashan Pi board compatibles Inochi Amaoto
2023-10-18 23:18 ` [PATCH v4 4/7] riscv: dts: sophgo: Separate compatible specific for CV1800B soc Inochi Amaoto
2023-10-19 12:04 ` Chen Wang
2023-10-18 23:18 ` [PATCH v4 5/7] riscv: dts: sophgo: cv18xx: Add gpio devices Inochi Amaoto
2023-10-19 12:02 ` Chen Wang
2023-10-18 23:18 ` [PATCH v4 6/7] riscv: dts: sophgo: add initial CV1812H SoC device tree Inochi Amaoto
2023-10-19 12:01 ` Chen Wang
2023-10-18 23:18 ` [PATCH v4 7/7] riscv: dts: sophgo: add Huashan Pi board " Inochi Amaoto
2023-10-19 12:00 ` Chen Wang
2023-10-19 14:04 ` [PATCH v4 0/7] Add Huashan Pi board support Conor Dooley
2023-11-30 12:51 ` Conor Dooley
2023-11-30 23:21 ` Inochi Amaoto
2023-12-01 0:41 ` Conor Dooley
2023-12-01 1:02 ` Inochi Amaoto
2023-12-01 8:14 ` Conor Dooley
2023-12-01 8:31 ` Inochi Amaoto
2023-12-01 16:21 ` Conor Dooley
2023-12-02 0:22 ` Inochi Amaoto
2023-12-02 1:11 ` Chen Wang
2023-12-03 11:51 ` Conor Dooley [this message]
2023-12-03 23:32 ` Inochi Amaoto
2023-12-04 9:15 ` Chen Wang
2023-12-04 9:32 ` Conor Dooley
2023-12-04 12:25 ` Chen Wang
2023-12-04 12:28 ` 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=20231203-parabola-deploy-105940119261@spud \
--to=conor@kernel.org \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=chao.wei@sophgo.com \
--cc=conor+dt@kernel.org \
--cc=conor.dooley@microchip.com \
--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=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=unicorn_wang@outlook.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