Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:7 as permitted sender) client-ip=2620:137:e000::3:7;
Date:   Mon, 4 Dec 2023 09:32:56 +0000
From:   Conor Dooley <conor.dooley@microchip.com>
To:     Chen Wang <unicorn_wang@outlook.com>
CC:     Inochi Amaoto <inochiama@outlook.com>,
        Conor Dooley <conor@kernel.org>,
        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>,
        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
Message-ID: <20231204-crane-wolf-95f32865db62@wendy>
References: <MA0P287MB033290A6C8B15202E31E43CCFE80A@MA0P287MB0332.INDP287.PROD.OUTLOOK.COM>
 <IA1PR20MB49537B177B6F3614D8D1E3E6BB87A@IA1PR20MB4953.namprd20.prod.outlook.com>
 <MA0P287MB0332AE2378D633B8A2DCFB77FE86A@MA0P287MB0332.INDP287.PROD.OUTLOOK.COM>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
        protocol="application/pgp-signature"; boundary="McIyWL/yGKMUQDuC"
Content-Disposition: inline
In-Reply-To: <MA0P287MB0332AE2378D633B8A2DCFB77FE86A@MA0P287MB0332.INDP287.PROD.OUTLOOK.COM>
Precedence: bulk

--McIyWL/yGKMUQDuC
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Mon, Dec 04, 2023 at 05:15:36PM +0800, Chen Wang wrote:
>=20
> On 2023/12/4 7:32, Inochi Amaoto wrote:
> > > On 2023/12/2 0:21, Conor Dooley wrote:

> > > As far as I know, sophgo's SoC product names all start with "sg", whi=
le products starting with "cv" come from CVITEK (another chip company). CVI=
TEK was acquired by sophgo a year ago, so now many SOC product names that o=
riginally started with "cv" are being repackaged and changed to start with =
"sg".
> > >=20
> > > For the cv1800b adopted by Duo, Sophgo has made it clear that it will=
 not change its codename.
> > >=20
> > > But I heard that for other products, such as the cv1812h used by Huas=
hanpi, sophgo may change their names in the future, but sophgo has not offi=
cially confirmed it yet. Looks like sophgo themselves are still in the proc=
ess of digesting cv's products, ;)
> > >=20
> > > 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 unt=
il there is clear news before doing this to avoid introducing unnecessary m=
odifications later.
> > >=20
> > Hi Chen,
> >=20
> > There is a update for you. The cv1812h does not have the A53 core as the
> > sg200x does. Maybe we should treat cv1812h as a trim of sg200x, not just
> > a reband.
> >=20
> > According to this information, I suggest to preserve these code for
> > cv1812h, it can make upstream the new soc eaiser. Also, adding a new
> > compatible is not too hard, and it is necessary if we have new soc.
> > Otherwise, the one with Huashan Pi now may be confused because it have
> > a old version.
>=20
> Thanks Inochi for your info, let's just preserve these code for huashan pi
> now and keep watching on what's going on then.

Could you explain on what you mean by "preserve"? I'm a little unsure.


--McIyWL/yGKMUQDuC
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iHUEABYIAB0WIQRh246EGq/8RLhDjO14tDGHoIJi0gUCZW2cyAAKCRB4tDGHoIJi
0iWtAQCTE8NoHTJcLy2WVDAg8jnv9rQILz7SbYqbBacA3DtmgAD/XtNuvBNLfda8
3vRc65P/zhIlckuMqFgMuwxMxDUS+wo=
=aCtm
-----END PGP SIGNATURE-----

--McIyWL/yGKMUQDuC--