All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chen Wang <unicorn_wang@outlook.com>
To: Conor Dooley <conor.dooley@microchip.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
Date: Mon, 4 Dec 2023 20:25:13 +0800	[thread overview]
Message-ID: <MA0P287MB0332862DC235652C83B4EC2EFE86A@MA0P287MB0332.INDP287.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <20231204-crane-wolf-95f32865db62@wendy>


On 2023/12/4 17:32, Conor Dooley wrote:
> On Mon, Dec 04, 2023 at 05:15:36PM +0800, Chen Wang wrote:
>> 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", 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.
> Could you explain on what you mean by "preserve"? I'm a little unsure.

hi, Conor,

I meant keeping your changes on riscv-dt-for-next and continue 
submitting this patch ([PATCH v4 0/7] Add Huashan Pi board support) to 
upstream.

Sorry for my poor english, hope I have explained it well. :$

Thanks,

Chen


WARNING: multiple messages have this Message-ID (diff)
From: Chen Wang <unicorn_wang@outlook.com>
To: Conor Dooley <conor.dooley@microchip.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
Date: Mon, 4 Dec 2023 20:25:13 +0800	[thread overview]
Message-ID: <MA0P287MB0332862DC235652C83B4EC2EFE86A@MA0P287MB0332.INDP287.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <20231204-crane-wolf-95f32865db62@wendy>


On 2023/12/4 17:32, Conor Dooley wrote:
> On Mon, Dec 04, 2023 at 05:15:36PM +0800, Chen Wang wrote:
>> 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", 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.
> Could you explain on what you mean by "preserve"? I'm a little unsure.

hi, Conor,

I meant keeping your changes on riscv-dt-for-next and continue 
submitting this patch ([PATCH v4 0/7] Add Huashan Pi board support) to 
upstream.

Sorry for my poor english, hope I have explained it well. :$

Thanks,

Chen


_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

  reply	other threads:[~2023-12-04 12:25 UTC|newest]

Thread overview: 56+ 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 ` 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   ` 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   ` 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   ` Inochi Amaoto
2023-10-18 23:18 ` [PATCH v4 4/7] riscv: dts: sophgo: Separate compatible specific for CV1800B soc Inochi Amaoto
2023-10-18 23:18   ` Inochi Amaoto
2023-10-19 12:04   ` Chen Wang
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-18 23:18   ` Inochi Amaoto
2023-10-19 12:02   ` Chen Wang
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-18 23:18   ` Inochi Amaoto
2023-10-19 12:01   ` Chen Wang
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-18 23:18   ` Inochi Amaoto
2023-10-19 12:00   ` Chen Wang
2023-10-19 12:00     ` Chen Wang
2023-10-19 14:04 ` [PATCH v4 0/7] Add Huashan Pi board support Conor Dooley
2023-10-19 14:04   ` Conor Dooley
2023-11-30 12:51 ` Conor Dooley
2023-11-30 12:51   ` Conor Dooley
2023-11-30 23:21   ` Inochi Amaoto
2023-11-30 23:21     ` Inochi Amaoto
2023-12-01  0:41     ` Conor Dooley
2023-12-01  0:41       ` Conor Dooley
2023-12-01  1:02       ` Inochi Amaoto
2023-12-01  1:02         ` Inochi Amaoto
2023-12-01  8:14         ` Conor Dooley
2023-12-01  8:14           ` Conor Dooley
2023-12-01  8:31           ` Inochi Amaoto
2023-12-01  8:31             ` Inochi Amaoto
2023-12-01 16:21             ` Conor Dooley
2023-12-01 16:21               ` Conor Dooley
2023-12-02  0:22               ` Inochi Amaoto
2023-12-02  0:22                 ` Inochi Amaoto
2023-12-02  1:11               ` Chen Wang
2023-12-02  1:11                 ` Chen Wang
2023-12-03 11:51                 ` Conor Dooley
2023-12-03 11:51                   ` Conor Dooley
2023-12-03 23:32                 ` Inochi Amaoto
2023-12-03 23:32                   ` Inochi Amaoto
2023-12-04  9:15                   ` Chen Wang
2023-12-04  9:15                     ` Chen Wang
2023-12-04  9:32                     ` Conor Dooley
2023-12-04  9:32                       ` Conor Dooley
2023-12-04 12:25                       ` Chen Wang [this message]
2023-12-04 12:25                         ` Chen Wang
2023-12-04 12:28                         ` Conor Dooley
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=MA0P287MB0332862DC235652C83B4EC2EFE86A@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.dooley@microchip.com \
    --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=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 \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.