From: "Yann Dirson" <yann.dirson@blade-group.com>
To: yocto@yoctoproject.org
Cc: twoerner@gmail.com, Yann Dirson <yann@blade-group.com>
Subject: [meta-rockchip][PATCH 0/6] WIP/RFC OP-TEE support for ARM and rk3399
Date: Tue, 13 Apr 2021 17:43:10 +0200 [thread overview]
Message-ID: <20210413154316.3666881-1-yann@blade-group.com> (raw)
From: Yann Dirson <yann@blade-group.com>
This tries to provide a generic framework for easier OP-TEE support in
BSP layers. It would probably make sense to have the generic parts in
meta-arm when they are finalized. Today the kernel/dts handling is
still not properly done, and patches to fix rk3399 support in OP-TEE
have not yet been merged upstream, and I'm mostly posting this to
gather comments on the whole idea.
Yann Dirson (6):
optee: condition for "optee" DISTRO_FEATURE
truster-firmware-a: include optee support when requested by
DISTRO_FEATURE
u-boot: include optee-os as BL32 when requested by DISTRO_FEATURE
WIP optee-os: rk3399 support
WIP nanopi-m4: declare OP-TEE presence in devicetree
WIP kernel config feature for OP-TEE activation
conf/machine/include/rk3399.inc | 2 +
.../trusted-firmware-a_%.bbappend | 19 ++++++++
recipes-bsp/u-boot/u-boot%.bbappend | 14 ++++++
.../0001-nanopi-declare-optee-presence.patch | 30 ++++++++++++
recipes-kernel/linux/files/bsp/tee.cfg | 2 +
recipes-kernel/linux/linux-yocto%.bbappend | 1 +
...399-enable-serial-console-by-default.patch | 46 +++++++++++++++++++
.../optee/files/rk3399-boot-fix.patch | 13 ++++++
recipes-security/optee/optee%.bbappend | 4 ++
recipes-security/optee/optee-os_%.bbappend | 9 ++++
10 files changed, 140 insertions(+)
create mode 100644 recipes-kernel/linux/files/0001-nanopi-declare-optee-presence.patch
create mode 100644 recipes-kernel/linux/files/bsp/tee.cfg
create mode 100644 recipes-security/optee/files/0001-rk3399-enable-serial-console-by-default.patch
create mode 100644 recipes-security/optee/files/rk3399-boot-fix.patch
create mode 100644 recipes-security/optee/optee%.bbappend
create mode 100644 recipes-security/optee/optee-os_%.bbappend
--
2.30.2
next reply other threads:[~2021-04-13 15:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-13 15:43 Yann Dirson [this message]
2021-04-13 15:43 ` [meta-rockchip][PATCH 1/6] optee: condition for "optee" DISTRO_FEATURE Yann Dirson
2021-04-13 15:43 ` [meta-rockchip][PATCH 2/6] truster-firmware-a: include optee support when requested by DISTRO_FEATURE Yann Dirson
2021-04-13 15:43 ` [meta-rockchip][PATCH 3/6] u-boot: include optee-os as BL32 " Yann Dirson
2021-04-13 15:43 ` [meta-rockchip][PATCH 4/6] WIP optee-os: rk3399 support Yann Dirson
2021-04-13 15:43 ` [meta-rockchip][PATCH 5/6] WIP nanopi-m4: declare OP-TEE presence in devicetree Yann Dirson
2021-04-13 15:43 ` [meta-rockchip][PATCH 6/6] WIP kernel config feature for OP-TEE activation Yann Dirson
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=20210413154316.3666881-1-yann@blade-group.com \
--to=yann.dirson@blade-group.com \
--cc=twoerner@gmail.com \
--cc=yann@blade-group.com \
--cc=yocto@yoctoproject.org \
/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.