public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: Yanhong Wang <yanhong.wang@starfivetech.com>
Cc: u-boot@lists.denx.de, Rick Chen <rick@andestech.com>,
	Leo <ycliang@andestech.com>, Lukasz Majewski <lukma@denx.de>,
	Sean Anderson <seanga2@gmail.com>,
	Lee Kuan Lim <kuanlim.lee@starfivetech.com>,
	Jianlong Huang <jianlong.huang@starfivetech.com>,
	Emil Renner Berthing <kernel@esmil.dk>
Subject: Re: [PATCH v2 00/17] Basic StarFive JH7110 RISC-V SoC support
Date: Sat, 21 Jan 2023 21:36:04 +0000	[thread overview]
Message-ID: <Y8xaxNYCxbnHMDT/@spud> (raw)
In-Reply-To: <20230118081132.31403-1-yanhong.wang@starfivetech.com>

[-- Attachment #1: Type: text/plain, Size: 2694 bytes --]

On Wed, Jan 18, 2023 at 04:11:15PM +0800, Yanhong Wang wrote:
> This series of patches base on the latest branch/master, and add support
> for the StarFive JH7110 RISC-V SoC and VisionFive V2 board. In order for
> this to be achieved, the respective DT nodes have been added,  and the
> required defconfigs have been added to the boards' defconfig. What is more,
> the basic required DM drivers have been added, such as reset, clock, pinctrl,
> uart, ram etc.
> 
> Note that the register base address of reset controller is same with the
> clock controller. Therefore, there is no device tree node alone for reset
> driver. It binds device node in the clock driver.
> 
> The u-boot-spl and u-boot has been tested on the VisionFive V2 boards which
> equip with JH7110 SoC and works normally.
> 
> For more information and support, you can visit RVspace wiki[1].
> 
> [1] https://wiki.rvspace.org/
> 
> Changes in v2:
> - Renamed file 'jh7110-regs.h' to 'regs.h'.
> - Reworded the clear L2 LIM memory code in C.
> - Removed flash init call in 'spl_soc_init' function.
> - Reworded the clock driver.
> - Rename the macro 'SET_DIV' to 'ASSIGNED_CLOCK_PARENTS' in 'spl.c'.
> - Moved the device tree node 'dmc@15700000' from 'jh7110-u-boot.dtsi' to
>   'starfive_visionfive2-u-boot.dtsi'.
> 
> Previous versions:
> v1 - https://patchwork.ozlabs.org/project/uboot/cover/20221212025020.23778-1-yanhong.wang@starfivetech.com/
> 
> Jianlong Huang (1):
>   dt-bindings: pinctrl: Add StarFive JH7110 pinctrl definitions
> 
> Kuan Lim Lee (1):
>   pinctrl: starfive: Add StarFive JH7110 driver
> 
> Yanhong Wang (15):
>   riscv: cpu: jh7110: Add support for jh7110 SoC
>   cache: starfive: Add StarFive JH7110 support
>   dt-bindings: reset: Add StarFive JH7110 reset definitions
>   reset: starfive: jh7110: Add reset driver for StarFive JH7110 SoC
>   dt-bindings: clock: Add StarFive JH7110 clock definitions
>   clk: starfive: Add StarFive JH7110 clock driver
>   ram: starfive: add ddr driver
>   board: starfive: add StarFive VisionFive v2 board support
>   riscv: cpu: jh7110: Add Kconfig for StarFive JH7110 SoC
>   board: starfive: Add Kconfig for StarFive VisionFive v2 Board
>   board: starfive: Add TARGET_STARFIVE_VISIONFIVE2 to Kconfig
>   riscv: dts: jh7110: Add initial StarFive JH7110 device tree
>   riscv: dts: jh7110: Add initial u-boot device tree
>   riscv: dts: jh7110: Add initial StarFive VisionFive v2 board device
>     tree
>   configs: starfive: add starfive_visionfive2_defconfig

Apologies if I have missed it somewhere - but where is patch 12?
I don't see it on lore.kernel.org nor in my inbox :(

Thanks,
Conor.


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  parent reply	other threads:[~2023-01-21 21:36 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-18  8:11 [PATCH v2 00/17] Basic StarFive JH7110 RISC-V SoC support Yanhong Wang
2023-01-18  8:11 ` [PATCH v2 01/17] riscv: cpu: jh7110: Add support for jh7110 SoC Yanhong Wang
2023-01-18  8:11 ` [PATCH v2 02/17] cache: starfive: Add StarFive JH7110 support Yanhong Wang
2023-01-18  8:11 ` [PATCH v2 03/17] dt-bindings: reset: Add StarFive JH7110 reset definitions Yanhong Wang
2023-01-18  8:11 ` [PATCH v2 04/17] reset: starfive: jh7110: Add reset driver for StarFive JH7110 SoC Yanhong Wang
2023-01-18  8:11 ` [PATCH v2 05/17] dt-bindings: clock: Add StarFive JH7110 clock definitions Yanhong Wang
2023-01-21 18:37   ` Sean Anderson
2023-01-18  8:11 ` [PATCH v2 06/17] clk: starfive: Add StarFive JH7110 clock driver Yanhong Wang
2023-01-21 18:56   ` Sean Anderson
2023-02-16  3:16     ` yanhong wang
2023-01-18  8:11 ` [PATCH v2 07/17] dt-bindings: pinctrl: Add StarFive JH7110 pinctrl definitions Yanhong Wang
2023-01-18  8:11 ` [PATCH v2 08/17] pinctrl: starfive: Add StarFive JH7110 driver Yanhong Wang
2023-01-18  8:11 ` [PATCH v2 09/17] ram: starfive: add ddr driver Yanhong Wang
2023-01-18  8:11 ` [PATCH v2 10/17] board: starfive: add StarFive VisionFive v2 board support Yanhong Wang
2023-01-21 17:38   ` Sean Anderson
2023-01-18  8:11 ` [PATCH v2 11/17] riscv: cpu: jh7110: Add Kconfig for StarFive JH7110 SoC Yanhong Wang
2023-01-18  8:11 ` [PATCH v2 13/17] board: starfive: Add TARGET_STARFIVE_VISIONFIVE2 to Kconfig Yanhong Wang
2023-01-18  8:11 ` [PATCH v2 14/17] riscv: dts: jh7110: Add initial StarFive JH7110 device tree Yanhong Wang
2023-01-19  6:18   ` David Abdurachmanov
2023-01-19  6:26     ` Sean Anderson
2023-01-19 18:30       ` Conor Dooley
2023-01-19 19:16         ` Sean Anderson
2023-01-19 19:25           ` Conor Dooley
2023-01-20  1:37             ` Sean Anderson
2023-02-16  5:50         ` yanhong wang
2023-01-18  8:11 ` [PATCH v2 15/17] riscv: dts: jh7110: Add initial u-boot " Yanhong Wang
2023-01-18  8:11 ` [PATCH v2 16/17] riscv: dts: jh7110: Add initial StarFive VisionFive v2 board " Yanhong Wang
2023-01-21 18:46   ` Sean Anderson
2023-02-16  6:20     ` yanhong wang
2023-01-18  8:11 ` [PATCH v2 17/17] configs: starfive: add starfive_visionfive2_defconfig Yanhong Wang
2023-01-23 14:53   ` Andreas Schwab
2023-02-16  7:28     ` yanhong wang
2023-02-16 14:17   ` Heinrich Schuchardt
2023-01-21 21:36 ` Conor Dooley [this message]
2023-01-21 21:56   ` [PATCH v2 00/17] Basic StarFive JH7110 RISC-V SoC support Sean Anderson
2023-01-21 22:05     ` Conor Dooley
2023-01-22 18:42       ` Conor Dooley
2023-02-10 17:41         ` Conor Dooley
2023-02-16  7:39     ` yanhong wang
2023-01-24  0:28 ` Heinrich Schuchardt
2023-02-16  9:01   ` yanhong wang
2023-01-24 14:46 ` Andreas Schwab
2023-02-06  7:38 ` Jan Kiszka
2023-02-07 15:46   ` Bin Meng

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=Y8xaxNYCxbnHMDT/@spud \
    --to=conor@kernel.org \
    --cc=jianlong.huang@starfivetech.com \
    --cc=kernel@esmil.dk \
    --cc=kuanlim.lee@starfivetech.com \
    --cc=lukma@denx.de \
    --cc=rick@andestech.com \
    --cc=seanga2@gmail.com \
    --cc=u-boot@lists.denx.de \
    --cc=yanhong.wang@starfivetech.com \
    --cc=ycliang@andestech.com \
    /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