On 2023/12/4 7:32, Inochi Amaoto wrote:
On 2023/12/2 0:21, Conor Dooley wrote:
On Fri, Dec 01, 2023 at 04:31:38PM +0800, Inochi Amaoto wrote:
On Fri, Dec 01, 2023 at 09:02:59AM +0800, Inochi Amaoto wrote:
On Fri, Dec 01, 2023 at 07:21:29AM +0800, Inochi Amaoto wrote:
On Thu, 19 Oct 2023 07:18:00 +0800, Inochi Amaoto wrote:
Huashan Pi board is an embedded development platform based on the
CV1812H chip. Add minimal device tree files for this board.
Currently, it can boot to a basic shell.
NOTE: this series is based on the Jisheng's Milk-V Duo patch.
Link: https://en.sophgo.com/product/introduce/huashan.html
Link: https://en.sophgo.com/product/introduce/cv181xH.html
Link: https://lore.kernel.org/linux-riscv/20231006121449.721-1-jszhang@xxxxxxxxxx/
[...]
Applied to riscv-dt-for-next, thanks! LMK if something looks not as
expected.
[1/7] dt-bindings: interrupt-controller: Add SOPHGO CV1812H plic
https://git.kernel.org/conor/c/21a34e63afcc
[2/7] dt-bindings: timer: Add SOPHGO CV1812H clint
https://git.kernel.org/conor/c/06ea2a1968a9
[3/7] dt-bindings: riscv: Add SOPHGO Huashan Pi board compatibles
https://git.kernel.org/conor/c/d7b92027834e
[4/7] riscv: dts: sophgo: Separate compatible specific for CV1800B soc
https://git.kernel.org/conor/c/5b5dce3951b2
[5/7] riscv: dts: sophgo: cv18xx: Add gpio devices
https://git.kernel.org/conor/c/dd791b45c866
[6/7] riscv: dts: sophgo: add initial CV1812H SoC device tree
https://git.kernel.org/conor/c/681ec684a741
[7/7] riscv: dts: sophgo: add Huashan Pi board device tree
https://git.kernel.org/conor/c/2c36b0cfb408
Thanks for the confirmation. But I suggest to revert these patches.
Several days ago, Sophgo informed me that CV1810 series will be
renamed. And the Huashan Pi will switch to the chip with new name.
To avoid unnecessary conflict, please drop these patch and I will
prepare a new patch once the renamed chip is launched.
This is a board that exists, that you (and possibly others) have, right?
Yes, of course.
I dunno then. It sounds from your message that this is purely a rebrand
of the SoCs,
IIRC, it is.
FYI, Chen and Chao. Maybe you know something more.
so since people already have these boards, I'd rather not.
We should be able to support both since it's just a naming change,
right?
I agree with this. If the above is true, we can just reuse the exists code
with a different compatible name, right?
I think so? I'm not sure what the precedent really is for pure
rebrandings of an SoC.
I say for now, assume we can do that, and we can discuss it with Rob and
Krzysztof when the time comes if there is no difference between the SoCs
and boards.
Cheers,
Conor.
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.
Hi Chen,
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.
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.
Thanks Inochi for your info, let's just preserve these code for huashan
pi now and keep watching on what's going on then.
Regards,
Chen
Thanks,
Chen
