summaryrefslogtreecommitdiffstats
path: root/meta-ti-bsp/conf/machine
Commit message (Collapse)AuthorAgeFilesLines
...
* conf/machine: rename beagleplay machine to beagleplay-tiDenys Dmytriyenko2024-12-162-0/+0
| | | | | | | | | | | | | BeaglePlay is officially supported by TI "ti-6_6" BSP and is part of the TI-SDK releases. Switching BSP to BeagleBoard.org "bb_org" settings for the same machine is possible within the same layer. But having different machine configs for the same machine name in multiple layers can be confusing and prone to errors. Hence rename the config to indicate BeaglePlay with official TI support in order to re-use the canonical name in a separate layer. Signed-off-by: Denys Dmytriyenko <denys@konsulko.com>
* conf: machine: omap-a15.inc: include ipu1 firmware in the boot partitionAniket Limaye2024-12-131-1/+2
| | | | | | | | | | Early Boot of remote processors is supported at the SPL stage of the bootloader. Currently, SPL looks for the remoteproc firmwares in the boot partition. Therefore, add the rproc firmware to the boot partition of wic images. Signed-off-by: Aniket Limaye <a-limaye@ti.com>
* conf: machine: am62xx-lp-evm: Add PWM overlaysJudith Mendez2024-12-061-0/+2
| | | | | | | Add the PWM overlays: k3-am62x-sk-dmtimer-pwm and k3-am62x-sk-pwm for AM62 LP SK. Signed-off-by: Judith Mendez <jm@ti.com>
* conf: machine: am62pxx: Pick overlays for V3Link camerasRishikesh Donadkar2024-11-211-0/+1
| | | | | | | | | | | | | The V3Link camera fusion board [1] can be used to connect upto 4 OV5640 sensors to SK-AM62A. Overlays for interfacing OV5640 sensor with V3Link are built as part of the TI linux kernel. Pick these in the BSP filesystem. [1]: https://www.arducam.com/product/arducam-v3link-camera-kit-for-ti-development-boards/ Signed-off-by: Rishikesh Donadkar <r-donadkar@ti.com> Acked-by: Chirag Shilwant <c-shilwant@ti.com>
* sgx: bump version for kernel 6.6 / mesa 23.2.1Randolph Sapp2024-11-071-1/+3
| | | | | | | | | | Bump versions of mesa-pvr and ti-sgx-ddk-km to support SGX with kernel 6.6 and the same version of mesa rogue is using. Enable SGX by default in the 6.6 BSP provider section logic. Signed-off-by: Randolph Sapp <rs@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* ti-bsp: Tighten up versions for PREFERRED_VERSIONRyan Eatmon2024-10-311-3/+3
| | | | | | | | | | PREFERRED_VERSION matches against the PV in the recipe, not against the file name. With the upcoming 6.12, the 6.1 kernel version string was a little too loose. The "6.1%" could glob onto the 6.12 recipe. Take this time to also clean up a couple of the other versions and narrow them down. Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: Add support for bsp-ti-6_12 in beagleplayChirag Shilwant2024-10-242-0/+2
| | | | | | | | Add bsp-ti-6_12 overrides in A53 & R5 machine configuration to ensure it picks the appropriate u-boot configs for beagleplay Signed-off-by: Chirag Shilwant <c-shilwant@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* uboot-ti-next: Add new recipe to track master-nextRyan Eatmon2024-10-221-1/+1
| | | | | | | | | Our upstream testing needs to point to both master and master-next and we need two different recipes to track that. This recipe mirrors the linux-ti-next recipe and points to the master-next branch for the latest bleeding edge changes. Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* linux-ti-mainline: Update to version: v6.11LCPD Automation Script2024-10-197-0/+11
| | | | | | | | | | | | | | | | | | | | | | | | | | Updated the value(s) for: am57xx-evm: KERNEL_DEVICETREE am62axx-evm: KERNEL_DEVICETREE am62pxx-evm: KERNEL_DEVICETREE am62xx-evm: KERNEL_DEVICETREE am62xx-lp-evm: KERNEL_DEVICETREE am68-sk: KERNEL_DEVICETREE am69-sk: KERNEL_DEVICETREE beagleplay: KERNEL_DEVICETREE am64xx-evm: KERNEL_DEVICETREE am65xx-evm: KERNEL_DEVICETREE am335x-evm: KERNEL_DEVICETREE am437x-evm: KERNEL_DEVICETREE j7200-evm: KERNEL_DEVICETREE j721e-evm: KERNEL_DEVICETREE j721e-sk: KERNEL_DEVICETREE j721s2-evm: KERNEL_DEVICETREE j722s-evm: KERNEL_DEVICETREE j784s4-evm: KERNEL_DEVICETREE linux-ti-mainline: PV,SRCREV Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* ti-bsp: Add RT and systest supportRyan Eatmon2024-10-091-0/+2
| | | | | | | | | | | | We were missing controlling the versions for linux-ti-staging-rt and linux-ti-staging-systest using the BSP framework. Since the PREFERRED_VERSION is not tied to the virtual/kernel we need two additional settings for those alternate kernel package names. For BSPs that do not have the -rt and -systest recipes then the two new variable settings should effectively be ignored and cause no issues. Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* ti-bsp: Fix copy/paste error for bsp-ti-6_12 settingRyan Eatmon2024-10-081-1/+1
| | | | Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* ti-bsp: Add ti-6_12Ryan Eatmon2024-10-041-1/+14
| | | | | | Add new BSP for the 6.12 kernel and u-boot 2024.10 versions. Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: Remove multiconfig compulsion for k3 platformscicd.master.202409240100cicd.master.202409200100cicd.master.202409180100cicd.master.202409170100Chirag Shilwant2024-09-1316-3/+31
| | | | | | | | | | | | | | | - While implementing k3.inc, there was an assumption that all k3 based TI SOC's would always have a Cortex-R5F core [1]. This assumption is not true. - Hence, create a new mc_k3r5 include file & move the multiconfig dependencies to it. Also, include this file only in those k3 platforms which needs the R5 multiconfig support. [1]: https://git.ti.com/cgit/arago-project/meta-ti/commit/conf/machine/include/k3.inc?h=scarthgap&id=f814840465358a6b5429ad20165742ac6e6e6a29 Signed-off-by: Chirag Shilwant <c-shilwant@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: omapl138-lcdk: Update KERNEL_DEVICETREERyan Eatmon2024-08-041-2/+2
| | | | | | | Update the entry for KERNEL_DEVICETREE to match what is in the 6.10 kernel. Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* linux-ti-mainline: Update to version: v6.10LCPD Automation Script2024-08-0117-14/+120
| | | | | | | | | | | | | | | | | | | | | | | | | | Updated the value(s) for: am57xx-evm: KERNEL_DEVICETREE am62axx-evm: KERNEL_DEVICETREE am62pxx-evm: KERNEL_DEVICETREE am62xx-evm: KERNEL_DEVICETREE am62xx-lp-evm: KERNEL_DEVICETREE am68-sk: KERNEL_DEVICETREE am69-sk: KERNEL_DEVICETREE beagleplay: KERNEL_DEVICETREE am64xx-evm: KERNEL_DEVICETREE am65xx-evm: KERNEL_DEVICETREE am335x-evm: KERNEL_DEVICETREE am437x-evm: KERNEL_DEVICETREE j7200-evm: KERNEL_DEVICETREE j721e-evm: KERNEL_DEVICETREE j721e-sk: KERNEL_DEVICETREE j721s2-evm: KERNEL_DEVICETREE j722s-evm: KERNEL_DEVICETREE j784s4-evm: KERNEL_DEVICETREE linux-ti-mainline: PV,SRCREV Signed-off-by: LCPD Automation Script <lcpdbld@list.ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* meta-ti-bsp: j742s2: add Rogue GPU driver to machine definitionAniket Limaye2024-07-191-1/+1
| | | | | | | | Add ti-img-rogue-driver as the preferred provider and enable the gpu driver in the image. Signed-off-by: Aniket Limaye <a-limaye@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* meta-ti-bsp: Add support for j742s2-evmAniket Limaye2024-07-193-0/+52
| | | | | | | | | - Add A72 and R5 machine configurations for j742s2-evm - Add firmware overrides. - Add u-boot overrides. Signed-off-by: Aniket Limaye <a-limaye@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: j722s: Update IMAGE_BOOT_FILES for mainline buildsRyan Eatmon2024-07-171-0/+1
| | | | | | | As this is still a new platform, the bsp-mainline also does not have the hs-fs boot files. Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* Revert "conf: machine: am62*-evm-k3r5.conf: apply fragment for enabling USB DFU"Ryan Eatmon2024-07-125-9/+1
| | | | | | | | This reverts commit fa94effc26a8678a5400291a3ca0ef1000eea7b1. There are boot issues with SD card booting with this change. Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: am62*-evm-k3r5.conf: apply fragment for enabling USB DFUSiddharth Vadapalli2024-07-095-1/+9
| | | | | | | | | | The config fragment "am62x_r5_usbdfu.config" is applicable to AM62x, AM62x-SIP, AM62x-LP-EVM, AM62Ax and AM62Px devices and enables USB DFU boot support at the R5 stage of boot. Signed-off-by: Siddharth Vadapalli <s-vadapalli@ti.com> Acked-by: Chirag Shilwant <c-shilwant@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: Update am62pxx-evm for multi-BSP supportChirag Shilwant2024-07-041-2/+4
| | | | | | | | | | | | | | | | | | - In ti-u-boot-2024.04, the config fragment to disable splashscreen is now renamed to am62x_evm_prune_splashscreen.config [1] Hence, update UBOOT_CONFIG_FRAGMENTS for the same. - Add UBOOT_CONFIG_FRAGMENTS:bsp-ti-6_1 which ensures that am62pxx-evm machine configuration still supports Display Cluster usecase [2] with ti-u-boot-2023.04 [1]: https://git.ti.com/cgit/ti-u-boot/ti-u-boot/commit/?h=ti-u-boot-2024.04&id=981eddc83dfdbbf176a4984977f9779dc1d56f87 [2]: https://software-dl.ti.com/mcu-plus-sdk/esd/AM62PX/09_01_00_39/exports/docs/api_guide_am62px/EXAMPLES_DRIVERS_DSS_DISPLAY_SHARE.html Signed-off-by: Chirag Shilwant <c-shilwant@ti.com> Reviewed-by: Devarsh Thakkar <devarsht@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: am69-sk: Pick overlays for IMX219 and FPD-LinkVaishnav Achath2024-07-011-0/+3
| | | | | | | | | | J721E SK, AM68 SK and AM69 SK have similar connectivity for CSI2 RPi connector and the same overlays can be reused, thus pick the J721E SK CSI2 IMX219, fusion overlay and AM68 SK V3Link fusion overlay for AM69 SK also. Signed-off-by: Vaishnav Achath <vaishnav.a@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: am68-sk: Pick overlays for IMX219 and FPD-LinkVaishnav Achath2024-07-011-0/+2
| | | | | | | | | J721E SK and AM68 SK have similar connectivity for CSI2 RPi connector and the same overlays can be reused, thus pick the J721E SK CSI2 IMX219 and fusion overlays for AM68 SK also. Signed-off-by: Vaishnav Achath <vaishnav.a@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: j784s4-evm: Pick overlays for CSI2 and FPD-LinkVaishnav Achath2024-07-011-0/+2
| | | | | | | | | J784S4 and J721S2 EVM has similar connectivity for MIPI CSI2 connector and the same overlays can be reused, thus pick the J721S2 CSI2 OV5640 and J721S2 EVM fusion overlays for J784S4. Signed-off-by: Vaishnav Achath <vaishnav.a@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf/machine, ti-bsp: Add support for next BSP providercicd.master.202406210100Ryan Eatmon2024-06-201-1/+14
| | | | | | | For our upstream testing flow we have the need to have a "next" BSP for configuring various settings based on building the latest kernel/uboot. Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* j722s: next BSP doesn't support all SR and HS variantsRyan Eatmon2024-06-201-1/+3
| | | | | | | Adjust IMAGE_BOOT_FILES list as next BSP does not support all combinations of SR1.0, HS-FS and HS-SE variants. Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* j7200: mainline BSP doesn't support all SR and HS variantsDenys Dmytriyenko2024-06-191-2/+6
| | | | | | | | | Adjust IMAGE_BOOT_FILES list as mainline BSP does not support all combinations of SR1.0, SR2.0, HS-FS and HS-SE variants. Suggested-by: Aniket Limaye <a-limaye@ti.com> Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* beaglebone-ai64: BB.org does not support all SR and HS variantsDenys Dmytriyenko2024-06-191-0/+3
| | | | | | | | Adjust IMAGE_BOOT_FILES list as BB.org BSP does not support all combinations of SR1.1, SR2.0, HS-FS and HS-SE variants, same as J721e EVM in mainline. Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: Update am62xxsip-evm for multi-BSP supportChirag Shilwant2024-06-172-0/+6
| | | | | | | | Update am62xxsip-evm machine configuration to support TI kernel 6.1 & ti-u-boot-2023.04 Signed-off-by: Chirag Shilwant <c-shilwant@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: add j721e-sk machine-configurationAniket Limaye2024-06-172-0/+27
| | | | | | | | | | | | As of commit [1] there will be a separate defconfig to build u-boot for j721e-evm and j721e-sk. Hence, introduce new yocto machine configs for j721e-sk. [1]: https://source.denx.de/u-boot/u-boot/-/commit/c9507f07a1d6c92bd1f73fd64384f8c5994be9c2 Signed-off-by: Aniket Limaye <a-limaye@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* meta-ti: remove MACHINE_KERNEL_PR globallyDenys Dmytriyenko2024-06-154-12/+0
| | | | | | | | MACHINE_KERNEL_PR is a remnant of the early OE days and hasn't been needed for quite some time. Let's finally remove it completely. Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf/machine: use the default TI BSP for BeaglePlayDenys Dmytriyenko2024-06-157-7/+8
| | | | | | | | | | | BeaglePlay gains official support from latest TI lts-6.6 baseline, so set it as the default. Other Beagle platforms will still use BB.org as default. And these defaults can still be changed with TI_PREFERRED_BSP setting in a distro config or by end user in the local.conf Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf/machine/beagle*, linux-bb.org: update for multi-BSP supportDenys Dmytriyenko2024-06-156-36/+100
| | | | | | | Update all Beagle platform configurations to support multiple BSPs. Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf/machine/j721e: some BSPs don't support all SR and HS variantsDenys Dmytriyenko2024-06-151-8/+10
| | | | | | | | Adjust IMAGE_BOOT_FILES list as some BSPs do not support all combinations of SR1.1, SR2.0, HS-FS and HS-SE variants. Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf/machine, ti-bsp: add support for multiple BSP providersDenys Dmytriyenko2024-06-1520-43/+131
| | | | | | | | | This adds a facility to define multiple supported BSPs with their own preferences for individual components, as well as lets machine configs specify conditional configurations for different BSPs. Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: Update UBOOT_MACHINE for am62xxsip-evmChirag Shilwant2024-06-152-7/+2
| | | | | | | | | | Modify the U-Boot defconfig names for A53 and R5 machine configurations based on ti-u-boot-2024.04 [1] [1]: https://git.ti.com/cgit/ti-u-boot/ti-u-boot/commit/?h=ti-u-boot-2024.04&id=df5181f8c6c41bf018ec043d565581b5d8a291c5 Signed-off-by: Chirag Shilwant <c-shilwant@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf/machine, linux-bb.org: re-org DT lists for Beagle platformsDenys Dmytriyenko2024-06-155-104/+24
| | | | | | | | | | | | | | | | | | | | | In order to be able to switch between different kernel providers, as well as different versions of kernel LTS (e.g. 6.1 vs. 6.6), let's re-organize Device Tree lists as follows: * Move all Beagle-specific DTBs and overlays into corresponding linux-bb.org recipe for now, to be used when building beagleboard.org baseline * Update KERNEL_DEVICETREE in the machine configs to only list what already exists in the upstream/mainline kernel * Update KERNEL_DEVICETREE_PREFIX to match the list when building TI baseline With this change it is now very easy to switch the kernel between providers supported by meta-ti - linux-ti-mainline, linux-ti-staging and linux-bb.org Please note that 6.6 LTS has moved to "vendored" device tree layout even for 32-bit platforms, while BB.org still uses 6.1 LTS and flat DT layout. Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: add AM68-SK machine configurationAniket Limaye2024-06-153-0/+50
| | | | | | | | | | | | | | As of commit [1] there will be a separate defconfig to build u-boot for j721s2-evm and am68-sk. Hence, introduce new yocto machine configs for am68-sk. This is done through a new am68.inc file as the am68-sk platform does not support GP. So j721s2-evm.inc is copied to am68.inc and updated accordingly. [1]: https://source.denx.de/u-boot/u-boot/-/commit/a96be9b8c05ea835d27f7c9bae03279b8bd5dcf2 Signed-off-by: Aniket Limaye <a-limaye@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* meta-ti-bsp: update BeagleBoard.org BSP to the latestDenys Dmytriyenko2024-06-152-0/+17
| | | | | | | | | * Update linux-bb.org to 6.1.80 for both 32 and 64 bit platforms * Update DTB/DTBO lists to include latest renames and additions * Re-enable vendored DTB layout by default Signed-off-by: Denys Dmytriyenko <denys@konsulko.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: Fallback to software renderingRyan Eatmon2024-06-154-4/+4
| | | | | | | | While we are working to finish our kernel migration 6.6, we are falling aback 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>
* conf: am437x-evm: Bump up max_leb_cntChirag Shilwant2024-05-141-1/+1
| | | | | | | New features added require another increase to max_leb_cnt. Signed-off-by: Chirag Shilwant <c-shilwant@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: am69-sk: Create a new am69.inc fileRyan Eatmon2024-04-302-1/+20
| | | | | | | | Reusing the j784s4.inc file presents problems as the am69-sk platform does not support GP. So copy the j784s4.inc to am69.inc and update accordingly. Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: j784s4-evm: Add k3-am69-sk dtb back inRyan Eatmon2024-04-301-0/+1
| | | | | | | | | Currently, the 6.1 kernel is the default. Removing the k3-am69-sk dtb file only applies to the 6.6 kernel. Restoring this entry so that current builds work until such time as the 6.1 kernel is removed from the recipes. Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: add AM69-SK machine configurationBeleswar Padhi2024-04-293-1/+31
| | | | | | | | | | | | | | | As of commits [1] and [2] in ti-u-boot-2024.04 and upstream respectively there is a separate defconfig to build u-boot for j784s4-evm and am69-sk Hence, introduce new yocto machine configs for am69-sk. Also remove am69 devicetree builds from the j784s4-evm conf [1]: https://git.ti.com/cgit/ti-u-boot/ti-u-boot/commit/?h=ti-u-boot-2024.04&id=8a46af7a39e6218e4de5c6195697af36201c778c [2]: https://source.denx.de/u-boot/u-boot/-/commit/740759d558e632e1540d620baadbcc46fdf24db2 Signed-off-by: Beleswar Padhi <b-padhi@ti.com> Signed-off-by: Aniket Limaye <a-limaye@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: am57/am33/am43: Add/fix DEVICETREE_FILERyan Eatmon2024-04-263-3/+7
| | | | | | | | | | | | | | | | | | The new kernel directory stucture for the DTBs is causing problems when assembing the image files. It produces errors like this: output: install: cannot stat 'deploy-ti/images/XXXX-evm/omap/XXXX.dtb': No such file or directory or output: install: cannot stat 'deploy-ti/images/XXXX-evm/ti/omap/XXXX.dtb': No such file or directory The issue comes from the UBOOT_EXTLINUX_BOOT_FILES list. am57 already had a mechanism but it was missing the omap/ dir to remove, and am33 and am43 were just takeing KERNEL_DEVICETREE directly. This patch fixes both cases. Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: Update KERNEL_DEVICETREE for mainline 32bit platformsRyan Eatmon2024-04-264-27/+27
| | | | | | | | | We missed that the KERNEL_DEVICETREE should have been updated for the 32bit platforms with the change in linux-ti-mainline to v6.6. The new directory structure under arch/arm/boot/dts is in effect for that version. Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: am335x-evm: Bump up max_leb_cntChirag Shilwant2024-04-081-1/+1
| | | | | | | New features added require another increase to max_leb_cnt. Signed-off-by: Chirag Shilwant <c-shilwant@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: beagleplay/beaglebone-ai64: Set KERNEL_DEVICETREE_PREFIXRyan Eatmon2024-04-042-0/+9
| | | | | | | | Set the KERNEL_DEVICETREE_PREFIX so that, when using the various TI kernel recipes, the "correct" DTB files are pulled in depending on what is available in that kernel source. Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: j721s2/j784s4: Pick overlays for V3Link camerasRahul T R2024-03-262-0/+2
| | | | | | | | | | | am69 and am68 sk boards supports V3Link cameras interfaced via V3Link camera fusion board. Refer to commit b7a97b1b (conf: machine: am62axx: Pick overlays for V3Link cameras) for details Signed-off-by: Rahul T R <r-ravikumar@ti.com> Acked-by: Jai Luthra <j-luthra@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
* conf: machine: j722s-evm: Update KERNERL_DEVICETREE_PREFIX to package ↵Rahul T R2024-03-251-1/+5
| | | | | | | | | | fpdlink cam dtbos j722s-evm supports capture from fpdlink cams via fpdlink fusion1 board or V3Link camera fusion board. So package fpdlink camera overlays Signed-off-by: Rahul T R <r-ravikumar@ti.com> Signed-off-by: Ryan Eatmon <reatmon@ti.com>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2025-07-23 19:06:56 +0000