| Message ID | 20240927-rk35-upstream-tf-a-v1-0-e3911342113f@cherry.de |
|---|---|
| Headers | show |
| Series | rk35xx: add support for upstream TF-A | expand |
On 9/27/24 2:59 PM, Quentin Schulz wrote: > Upstream TF-A (> 2.11; no release yet) has gained initial support for > the RK356x and RK3588 so one may be interested in using it. > > The default still is to use the downstream blob but the option is now > given to the user who can simply change the value of > PREFERRED_PROVIDER_trusted-firmware-a in their own configuration file in > order to use upstream TF-A. > > This depends on two different patch series that have yet to be merged: > - https://lore.kernel.org/yocto-patches/20240927-rkbin-split-recipes-v1-0-0f4a9b0cbf56@cherry.de/ > for meta-rockchip > - https://lore.kernel.org/yocto-meta-arm/20240927-tf-a-master-v1-1-733c925c80e4@cherry.de/ > for meta-arm For your information, this one's been merged into styhead and master branch already. I forgot to mention that RK356x support is known to be incomplete, c.f. https://review.trustedfirmware.org/c/TF-A/trusted-firmware-a/+/31265 for fixes that hopefully will make it in time for v2.12 :) Cheers, Quentin
Hi Trevor, Gentle ping to make sure this does get forgotten :) Anything I can do to make the review easier for you? Cheers, Quentin On 9/27/24 2:59 PM, Quentin Schulz wrote: > Upstream TF-A (> 2.11; no release yet) has gained initial support for > the RK356x and RK3588 so one may be interested in using it. > > The default still is to use the downstream blob but the option is now > given to the user who can simply change the value of > PREFERRED_PROVIDER_trusted-firmware-a in their own configuration file in > order to use upstream TF-A. > > This depends on two different patch series that have yet to be merged: > - https://lore.kernel.org/yocto-patches/20240927-rkbin-split-recipes-v1-0-0f4a9b0cbf56@cherry.de/ > for meta-rockchip > - https://lore.kernel.org/yocto-meta-arm/20240927-tf-a-master-v1-1-733c925c80e4@cherry.de/ > for meta-arm > > Only the RK3588 support was build and boot tested as I don't own any > RK356x board. > > Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de> > --- > Quentin Schulz (2): > rk356x: add support for upstream TF-A > rk3588(s): add support for upstream TF-A > > conf/machine/include/rk3566.inc | 3 +++ > conf/machine/include/rk3568.inc | 3 +++ > conf/machine/include/rk3588s.inc | 3 +++ > .../trusted-firmware-a_%.bbappend | 23 ++++++++++++++++++++++ > 4 files changed, 32 insertions(+) > --- > base-commit: 24a411a17f389650c4cea38bef1f9279117fab8e > change-id: 20240927-rk35-upstream-tf-a-356760495fc1 > prerequisite-change-id: 20240927-rkbin-split-recipes-61503f078ab6:v1 > prerequisite-patch-id: 852459a4ef85dcfa74407f5455af93ac5e2ab3ee > prerequisite-patch-id: 0ed848000063d5b8b9dbc02f63e09a199e90bd64 > prerequisite-patch-id: f665b620ee911de701142439dd00566dd12131d2 > > Best regards,
Hi all, On 9/27/24 2:59 PM, Quentin Schulz wrote: > Upstream TF-A (> 2.11; no release yet) has gained initial support for > the RK356x and RK3588 so one may be interested in using it. > > The default still is to use the downstream blob but the option is now > given to the user who can simply change the value of > PREFERRED_PROVIDER_trusted-firmware-a in their own configuration file in > order to use upstream TF-A. > > This depends on two different patch series that have yet to be merged: > - https://lore.kernel.org/yocto-patches/20240927-rkbin-split-recipes-v1-0-0f4a9b0cbf56@cherry.de/ > for meta-rockchip > - https://lore.kernel.org/yocto-meta-arm/20240927-tf-a-master-v1-1-733c925c80e4@cherry.de/ > for meta-arm > > Only the RK3588 support was build and boot tested as I don't own any > RK356x board. > > Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de> Just because it's unusual for Trevor to not send a mail saying it was merged, I do it myself here: this was merged into master. Thanks Trevor! Quentin
Upstream TF-A (> 2.11; no release yet) has gained initial support for the RK356x and RK3588 so one may be interested in using it. The default still is to use the downstream blob but the option is now given to the user who can simply change the value of PREFERRED_PROVIDER_trusted-firmware-a in their own configuration file in order to use upstream TF-A. This depends on two different patch series that have yet to be merged: - https://lore.kernel.org/yocto-patches/20240927-rkbin-split-recipes-v1-0-0f4a9b0cbf56@cherry.de/ for meta-rockchip - https://lore.kernel.org/yocto-meta-arm/20240927-tf-a-master-v1-1-733c925c80e4@cherry.de/ for meta-arm Only the RK3588 support was build and boot tested as I don't own any RK356x board. Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de> --- Quentin Schulz (2): rk356x: add support for upstream TF-A rk3588(s): add support for upstream TF-A conf/machine/include/rk3566.inc | 3 +++ conf/machine/include/rk3568.inc | 3 +++ conf/machine/include/rk3588s.inc | 3 +++ .../trusted-firmware-a_%.bbappend | 23 ++++++++++++++++++++++ 4 files changed, 32 insertions(+) --- base-commit: 24a411a17f389650c4cea38bef1f9279117fab8e change-id: 20240927-rk35-upstream-tf-a-356760495fc1 prerequisite-change-id: 20240927-rkbin-split-recipes-61503f078ab6:v1 prerequisite-patch-id: 852459a4ef85dcfa74407f5455af93ac5e2ab3ee prerequisite-patch-id: 0ed848000063d5b8b9dbc02f63e09a199e90bd64 prerequisite-patch-id: f665b620ee911de701142439dd00566dd12131d2 Best regards,