From: Leo Liang <ycliang@andestech.com>
To: <trini@konsulko.com>
Cc: <u-boot@lists.denx.de>, <rick@andestech.com>, <ycliang@andestech.com>
Subject: [GIT PULL] u-boot-riscv/master
Date: Tue, 9 Apr 2024 16:25:36 +0800 [thread overview]
Message-ID: <ZhT7gPuUWx2sNkXJ@swlinux02> (raw)
Hi Tom,
The following changes since commit 069d07396e30aa9be396c1dd3fc158ac199e6843:
Merge tag 'efi-2024-07-rc1' of https://source.denx.de/u-boot/custodians/u-boot-efi (2024-04-08 14:33:59 -0600)
are available in the Git repository at:
https://source.denx.de/u-boot/custodians/u-boot-riscv.git
for you to fetch changes up to c1f78a4f632276bb4d77f8c79fe203709a9fa397:
doc: describe Milk-V Mars board (2024-04-09 11:30:37 +0800)
CI result shows no issue: https://source.denx.de/u-boot/custodians/u-boot-riscv/-/pipelines/20256
----------------------------------------------------------------
- RISC-V: Support backtrace and improve isa extension parsing
- cpu: Add cv1800b SoC support
- board: Add Milk-V Mars board support
- board: Add Milk-V Duo SD card support
----------------------------------------------------------------
Ben Dooks (1):
riscv: add backtrace support
Conor Dooley (2):
riscv: don't read riscv, isa in the riscv cpu's get_desc()
riscv: support extension probing using riscv, isa-extensions
Heinrich Schuchardt (7):
riscv: starfive: MMC card detect
riscv: do not set default fdt for VisionFive 2
eeprom: starfive: function get_product_id_from_eeprom()
riscv: set fdtfile on Milk-V Mars
board: starfive: support Milk-V Mars board
riscv: starfive: avoid including common.h
doc: describe Milk-V Mars board
Kongyang Liu (5):
riscv: cpu: cv1800b: Add support for cv1800b SoC
riscv: cache: Implement dcache for cv1800b
mmc: cv1800b: Add sdhci driver support for cv1800b SoC
riscv: dts: sophgo: Add clk node and sdhci node
configs: milkv_duo: Add SD card configs
Łukasz Stelmach (1):
riscv: Move virtio scan to board_late_init()
arch/riscv/Kconfig | 22 ++++
arch/riscv/Makefile | 4 +
arch/riscv/cpu/cpu.c | 60 +++++++----
arch/riscv/cpu/cv1800b/Kconfig | 12 +++
arch/riscv/cpu/cv1800b/Makefile | 7 ++
arch/riscv/cpu/cv1800b/cache.c | 45 ++++++++
arch/riscv/cpu/cv1800b/cpu.c | 9 ++
arch/riscv/cpu/cv1800b/dram.c | 21 ++++
arch/riscv/cpu/start.S | 1 +
arch/riscv/dts/cv1800b-milkv-duo.dts | 8 ++
arch/riscv/dts/cv1800b.dtsi | 4 +
arch/riscv/dts/cv18xx.dtsi | 22 ++++
arch/riscv/dts/jh7110-starfive-visionfive-2.dtsi | 2 +-
arch/riscv/include/asm/arch-jh7110/eeprom.h | 9 ++
arch/riscv/lib/interrupts.c | 35 +++++++
board/emulation/qemu-riscv/qemu-riscv.c | 12 +--
board/sophgo/milkv_duo/Kconfig | 4 +-
board/starfive/visionfive2/spl.c | 100 +++++++++++++++---
board/starfive/visionfive2/starfive_visionfive2.c | 48 ++++++---
.../starfive/visionfive2/visionfive2-i2c-eeprom.c | 9 +-
configs/milkv_duo_defconfig | 10 ++
configs/starfive_visionfive2_defconfig | 1 -
doc/board/starfive/index.rst | 1 +
doc/board/starfive/milk-v_mars.rst | 111 ++++++++++++++++++++
doc/board/starfive/visionfive2.rst | 18 ++++
drivers/cpu/riscv_cpu.c | 8 +-
drivers/mmc/Kconfig | 13 +++
drivers/mmc/Makefile | 1 +
drivers/mmc/cv1800b_sdhci.c | 116 +++++++++++++++++++++
29 files changed, 649 insertions(+), 64 deletions(-)
create mode 100644 arch/riscv/cpu/cv1800b/Kconfig
create mode 100644 arch/riscv/cpu/cv1800b/Makefile
create mode 100644 arch/riscv/cpu/cv1800b/cache.c
create mode 100644 arch/riscv/cpu/cv1800b/cpu.c
create mode 100644 arch/riscv/cpu/cv1800b/dram.c
create mode 100644 doc/board/starfive/milk-v_mars.rst
create mode 100644 drivers/mmc/cv1800b_sdhci.c
Best regards,
Leo
next reply other threads:[~2024-04-09 8:25 UTC|newest]
Thread overview: 76+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-09 8:25 Leo Liang [this message]
2024-04-10 0:43 ` [GIT PULL] u-boot-riscv/master Tom Rini
-- strict thread matches above, loose matches on Subject: below --
2025-10-16 12:07 [GIT,PULL] u-boot-riscv/master Leo Liang
2025-10-16 17:38 ` Tom Rini
2025-08-12 8:04 [GIT PULL] u-boot-riscv/master Leo Liang
2025-08-12 15:22 ` Tom Rini
2025-08-13 6:57 ` Leo Liang
2025-08-13 11:16 ` Martin Herren
2025-08-13 11:59 ` Leo Liang
2025-05-21 9:50 Leo Liang
2025-05-21 18:39 ` Tom Rini
2025-05-22 11:28 ` Conor Dooley
2025-05-22 14:45 ` Tom Rini
2025-05-22 15:36 ` Leo Liang
2025-05-22 15:54 ` Tom Rini
2025-05-22 16:40 ` Yao Zi
2025-05-23 9:18 ` Conor Dooley
2025-05-26 3:32 ` Mayuresh Chitale
2025-05-26 9:17 ` Conor Dooley
2025-05-26 14:56 ` Tom Rini
2025-05-26 17:34 ` Mayuresh Chitale
2025-05-26 18:16 ` Tom Rini
2025-05-27 17:10 ` Mayuresh Chitale
2025-05-27 17:34 ` Tom Rini
2025-04-25 10:07 Leo Liang
2025-04-25 10:35 ` Yao Zi
2025-04-26 14:14 ` Tom Rini
2025-04-25 12:57 ` E Shattow
2025-04-25 13:02 ` E Shattow
2025-04-25 23:43 ` Tom Rini
2025-04-26 1:13 ` E Shattow
2025-04-26 14:14 ` Tom Rini
2025-04-27 7:47 ` E Shattow
2025-03-25 6:19 Leo Liang
2025-03-25 20:18 ` Tom Rini
2025-03-06 12:18 Leo Liang
2025-03-07 11:20 ` Yao Zi
2025-02-20 5:13 Leo Liang
2025-02-20 17:19 ` Tom Rini
2025-02-03 8:17 Leo Liang
2025-02-03 21:26 ` Tom Rini
2025-01-17 1:53 Leo Liang
2025-01-17 17:56 ` Tom Rini
2024-11-27 13:08 Leo Liang
2024-11-27 18:54 ` Tom Rini
2024-11-06 12:12 Leo Liang
2024-11-08 16:51 ` Tom Rini
2024-11-11 13:24 ` Tom Rini
2024-10-29 12:33 Leo Liang
2024-10-29 16:37 ` Tom Rini
2024-10-28 12:24 Leo Liang
2024-10-28 19:33 ` Tom Rini
2024-07-22 8:29 Leo Liang
2024-07-22 19:31 ` Tom Rini
2024-05-30 8:56 Leo Liang
2024-06-03 17:42 ` Tom Rini
2024-05-14 13:28 Leo Liang
2024-05-14 16:14 ` Tom Rini
2024-05-01 16:38 Leo Liang
2024-05-02 14:42 ` Tom Rini
2024-03-26 13:22 Leo Liang
2024-03-27 12:12 ` Tom Rini
2024-03-12 8:51 Leo Liang
2024-03-12 18:52 ` Tom Rini
2024-01-31 10:21 Leo Liang
2024-01-31 14:14 ` Tom Rini
2023-12-14 2:38 Leo Yu-Chi Liang(梁育齊)
2023-12-14 12:19 ` Tom Rini
2023-12-14 12:46 ` Leo Liang
2023-12-14 14:39 ` Tom Rini
2023-12-07 13:46 Leo Liang
2023-12-09 20:59 ` Tom Rini
2023-11-02 10:49 Leo Liang
2023-11-02 14:53 ` Tom Rini
2021-02-26 1:53 Leo Liang
2021-02-26 17:40 ` Tom Rini
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=ZhT7gPuUWx2sNkXJ@swlinux02 \
--to=ycliang@andestech.com \
--cc=rick@andestech.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.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.