summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
...
* conf/machine: fix use of screen and touchscreen machine featuresDenys Dmytriyenko2023-02-245-6/+4
| | | | | | | | Some machine configs didn't specify their use of screen and touchscreen machine features correctly, fix them. Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: Fallback to software renderingRyan Eatmon2023-02-244-4/+4
| | | | | | | | | | | While we are working to update our platforms to support Weston 10 and beyond, we are falling back to software rendering for platforms that do not currently have a solution for GPU drivers (namely the boards that use SGX). Signed-off-by: Ryan Eatmon <reatmon@ti.com> Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* meta-ti-bsp: machine: set SGX display controller aliasRandolph Sapp2023-02-243-0/+9
| | | | | | | | | Set SGX display controller alias variables accordingly, as SGX has a few different aliases across platforms. Signed-off-by: Randolph Sapp <rs@ti.com> Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* meta-ti-bsp: machine: remove default preferences for egl,gles,gbmRandolph Sapp2023-02-249-34/+0
| | | | | | | | | | | Remove default preferences for virtual/egl, virtual/libgles and virtual/libgbm from machine configs to follow the new dependency chains via mesa in oder to support accelerated and software-rendered graphics, which is selected by virtual/gpudriver preference. Signed-off-by: Randolph Sapp <rs@ti.com> Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* meta-ti-bsp: graphics: Resolve dependency chainRandolph Sapp2023-02-248-113/+105
| | | | | | | | | | Patched mesa will now be configured based on what virtual/gpudriver preferred provider is selected. The gpu drivers will now runtime recommend the associated UM components. Signed-off-by: Randolph Sapp <rs@ti.com> Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* mesa: locally overlay 22.0-specific patches from oe-core/kirkstoneDenys Dmytriyenko2023-02-246-0/+367
| | | | | | | | | | Locally overlay verbatim copies of mesa 22.0 patches from oe-core/kirkstone, so the same codebase works in kirkstone and master. Since upstream version of mesa in master is now 22.3 and no longer carries these patches, but they are still needed for 22.0-based PVR fork of mesa used with Rogue driver. Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* Revert "meta-ti-bsp: graphics: Resolve dependency chain"Denys Dmytriyenko2023-02-219-97/+141
| | | | | | | | | Merged by accident. This reverts commit 15417ca726f75881a2c51c08d258ea923803cbb9. Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* Revert "meta-ti-bsp: machine: Remove all gpu features"Denys Dmytriyenko2023-02-219-5/+45
| | | | | | | | | Merged by accident. This reverts commit 51bb56b74cd2e7f7e922cce84a023f669291ef00. Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* Revert "meta-ti-bsp: machine: Attempt to update DC alias"Denys Dmytriyenko2023-02-213-9/+0
| | | | | | | | | Merged by accident. This reverts commit 0dd6a86b9a20bc1117d19bec3e642602b6c54b8c. Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* Revert "conf: machine: Fallback to software rendering"Denys Dmytriyenko2023-02-214-4/+4
| | | | | | | | | Merged by accident. This reverts commit 5ae790999e762063446ec4623693eecd8ecd6be9. Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: Fallback to software renderingRyan Eatmon2023-02-154-4/+4
| | | | | | | | | While we are working to update our platforms to support Weston 10 and beyond, we are falling back to software rendering for platforms that do not currently have a solution for GPU drivers (namely the boards that use SGX). Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* meta-ti-bsp: machine: Attempt to update DC aliasRandolph Sapp2023-02-153-0/+9
| | | | | | | | | Attempt to update the SGX display controller alias variable according to what Andrew told me. SGX apparently had a few different aliases across platforms. Signed-off-by: Randolph Sapp <rs@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* meta-ti-bsp: machine: Remove all gpu featuresRandolph Sapp2023-02-159-45/+5
| | | | | | | | | Remove all gpu machine features and instead rely on the new dependency chain for resolving gpu dependencies. Set preferred providers for virtual/gpudriver where needed. Signed-off-by: Randolph Sapp <rs@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* meta-ti-bsp: graphics: Resolve dependency chainRandolph Sapp2023-02-1510-142/+129
| | | | | | | | | Patched mesa will now be configured based on what virtual/gpudriver preferred provider is selected. The gpu drivers will now runtime recommend the associated um components. Signed-off-by: Randolph Sapp <rs@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf/machine/k3r5.inc: update bootflow linksDenys Dmytriyenko2023-02-151-2/+3
| | | | | | | | | Original READMEs with bootflows were reworked and moved to a dedicated doc/ folder in more recent U-boot versions. Update links in the k3r5 config file accordingly to provide some basic explanation of K3 bootflows. Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* uio-module-drv: Remove deprecated uio-module-drvAndrew Davis2023-02-1510-1192/+0
| | | | | | | | | | UIO drivers are generally frowned upon in the community, and for PRU we now have much better alternatives in RProc, RPmsg, and PRU-Consumer. Let's not send the wrong message by continuing to support this crufty interface. Remove the kernel module, DTBs, and test recipe. Signed-off-by: Andrew Davis <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* meta-ti-bsp: add BeagleBone AI-64 supportDenys Dmytriyenko2023-01-315-0/+153
| | | | | | | | | | | | | BeagleBone AI-64 (https://beagleboard.org/ai-64) uses Texas Instruments Jacinto TDA4VM/J721e SoC. Officially BeagleBone AI-64 supports Debian Linux and builds its BSP on top of meta-ti and TI SDK, but adds custom DTBs and DTBO overlays, plus integrates other drivers and features. Let's add corresponding recipes for beagleboard.org kernel and u-boot along with the BeagleBone AI-64 machine config. Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* ti-sgx-ddk-um: use udev for userspace initializationMatthias Schiffer2023-01-312-1/+23
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The ti-sgx-ddk driver requires an additional userspace initialization step after the kernel module has probed the device. Without this initialization, no EGL context can be created and Weston etc. will fail to start. The driver package contains an init script, but this does not work on pure systemd-based systems without sysvinit compat support (as provided by the systemd-compat-units package). Introduce an enabled-by-default PACKAGECONFIG that installs a udev rule instead to run the init command automatically when the driver is loaded, solving the issue without depending on a specific init system. On builds without udev, this PACKAGECONFIG can be disabled, reverting to the old init script-based solution. udev reports several events when the pvrsrvkm module is loaded: - add event for the kernel module - add events for two DRM devices - bind event for the GPU platform device The DRM devices aren't nice to match on, and the kernel module add is too early to run `pvrsrvctl --start`, so we trigger on the platform device bind. Tested with Weston 9.0.0 on the AM65x-based TQ-Systems MBa65xx. Signed-off-by: Matthias Schiffer <matthias.schiffer@ew.tq-group.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* treewide: replace leftover git://git.ti.comMatthias Schiffer2023-01-312-2/+2
| | | | | | | | These URIs have been updated in dunfell, but two instances were forgotten in kirkstone/master. Signed-off-by: Matthias Schiffer <matthias.schiffer@ew.tq-group.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* ti-sci-fw: sets TI_K3_SECDEV_INSTALL_DIR default valueJose Quaresma2023-01-311-0/+2
| | | | | | | | | | The TI_K3_SECDEV_INSTALL_DIR is defined on the meta-ti-extras layer so when the layer is not used the variable is undefined. For such cases we can use default value that is the same defined on the recipes-ti/includes/ti-paths.inc Signed-off-by: Jose Quaresma <jose.quaresma@foundries.io> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* ti-k3-secdev: sets TI_K3_SECDEV_INSTALL_DIR_RECIPE default valueJose Quaresma2023-01-311-0/+2
| | | | | | | | | | | The TI_K3_SECDEV_INSTALL_DIR_RECIPE is defined on the meta-ti-extras layer so when the layer is not used the variable is undefined. For such cases we can use default value that is the same defined on the recipes-ti/includes/ti-paths.inc Signed-off-by: Jose Quaresma <jose.quaresma@foundries.io> Acked-by: Andrew Davis <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* ti-k3-secdev: move from meta-ti-extras to meta-ti-bspJose Quaresma2023-01-311-1/+1
| | | | | | | | | | | | | | | | | | | | | | The meta-ti-bsp layer is still broken for K3 HS platforms. The patch [1] makes the check-layer happy again as it does not fail any more during bitbake parsing but it will be difficult for the end user to discover this dependency on meta-ti-extras. On the other side, meta-ti-extras depends on meta-ti-bsp so this is a circular dependency. Currently the layer is broken for am62xx-evm/am64xx-evm machines: | ERROR: Nothing PROVIDES 'ti-k3-secdev-native' (but mc:k3r5:/srv/oe/build/conf/../../layers/meta-ti/meta-ti-bsp/recipes-bsp/ti-sci-fw/ti-sci-fw_git.bb DEPENDS on or otherwise requires it). Close matches: | libtspi-dev-native | makedevs-native [1] - 8e43835c ti-sci-fw: make dependency on meta-ti-extras soft Signed-off-by: Jose Quaresma <jose.quaresma@foundries.io> Acked-by: Andrew Davis <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* ti-unpack: Remove update_data callRyan Eatmon2023-01-271-1/+0
| | | | | | | | | update_data() was removed from upstream bitbake, so we should remove the call from our code as well. https://github.com/openembedded/bitbake/commit/584989ed2b5af4e8799571dece0cf94f995ef14e Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: Rework do_image_wic dependenciesAndrew Davis2023-01-2015-52/+17
| | | | | | | | | | | | | | | | | | The WIC image for K3 depends on the TI-SCI firmware, on AM65x and J721e also the bootloader. Make this clear by only depending on firmware in the base k3.inc file, then adding the bootloader dependency in AM65x and J721e specific includes. Remove unneeded overrides from the evm level files. Remove do_image_tar dependencies as the tar files do not include the bootloader nor TI-SCI firmware, only the boot partition of the WIC file needs these. Signed-off-by: Andrew Davis <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com> Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: Move TFA_BOARD and OPTEEMACHINE to the SoC levelAndrew Davis2023-01-209-12/+17
| | | | | | | | | These defines are specific to a SoC, not a SoC family (K3) nor any specific board. Move these to the SoC level for all boards to be consistent with boards already doing this correctly. Signed-off-by: Andrew Davis <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: Remove OPTEEOUTPUTMACHINE definitionAndrew Davis2023-01-2010-10/+0
| | | | | | | | This was used in the base Linaro optee-os_git.bb recipe, it is no longer used, remove it from our boards. Signed-off-by: Andrew Davis <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: Remove j7 grouping and j7.incAndrew Davis2023-01-205-9/+16
| | | | | | | | | | | J7 is an unneeded level of grouping that is now causing issues and leading to mistakes when adding new J7 based platforms. Each J7x family device should use the SoC name specifically to prevent accidentally adding or removing features that are not meant for the new SoC. Signed-off-by: Andrew Davis <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: Use new J7 SoC names over specific board namesAndrew Davis2023-01-208-35/+34
| | | | | | | | | | | | | | | | Now that we have SoC names, we can avoid adding features based on the board name. We expect folks to create their own boards based on these SoCs, and so using the TI made EVM board name everywhere adds extra churn when adding a new board. Plus it is more correct for most of these features as they depend on the SoC, not on the EVM board. One other thing we do here is to not use the generic "j7" name, the current and future J7 devices are far to feature diverse to group at this level. Grouping like that will lead to the wrong things getting enabled as new J7 SoCs are added. Signed-off-by: Andrew Davis <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: j784s4: Move common defines into j784s4.incAndrew Davis2023-01-202-3/+11
| | | | | | | | | Like we do with J721e, J7200, and J721s2, use a SoC header include file to define common properties. This eases adding new boards based on these SoC. Signed-off-by: Andrew Davis <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: Remove multi-certificate image commentAndrew Davis2023-01-201-2/+0
| | | | | | | Multi-cert is already now the default, no need to add a comment on that. Signed-off-by: Andrew Davis <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* meta-ti-bsp: Move legacy HS signing classes into this layerAndrew Davis2023-01-206-0/+932
| | | | | | | | | These were in the meta-arago layer, but any distro should be able to run on HS devices. So move the classes and setup to the BSP layer. Signed-off-by: Andrew Davis <afd@ti.com> Reviewed-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* ti-sgx-ddk-um: Update SRCREV for Kirkstone supportAndrew Davis2023-01-201-4/+5
| | | | | Signed-off-by: Andrew Davis <afd@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* meta-ti-bsp: Add am57xx.inc allowing use of SoC name over full EVM nameAndrew Davis2023-01-209-18/+17
| | | | | | | | | | In many spots we have to use the full EVM name for each EVM using the AM57x SoC leading to missed features on some EVMs. Add the am57xx name so we can generically add for AM57x. Signed-off-by: Andrew Davis <afd@ti.com> Reviewed-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* ti-sci-fw: make dependency on meta-ti-extras softDenys Dmytriyenko2022-12-011-2/+2
| | | | | | | | | | | | | | | | | | Replace "require" with "include" to load ti-paths.inc and not break parsing when meta-ti-extras is not in the BBLAYERS list. As ti-paths.inc is only needed to define TI_K3_SECDEV_INSTALL_DIR for ti-k3-secdev when TI_SECURE_DEV_PKG_K3 is not set and building for K3 HS platforms. Since ti-k3-secdev resides in meta-ti-extras, the soft dependency will still work fine and give a build error "Nothing PROVIDES 'ti-k3-secdev-native'" when it is needed. Also, since TI_K3_SECDEV_INSTALL_DIR can now be undefined, use d.getVar() to access it ensuring it doesn't break the condition. Reported-by: Daniel Díaz <mrchapp@gmail.com> Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf/machine/omapl138: correct few of the machine settingsDenys Dmytriyenko2022-11-157-35/+13
| | | | | | | | | | | | Cleanup and unify again - omapl138-lcdk is the only platform supported in the OMAP-L1 family. Plus there's no longer DaVinci family with corresponding settings. Adjust accordingly. Please note, there's currently a bug building Rust on ARMv5 platforms: https://bugzilla.yoctoproject.org/show_bug.cgi?id=14967 Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* optee: make bbappends version-specificDenys Dmytriyenko2022-11-102-0/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Kirkstone branch of meta-arm comes with 2 versions of optee-os and optee-client - 3.14 and 3.16. They have different dependencies and slightly different build flows. In our bbappends we bump SRCREV to latest version for newer platform support and also update PV to indicate the correct version. While bbappends are expected to be applied against newer 3.16 version of the recipes, they use wildcard versioning and are not version-specific. That results in bbappends applied to both versions of the recipes and PV set to be the same, while the content is different. At this point bitbake can pick up any version of the base recipe and if it gets 3.14 to apply the bbappend, the build fails due to that version being too old and have different dependencies and build flows. Making bbappends version-specific avoids the problem. Alternatively, a whole recipe of the required newer version could be added, instead of using bbappends. Also, this is specific to Kirkstone, where meta-arm provides two versions of optee - 3.14 and 3.16. In Lagdale and master only a single 3.18 version of optee is provided. Another hacky approach would be to not bump PV and let it be set by the base recipe. That would avoid the build issue and keep bbappends version-agnostic across branches, but result in incorrect versioning of the binary packages, which might be confusing. Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* cmem-mod: Remove CMEM kernel moduleAndrew Davis2022-11-1013-431/+0
| | | | | | | | | | | | | | CMEM has been deprecated for removal for some time now. All users should have migrated to the Linux upstream DMA-BUF Heaps framework. Remove CMEM. We only remove the kernel module part in this patch to prevent builds from breaking in the meta-arago layer due to dependencies on the CMEM library. These packages should either be updated or disabled. After that we will remove the library. Signed-off-by: Andrew Davis <afd@ti.com> Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* optee-os: Upgrade to upstream 3.19.0Praneeth Bajjuri2022-11-101-2/+2
| | | | | | | | | Update to the latest upstream master which is 3.19.0. Signed-off-by: Praneeth Bajjuri <praneeth@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com> Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* ti-img-rogue-driver: Bump the source revisionRandolph Sapp2022-11-101-1/+1
| | | | | | | | | | | | | Bump the source revision for the rogue pvr kernel module. Source changelog: - A hack was added to increase stability on J7 platforms while we are looking into a proper fix for cache coherency issues in this module Signed-off-by: Randolph Sapp <rs@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com> Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* ti-sci-fw: use getVar() to check if TI_SECURE_DEV_PKG_K3 is definedDenys Dmytriyenko2022-11-101-1/+1
| | | | | | | | | Otherwise undefined variable is returned literally as ${TI_SECURE_DEV_PKG_K3} and the condition won't work. Cc: Andrew Davis <afd@ti.com> Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* ti-k3-secdev: include ti-paths.incDenys Dmytriyenko2022-11-101-0/+2
| | | | | | | | | Include ti-paths.inc so TI_K3_SECDEV_INSTALL_DIR_RECIPE gets defined and artifacts are installed in the correct location. Cc: Andrew Davis <afd@ti.com> Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* linux-ti-staging: update to the latestDenys Dmytriyenko2022-11-102-4/+4
| | | | | | | This matches current version in Dunfell. Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* u-boot-ti-staging: update to the latestDenys Dmytriyenko2022-11-101-1/+1
| | | | | | | This matches current version in Dunfell. Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* ti-linux-fw: update to the latestDenys Dmytriyenko2022-11-101-2/+2
| | | | | | | This matches current version in Dunfell. Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* cnm-wave-fw: update firmware name to wave521c_k3_codec_fw.binRyan Eatmon2022-11-101-3/+1
| | | | | | | | | | | | | update firmware name to wave521c_k3_codec_fw.bin to align with linux-firmware main branch. the following patch is part of ti-linux-firmware thru mainline sync. commit 48407ffd ("cnm: update chips&media wave521c firmware.") Signed-off-by: Praneeth Bajjuri <praneeth@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com> Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* optee-os: Enable TRNG driver as OP-TEE support is addedJayesh Choudhary2022-11-101-1/+0
| | | | | | | | | | OP-TEE upstream now has support for sa3ul for j721s2 platform. Re-enable the trng driver which was disabled earlier. Signed-off-by: Jayesh Choudhary <j-choudhary@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com> Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: j721s2: Add OP-TEE flavourJayesh Choudhary2022-11-101-0/+1
| | | | | | | | | | | Change the OP-TEE flavour from default k3-j721e to k3-j784s4 as sa3ul support for j784s4 is upstreamed in OP-TEE and we can use the same settings in j721s2 to access TRNG. Signed-off-by: Jayesh Choudhary <j-choudhary@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com> Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: j784s4: Add OP-TEE flavourJayesh Choudhary2022-11-101-0/+1
| | | | | | | | | | | Add the new OP-TEE flavour for J784S4 instead of default k3-j721e. The TI-SCI ID for MCU domain sa2ul/sa3ul are not the same for J721E and J784S4. So a new flavour is added in upstream OP-TEE. Signed-off-by: Jayesh Choudhary <j-choudhary@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com> Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* optee-os: Update SRCREV for OP-TEE TRNG in J784S4Jayesh Choudhary2022-11-101-1/+1
| | | | | | | | | | Update the SRCREV to the commit when sa3ul support was added in upstream OP-TEE for J784S4 platform to access rng. Signed-off-by: Jayesh Choudhary <j-choudhary@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com> Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* j721s2 and j784s4: Correct serial console deviceRyan Eatmon2022-11-102-2/+2
| | | | | | | | | | | | | Serial console in J721S2/J784S4 EVM config was set to ttyS10. It should be ttyS2. This caused sysv based systems (eg, tiny) to apparently hang because of no login prompt. This didn't show up as a problem on systemd systems (eg, default) because systemd will automatically setup a serial tty with the console option passed in on the kernel command line (using console=...), which U-Boot correctly passes in as ttyS2 for J721S2/J784S4. Signed-off-by: Jonathan Humphreys <j-humphreys@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com> Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2025-08-09 05:43:08 +0000