From: Cristian Ciocaltea <cristian.ciocaltea@collabora.com>
To: Conor Dooley <conor@kernel.org>
Cc: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Michael Zhu <michael.zhu@starfivetech.com>,
Drew Fustini <drew@beagleboard.org>,
Emil Renner Berthing <kernel@esmil.dk>,
Conor Dooley <conor.dooley@microchip.com>,
devicetree@vger.kernel.org, linux-riscv@lists.infradead.org,
linux-kernel@vger.kernel.org, kernel@collabora.com
Subject: Re: [PATCH v4 0/3] Enable initial support for StarFive VisionFive V1 SBC
Date: Wed, 16 Nov 2022 23:04:03 +0200 [thread overview]
Message-ID: <3b4b8aef-a06d-36b5-a143-78f0ce30eb77@collabora.com> (raw)
In-Reply-To: <Y3Ui9mmcvuWMw2AL@spud>
On 11/16/22 19:50, Conor Dooley wrote:
> On Tue, Oct 18, 2022 at 12:05:39AM +0300, Cristian Ciocaltea wrote:
>> The StarFive VisionFive V1 SBC [1] is similar with the already supported
>> BeagleV Starlight Beta board, both being based on the StarFive JH7100 SoC.
>>
>> In addition to documenting the necessary compatibles, this patch series
>> moves most of the content from jh7100-beaglev-starlight.dts to a new file
>> jh7100-common.dtsi, to be shared between the two boards.
>>
>> No other changes are required in order to successfully boot the board.
>>
>> [1] https://github.com/starfive-tech/VisionFive
>
> Hey Cristian,
>
> Apologies for the delay here, we've been sorting out re-routing RISC-V
> DT stuff via the SoC tree. That should be sorted now, so I have picked
> the series up. Should be at:
> https://git.kernel.org/conor/c/a3fe69160c7328a284ebc711ccb689f3beec42dc
Hi Conor,
No problem, thanks for taking care of this!
Regards,
Cristian
> Thanks,
> Conor.
>
>>
>> Changes in v4:
>> - Rebased onto v6.1.0-rc1
>> - Fixed a conflict in patch 2/3 as pinctrl-starfive.h has been renamed
>> to pinctrl-starfive-jh7100.h
>>
>> Changes in v3:
>> - Added Reviewed-by tag from Krzysztof in patch 1/3
>> - Optimized patch 2/3 by enabling copy detection on "git format-patch",
>> as indicated by Krzysztof
>>
>> Changes in v2:
>> - Simplified documentation by using 'enum' instead of 'const' in
>> patch 1/3, according to Conor's review
>> - Added Reviewed-by tags from Conor
>>
>> Cristian Ciocaltea (3):
>> dt-bindings: riscv: starfive: Add StarFive VisionFive V1 board
>> riscv: dts: starfive: Add common DT for JH7100 based boards
>> riscv: dts: starfive: Add StarFive VisionFive V1 device tree
>>
>> .../devicetree/bindings/riscv/starfive.yaml | 4 +-
>> arch/riscv/boot/dts/starfive/Makefile | 2 +-
>> .../dts/starfive/jh7100-beaglev-starlight.dts | 153 +-----------------
>> ...aglev-starlight.dts => jh7100-common.dtsi} | 3 -
>> .../jh7100-starfive-visionfive-v1.dts | 20 +++
>> 5 files changed, 25 insertions(+), 157 deletions(-)
>> copy arch/riscv/boot/dts/starfive/{jh7100-beaglev-starlight.dts => jh7100-common.dtsi} (96%)
>> create mode 100644 arch/riscv/boot/dts/starfive/jh7100-starfive-visionfive-v1.dts
>>
>>
>> base-commit: 9abf2313adc1ca1b6180c508c25f22f9395cc780
>> --
>> 2.38.0
>>
prev parent reply other threads:[~2022-11-16 21:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-17 21:05 Cristian Ciocaltea
2022-10-17 21:05 ` [PATCH v4 1/3] dt-bindings: riscv: starfive: Add StarFive VisionFive V1 board Cristian Ciocaltea
2022-10-18 8:15 ` Matthias Brugger
2022-10-17 21:05 ` [PATCH v4 2/3] riscv: dts: starfive: Add common DT for JH7100 based boards Cristian Ciocaltea
2022-10-18 8:22 ` Matthias Brugger
2022-10-17 21:05 ` [PATCH v4 3/3] riscv: dts: starfive: Add StarFive VisionFive V1 device tree Cristian Ciocaltea
2022-10-18 8:26 ` Matthias Brugger
2022-11-16 17:50 ` [PATCH v4 0/3] Enable initial support for StarFive VisionFive V1 SBC Conor Dooley
2022-11-16 21:04 ` Cristian Ciocaltea [this message]
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=3b4b8aef-a06d-36b5-a143-78f0ce30eb77@collabora.com \
--to=cristian.ciocaltea@collabora.com \
--cc=aou@eecs.berkeley.edu \
--cc=conor.dooley@microchip.com \
--cc=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=drew@beagleboard.org \
--cc=kernel@collabora.com \
--cc=kernel@esmil.dk \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=michael.zhu@starfivetech.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=robh+dt@kernel.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
all inboxes | Powered by JetHome®