public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
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: Thu, 2 Nov 2023 18:49:56 +0800	[thread overview]
Message-ID: <ZUN-1ADrFIKePtRs@swlinux02> (raw)

Hi Tom,

The following changes since commit a803f87202aa48974bdff4d8100464a8288931e4:

  Merge https://source.denx.de/u-boot/custodians/u-boot-mmc (2023-11-01 09:44:33 -0400)

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 9d22d4a7cef7f2fdaf5c060b71574e6f82ea5ff0:

  configs: visionfive2: Enable JH7110 RNG driver (2023-11-02 17:45:53 +0800)

CI result shows no issue: https://source.denx.de/u-boot/custodians/u-boot-riscv/-/pipelines/18407
----------------------------------------------------------------

+ CI: Use OpenSBI 1.3.1 release for testing
+ riscv: Support resume after exception
+ rng: Support RNG provided by RISC-V Zkr ISA extension
+ board: starfive VF2: Support jtag
+ board: starfive VF2: Support TRNG driver
+ board: sifive unmatched: Move kernel load address

----------------------------------------------------------------
Chanho Park (7):
      riscv: cpu: jh7110: Add gpio helper macros
      board: starfive: spl: Support jtag for VisionFive2 board
      riscv: import read/write_relaxed functions
      clk: starfive: jh7110: Add security clocks
      rng: Add StarFive JH7110 RNG driver
      riscv: dts: jh7110: Add rng device tree node
      configs: visionfive2: Enable JH7110 RNG driver

Heinrich Schuchardt (3):
      CI: use OpenSBI 1.3.1 for testing
      riscv: allow resume after exception
      rng: Provide a RNG based on the RISC-V Zkr ISA extension

Samuel Holland (3):
      riscv: Sort target configs alphabetically
      riscv: Align the trap handler to 64 bytes
      riscv: Weakly define invalidate_icache_range()

Yong-Xuan Wang (1):
      board: sifive: unmatched: move kernel load address to 0x80200000

 .azure-pipelines.yml                      |   8 +-
 .gitlab-ci.yml                            |   8 +-
 arch/riscv/Kconfig                        |  18 +-
 arch/riscv/cpu/mtrap.S                    |   2 +-
 arch/riscv/dts/jh7110.dtsi                |  10 ++
 arch/riscv/include/asm/arch-jh7110/gpio.h |  85 +++++++++
 arch/riscv/include/asm/io.h               |  45 +++++
 arch/riscv/lib/cache.c                    |   2 +-
 arch/riscv/lib/interrupts.c               |  13 ++
 board/starfive/visionfive2/spl.c          |  23 +++
 configs/starfive_visionfive2_defconfig    |   2 +
 doc/api/index.rst                         |   1 +
 doc/api/interrupt.rst                     |   6 +
 drivers/clk/starfive/clk-jh7110.c         |  10 ++
 drivers/rng/Kconfig                       |  14 ++
 drivers/rng/Makefile                      |   2 +
 drivers/rng/jh7110_rng.c                  | 274 ++++++++++++++++++++++++++++++
 drivers/rng/riscv_zkr_rng.c               | 116 +++++++++++++
 include/configs/sifive-unmatched.h        |   2 +-
 include/interrupt.h                       |  45 +++++
 20 files changed, 666 insertions(+), 20 deletions(-)
 create mode 100644 arch/riscv/include/asm/arch-jh7110/gpio.h
 create mode 100644 doc/api/interrupt.rst
 create mode 100644 drivers/rng/jh7110_rng.c
 create mode 100644 drivers/rng/riscv_zkr_rng.c
 create mode 100644 include/interrupt.h

 Best regards,
 Leo

             reply	other threads:[~2023-11-02 10:54 UTC|newest]

Thread overview: 76+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-02 10:49 Leo Liang [this message]
2023-11-02 14:53 ` [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-04-09  8:25 Leo Liang
2024-04-10  0:43 ` 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
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=ZUN-1ADrFIKePtRs@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox