devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: E Shattow <e@freeshell.de>
To: Maud Spierings <maud_spierings@hotmail.com>, linux.amoon@gmail.com
Cc: aou@eecs.berkeley.edu, bhelgaas@google.com, broonie@kernel.org,
	conor+dt@kernel.org, devicetree@vger.kernel.org,
	emil.renner.berthing@canonical.com, hal.feng@starfivetech.com,
	heinrich.schuchardt@canonical.com, krzk+dt@kernel.org,
	kwilczynski@kernel.org, lgirdwood@gmail.com,
	linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org,
	linux-riscv@lists.infradead.org, lpieralisi@kernel.org,
	mani@kernel.org, palmer@dabbelt.com, pjw@kernel.org,
	rafael@kernel.org, robh@kernel.org, viresh.kumar@linaro.org,
	sandie.cao@deepcomputing.io
Subject: Re: [PATCH v4 4/6] riscv: dts: starfive: Add common board dtsi for VisionFive 2 Lite variants
Date: Thu, 4 Dec 2025 23:30:19 -0800	[thread overview]
Message-ID: <72318f65-a360-4be0-baee-7f94b7cbf949@freeshell.de> (raw)
In-Reply-To: <AM7P189MB1009B900894F02496519B2F4E3A7A@AM7P189MB1009.EURP189.PROD.OUTLOOK.COM>



On 12/4/25 23:23, Maud Spierings wrote:
>>
>> Hi Hal,
>>
>> On Tue, 25 Nov 2025 at 13:27, Hal Feng <hal.feng@starfivetech.com> wrote:
>>>
>>> Add a common board dtsi for use by VisionFive 2 Lite and
>>> VisionFive 2 Lite eMMC.
>>>
>>> Acked-by: Emil Renner Berthing <emil.renner.berthing@canonical.com>
>>> Tested-by: Matthias Brugger <mbrugger@suse.com>
>>> Signed-off-by: Hal Feng <hal.feng@starfivetech.com>
>>> ---
>>>  .../jh7110-starfive-visionfive-2-lite.dtsi    | 161 ++++++++++++++++++
>>>  1 file changed, 161 insertions(+)
>>>  create mode 100644 arch/riscv/boot/dts/starfive/jh7110-starfive-
>>> visionfive-2-lite.dtsi
>>>
>>> diff --git a/arch/riscv/boot/dts/starfive/jh7110-starfive-
>>> visionfive-2-lite.dtsi b/arch/riscv/boot/dts/starfive/jh7110-
>>> starfive-visionfive-2-lite.dtsi
>>> new file mode 100644
>>> index 000000000000..f8797a666dbf
>>> --- /dev/null
>>> +++ b/arch/riscv/boot/dts/starfive/jh7110-starfive-visionfive-2-
>>> lite.dtsi
>>> @@ -0,0 +1,161 @@
>>> +// SPDX-License-Identifier: GPL-2.0 OR MIT
>>> +/*
>>> + * Copyright (C) 2025 StarFive Technology Co., Ltd.
>>> + * Copyright (C) 2025 Hal Feng <hal.feng@starfivetech.com>
>>> + */
>>> +
>>> +/dts-v1/;
>>> +#include "jh7110-common.dtsi"
>>> +
>>> +/ {
>>> +       vcc_3v3_pcie: regulator-vcc-3v3-pcie {
>>> +               compatible = "regulator-fixed";
>>> +               enable-active-high;
>>> +               gpio = <&sysgpio 27 GPIO_ACTIVE_HIGH>;
>>> +               regulator-name = "vcc_3v3_pcie";
>>> +               regulator-min-microvolt = <3300000>;
>>> +               regulator-max-microvolt = <3300000>;
>>> +       };
>>> +};
>>
>> The vcc_3v3_pcie regulator node is common to all JH7110 development
>> boards.
>> and it is enabled through the PWREN_H signal (PCIE0_PWREN_H_GPIO32).
>>
>> VisionFive 2 Product Design Schematics below
>> [1] https://doc-en.rvspace.org/VisionFive2/PDF/
>> SCH_RV002_V1.2A_20221216.pdf
>>
>> Mars_Hardware_Schematics
>> [2] https://github.com/milkv-mars/mars-files/blob/main/
>> Mars_Hardware_Schematics/Milk-V_Mars_SCH_V1.21_2024-0510.pdf
>>
> 
> I'm not sure if this also holds true for the deepcomputing fml13v01,
> sadly as far as I know there is no schematics available for that.
> 
> the downstream dts [3] doesn't contain any evidence of it, neither does
> upstream.
> 
> I wouldn't be surprised if it is there but just not present in the dts,
> but it may be nice to get some feedback from someone at deepcomputing.
> 
> adding Sandie Cao who did some of the upstreaming work.
> 
> Link: https://github.com/DC-DeepComputing/fml13v01-linux/
> blob/97c64fe2832b6826914b6da7aa4febcdd4d3d444/arch/riscv/boot/dts/
> starfive/jh7110-deepcomputing-fml13v01.dts#L416-L432 [3]
> 
> kind regards,
> Maud
> 

I asked (to DeepComputing sales e-mail address) for schematics 28th July
2025, the reply was "There is no plan to public it by now." I also got
some generic response when I asked a technical question about RGPIO3
connection to look at the DeepComputing repo on github.

No schematics and no help to developers.

-E

  reply	other threads:[~2025-12-05  7:37 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-25  7:55 [PATCH v4 0/6] Add support for StarFive VisionFive 2 Lite board Hal Feng
2025-11-25  7:55 ` [PATCH v4 1/6] PCI: starfive: Use regulator APIs instead of GPIO APIs to enable the 3V3 power supply of PCIe slots Hal Feng
2025-11-25 20:00   ` Conor Dooley
2025-12-06 12:37     ` Matthias Brugger
2025-12-01  6:45   ` Hal Feng
2025-12-01 20:52   ` Bjorn Helgaas
2025-12-02  1:45     ` 回复: " Kevin Xie
2025-12-02  3:02       ` Kevin Xie
2025-12-02  3:16         ` Kevin Xie
2025-12-02 16:31         ` Bjorn Helgaas
2025-12-04 13:19           ` Hal Feng
2025-12-02  3:38     ` Hal Feng
2025-11-25  7:56 ` [PATCH v4 2/6] dt-bindings: riscv: Add StarFive JH7110S SoC and VisionFive 2 Lite board Hal Feng
2025-11-25  7:56 ` [PATCH v4 3/6] riscv: dts: starfive: jh7110-common: Move out some nodes to the board dts Hal Feng
2025-11-25  7:56 ` [PATCH v4 4/6] riscv: dts: starfive: Add common board dtsi for VisionFive 2 Lite variants Hal Feng
2025-12-04 17:05   ` Anand Moon
2025-12-05  7:23     ` Maud Spierings
2025-12-05  7:30       ` E Shattow [this message]
2025-12-05  7:41     ` Hal Feng
2025-12-05  8:01       ` Anand Moon
2025-11-25  7:56 ` [PATCH v4 5/6] riscv: dts: starfive: Add VisionFive 2 Lite board device tree Hal Feng
2025-11-26  1:44   ` E Shattow
2025-11-25  7:56 ` [PATCH v4 6/6] riscv: dts: starfive: Add VisionFive 2 Lite eMMC " Hal Feng
2025-11-26  1:45   ` E Shattow
2025-11-25 22:24 ` (subset) [PATCH v4 0/6] Add support for StarFive VisionFive 2 Lite board Conor Dooley
2025-12-19  8:09 ` patchwork-bot+linux-riscv

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=72318f65-a360-4be0-baee-7f94b7cbf949@freeshell.de \
    --to=e@freeshell.de \
    --cc=aou@eecs.berkeley.edu \
    --cc=bhelgaas@google.com \
    --cc=broonie@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=emil.renner.berthing@canonical.com \
    --cc=hal.feng@starfivetech.com \
    --cc=heinrich.schuchardt@canonical.com \
    --cc=krzk+dt@kernel.org \
    --cc=kwilczynski@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=linux.amoon@gmail.com \
    --cc=lpieralisi@kernel.org \
    --cc=mani@kernel.org \
    --cc=maud_spierings@hotmail.com \
    --cc=palmer@dabbelt.com \
    --cc=pjw@kernel.org \
    --cc=rafael@kernel.org \
    --cc=robh@kernel.org \
    --cc=sandie.cao@deepcomputing.io \
    --cc=viresh.kumar@linaro.org \
    /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;
as well as URLs for NNTP newsgroup(s).