public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: "nico.cheng@rock-chips.com" <nico.cheng@rock-chips.com>
To: "Peter Robinson" <pbrobinson@gmail.com>
Cc: Glass <sjg@chromium.org>,
	philipp.tomsich <philipp.tomsich@vrull.eu>,
	 Yang <kever.yang@rock-chips.com>,
	 yamada.masahiro <yamada.masahiro@socionext.com>,
	 chenjh <chenjh@rock-chips.com>,
	jason.zhu <jason.zhu@rock-chips.com>,  trini <trini@konsulko.com>,
	yifeng.zhao <yifeng.zhao@rock-chips.com>,
	 u-boot <u-boot@lists.denx.de>
Subject: Re: Re: [PATCH v3 0/3] Add SPL build support for RK3568
Date: Tue, 26 Oct 2021 19:24:51 +0800	[thread overview]
Message-ID: <202110261924508927234@rock-chips.com> (raw)
In-Reply-To: CALeDE9NG5rWKQ_xVd-3iOd_mEBzs63hht6dZmX9FovgpxF33=g@mail.gmail.com

Hi Peter,

The scripts that package the ATF and other components are subject to further updates to the patch, which is not currently available in the submitted patch.

Nico

--------------



nico.cheng@rock-chips.com



>Hi Nico,



>



>Is this expected to work with Arm Trusted Firmware or some other TF?



>



>Could we have some docs/details for how to test this?



>



>Peter



>



>> This series adds support for the rk3568 SOC, SPL load next-stage image from



>> eMMC will be supported after this series of patches.



>>



>> Changes in v3:



>> Replace configuration parameters of SGRF_SOC_CON4 with macro



>> definitions.



>>



>> Changes in v2:



>> We use the rk_clrreg function instead of the writel to set eMMC sdmmc0 to



>> secure.



>> Modify comments to make them more explicit.



>>



>> Nico Cheng (3):



>>   rockchip: Kconfig: Enable SPL support for rk3568



>>   arm: dts: rockchip: rk3568: Enable sdhci and sdmmc0 node



>>   rockchip: rk3568: add arch_cpu_init()



>>



>>  arch/arm/dts/rk3568-u-boot.dtsi        | 17 ++++++++++++++++



>>  arch/arm/mach-rockchip/Kconfig         |  2 ++



>>  arch/arm/mach-rockchip/rk3568/rk3568.c | 27 +++++++++++++++++++++++---



>>  configs/evb-rk3568_defconfig           | 25 +++++++++++++++++++++++-



>>  include/configs/rk3568_common.h        |  4 ++++



>>  5 files changed, 71 insertions(+), 4 deletions(-)



>>



>> --



>> 2.17.1



>>



>>



>>



>



>



  reply	other threads:[~2021-10-26 11:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-26  2:42 [PATCH v3 0/3] Add SPL build support for RK3568 Nico Cheng
2021-10-26  2:42 ` [PATCH v3 1/3] rockchip: Kconfig: Enable SPL support for rk3568 Nico Cheng
2021-12-24  3:04   ` Kever Yang
2022-03-11 19:34   ` Jagan Teki
2021-10-26  2:42 ` [PATCH v3 2/3] arm: dts: rockchip: rk3568: Enable sdhci and sdmmc0 node Nico Cheng
2021-12-24  3:04   ` Kever Yang
2021-10-26  2:42 ` [PATCH v3 3/3] rockchip: rk3568: add arch_cpu_init() Nico Cheng
2021-12-24  3:04   ` Kever Yang
2021-10-26  8:09 ` [PATCH v3 0/3] Add SPL build support for RK3568 Peter Robinson
2021-10-26 11:24   ` nico.cheng [this message]
2021-10-26 13:20   ` Kever Yang

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=202110261924508927234@rock-chips.com \
    --to=nico.cheng@rock-chips.com \
    --cc=chenjh@rock-chips.com \
    --cc=jason.zhu@rock-chips.com \
    --cc=kever.yang@rock-chips.com \
    --cc=pbrobinson@gmail.com \
    --cc=philipp.tomsich@vrull.eu \
    --cc=sjg@chromium.org \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    --cc=yamada.masahiro@socionext.com \
    --cc=yifeng.zhao@rock-chips.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