From 0caec93231090d14bb16f954e55ca0ba641bb5e7 Mon Sep 17 00:00:00 2001 From: Randolph Sapp Date: Tue, 11 Nov 2025 17:45:35 -0600 Subject: [PATCH 1/3] fix(TDA4VM): set __PART_FAMILY_NAME__ to device All platforms currently use __PART_FAMILY_NAME__ to point at an explicit device name. Update this platform to match. Signed-off-by: Randolph Sapp --- configs/TDA4VM/TDA4VM_linux_config.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/configs/TDA4VM/TDA4VM_linux_config.txt b/configs/TDA4VM/TDA4VM_linux_config.txt index e3aee8e7f..a5eaf7c48 100755 --- a/configs/TDA4VM/TDA4VM_linux_config.txt +++ b/configs/TDA4VM/TDA4VM_linux_config.txt @@ -13,7 +13,7 @@ Replacement Variables --------------------- -'__PART_FAMILY_NAME__' : 'Jacinto 7' +'__PART_FAMILY_NAME__' : 'TDA4VM' '__PART_FAMILY_DEVICE_NAMES__' : 'TDA4VM' '__PRODUCT_LINE_NAME__' : 'Jacinto' '__SDK_BUILD_MACHINE__' : 'j721e-evm' From 89f37f70e419de6b16afe1b1f92b3a6c3993bf10 Mon Sep 17 00:00:00 2001 From: Randolph Sapp Date: Tue, 11 Nov 2025 17:39:47 -0600 Subject: [PATCH 2/3] refactor(names): use shorter replacement name Replace all instances of __PART_FAMILY_DEVICE_NAMES__ with __PART_FAMILY_NAME__ since the two are equivalent. Signed-off-by: Randolph Sapp --- .../Overview_Getting_Started_Guide.rst | 6 ++-- source/buildroot/Building_Buildroot_Image.rst | 4 +-- .../Demo_User_Guides/Chromium_Browser.rst | 8 ++--- source/debian/Overview.rst | 2 +- .../AM62LX/debian/Getting_Started_Guide.rst | 2 +- .../AM62PX/debian/Getting_Started_Guide.rst | 2 +- .../AM62X/debian/Getting_Started_Guide.rst | 2 +- .../AM64X/debian/Getting_Started_Guide.rst | 2 +- source/devices/J7_Family/linux/index.rst | 2 +- .../Demo_User_Guides/Chromium_Browser.rst | 20 ++++++------ .../Edge_AI_Gallery_User_Guide.rst | 4 +-- .../TI_Apps_Launcher_User_Guide.rst | 10 +++--- .../TI_LVGL_Demo_User_Guide.rst | 6 ++-- .../Graphics/Rogue/Overview.rst | 6 ++-- .../Hypervisor/Jailhouse.rst | 32 +++++++++---------- .../IPC/_RPMsg_char_driver.rst | 2 +- .../Kernel/Kernel_Drivers/Crypto/DTHEv2.rst | 2 +- .../Kernel_Drivers/Crypto/SA2UL_OMAP.rst | 2 +- .../Kernel/Kernel_Drivers/Display/DSS7.rst | 2 +- .../Kernel_Drivers/E5010_JPEG_Encoder.rst | 6 ++-- .../Kernel/Kernel_Drivers/MCRC64.rst | 4 +-- .../Kernel_Drivers/Network/CPSW-Ethernet.rst | 2 +- .../Kernel_Drivers/Network/CPSW-PTP.rst | 2 +- .../Kernel/Kernel_Drivers/Network/CPSW2g.rst | 6 ++-- .../Kernel/Kernel_Drivers/Network/CPSW3g.rst | 2 +- .../Kernel/Kernel_Drivers/Network/CPSWng.rst | 2 +- .../Network/_K3-CPSW-common.rst | 4 +-- .../Kernel_Drivers/PCIe/PCIe_End_Point.rst | 2 +- .../Kernel_Drivers/PCIe/PCIe_Root_Complex.rst | 10 +++--- .../Kernel/Kernel_Drivers/SERDES/SERDES.rst | 6 ++-- .../Kernel/Kernel_Drivers/Storage/MMC-SD.rst | 8 ++--- .../Kernel/Kernel_Drivers/UART.rst | 2 +- .../Kernel/Kernel_Drivers/USB/AM62_DWC3.rst | 2 +- .../Kernel/Kernel_Drivers/USB/CDNS3.rst | 18 +++++------ .../PRU-ICSS/Linux_Drivers/pruss-uart.rst | 2 +- .../Power_Management/pm_cpuidle.rst | 4 +-- .../Power_Management/pm_overview.rst | 8 ++--- .../Power_Management/pm_wakeup_sources.rst | 14 ++++---- .../linux/Foundational_Components/Sysfw.rst | 2 +- .../U-Boot/UG-DDRSS-J7.rst | 2 +- .../U-Boot/UG-DDRSS.rst | 2 +- .../Foundational_Components/U-Boot/UG-DFU.rst | 4 +-- .../U-Boot/UG-Falcon-Mode.rst | 2 +- .../U-Boot/UG-Memory-K3.rst | 10 +++--- .../U-Boot/UG-Memory-OMAP.rst | 6 ++-- .../U-Boot/UG-QSPI.rst | 2 +- .../U-Boot/UG-Splash-Screen.rst | 12 +++---- ...nal_Components_Multimedia_D5520_VXE384.rst | 4 +-- ...undational_Components_Multimedia_wave5.rst | 4 +-- .../Target/How_to_boot_quickly.rst | 4 +-- .../How_to_enable_DT_overlays_in_linux.rst | 2 +- .../How_to_playback_audio_over_HDMI.rst | 4 +-- source/linux/Overview/_Top_Level_Makefile.rst | 6 ++-- 53 files changed, 143 insertions(+), 143 deletions(-) diff --git a/source/android/Overview_Getting_Started_Guide.rst b/source/android/Overview_Getting_Started_Guide.rst index 168bafe9b..741ab20e6 100644 --- a/source/android/Overview_Getting_Started_Guide.rst +++ b/source/android/Overview_Getting_Started_Guide.rst @@ -9,7 +9,7 @@ Using Prebuilt binaries .. ifconfig:: CONFIG_part_variant in ('AM62X') - The SDK download page provides pre-built Android binaries (:file:`AM62x_{XX}.{YY}.{ZZ}_emmc.tgz`) which can be readily used to flash the |__PART_FAMILY_DEVICE_NAMES__| EVM and boot Android. + The SDK download page provides pre-built Android binaries (:file:`AM62x_{XX}.{YY}.{ZZ}_emmc.tgz`) which can be readily used to flash the |__PART_FAMILY_NAME__| EVM and boot Android. Extract the contents of the pre-built images tarball and follow the procedure mentioned in :ref:`android-flashing` page to flash these binaries to the EVM. @@ -20,7 +20,7 @@ Using Prebuilt binaries .. ifconfig:: CONFIG_part_variant in ('AM62PX') - The SDK download page provides pre-built Android binaries (:file:`AM62Px_{XX}.{YY}.{ZZ}_emmc.tgz`) which can be readily used to flash the |__PART_FAMILY_DEVICE_NAMES__| EVM and boot Android. + The SDK download page provides pre-built Android binaries (:file:`AM62Px_{XX}.{YY}.{ZZ}_emmc.tgz`) which can be readily used to flash the |__PART_FAMILY_NAME__| EVM and boot Android. Extract the contents of the pre-built images tarball and follow the procedure mentioned in :ref:`android-flashing` page to flash these binaries to the EVM. @@ -31,7 +31,7 @@ Using Prebuilt binaries .. ifconfig:: CONFIG_part_variant in ('AM67A') - The SDK download page provides pre-built Android binaries (:file:`AM67A_{XX}.{YY}.{ZZ}_emmc.tgz`) which can be readily used to flash the |__PART_FAMILY_DEVICE_NAMES__| EVM and boot Android. + The SDK download page provides pre-built Android binaries (:file:`AM67A_{XX}.{YY}.{ZZ}_emmc.tgz`) which can be readily used to flash the |__PART_FAMILY_NAME__| EVM and boot Android. Extract the contents of the pre-built images tarball and follow the procedure mentioned in :ref:`android-flashing` page to flash these binaries to the EVM. diff --git a/source/buildroot/Building_Buildroot_Image.rst b/source/buildroot/Building_Buildroot_Image.rst index 4b2febc07..08ece6ff4 100644 --- a/source/buildroot/Building_Buildroot_Image.rst +++ b/source/buildroot/Building_Buildroot_Image.rst @@ -158,13 +158,13 @@ Booting the SD Card Image ========================= After the image is flashed to SD Card. Change the boot mode pins in -|__PART_FAMILY_DEVICE_NAMES__| board for SD Card boot. +|__PART_FAMILY_NAME__| board for SD Card boot. .. code-block:: console SW1[1:8] = 11000010 and SW2[1:8] = 01000000 -Insert the SD Card in SD Card slot in |__PART_FAMILY_DEVICE_NAMES__| board. Use a +Insert the SD Card in SD Card slot in |__PART_FAMILY_NAME__| board. Use a USB Micro-B cable to connect the host PC to the USB Micro-B interface for UART on the EVM then power on the board, the following logs can be observed on the terminal window: diff --git a/source/debian/Demo_User_Guides/Chromium_Browser.rst b/source/debian/Demo_User_Guides/Chromium_Browser.rst index efd2a24f1..e5d35af0a 100644 --- a/source/debian/Demo_User_Guides/Chromium_Browser.rst +++ b/source/debian/Demo_User_Guides/Chromium_Browser.rst @@ -126,7 +126,7 @@ Run as the root user +---------------------------------+----------------------+------------------------------------------------+ | **Platform** | **Performance FPS** | **GPU Utilisation** | +---------------------------------+----------------------+------------------------------------------------+ - | |__PART_FAMILY_DEVICE_NAMES__| | 36 @ 1080p60 | 72% | + | |__PART_FAMILY_NAME__| | 36 @ 1080p60 | 72% | +---------------------------------+----------------------+------------------------------------------------+ .. ifconfig:: CONFIG_part_variant in ('AM62X') @@ -134,7 +134,7 @@ Run as the root user +---------------------------------+----------------------+------------------------------------------------+ | **Platform** | **Performance FPS** | **GPU Utilisation** | +---------------------------------+----------------------+------------------------------------------------+ - | |__PART_FAMILY_DEVICE_NAMES__| | 11 @ 1080p60 | 100% | + | |__PART_FAMILY_NAME__| | 11 @ 1080p60 | 100% | +---------------------------------+----------------------+------------------------------------------------+ .. note:: @@ -158,7 +158,7 @@ Run as the root user +---------------------------------+-----------------------------------------------------------------------+ | **Platform** | **MotionMark v1.3** | +---------------------------------+-----------------------------------------------------------------------+ - | |__PART_FAMILY_DEVICE_NAMES__| | 45.85 @ 1080p60 | + | |__PART_FAMILY_NAME__| | 45.85 @ 1080p60 | +---------------------------------+-----------------------------------------------------------------------+ .. ifconfig:: CONFIG_part_variant in ('AM62X') @@ -166,6 +166,6 @@ Run as the root user +---------------------------------+-----------------------------------------------------------------------+ | **Platform** | **MotionMark v1.3** | +---------------------------------+-----------------------------------------------------------------------+ - | |__PART_FAMILY_DEVICE_NAMES__| | 1.29 @ 1080p60 | + | |__PART_FAMILY_NAME__| | 1.29 @ 1080p60 | +---------------------------------+-----------------------------------------------------------------------+ diff --git a/source/debian/Overview.rst b/source/debian/Overview.rst index bec5b58b1..69263d351 100644 --- a/source/debian/Overview.rst +++ b/source/debian/Overview.rst @@ -19,7 +19,7 @@ A few key highlights of this project are: `__ hosts these packages. - This document also provides the required steps and instructions to customize the TI's components - for |__PART_FAMILY_DEVICE_NAMES__| System-on-a-Chip (SoC) and create the corresponding deb packages. + for |__PART_FAMILY_NAME__| System-on-a-Chip (SoC) and create the corresponding deb packages. - The entire project is public and we accept community contributions as pull requests to GitHub repositories. diff --git a/source/devices/AM62LX/debian/Getting_Started_Guide.rst b/source/devices/AM62LX/debian/Getting_Started_Guide.rst index 857f8dfc9..d8dde8057 100644 --- a/source/devices/AM62LX/debian/Getting_Started_Guide.rst +++ b/source/devices/AM62LX/debian/Getting_Started_Guide.rst @@ -65,7 +65,7 @@ Once the setup ends, reboot the board. Weston screen will appear on the display. .. image:: /images/debian_homescreen.png -You've successfully booted Debian on |__PART_FAMILY_DEVICE_NAMES__|. +You've successfully booted Debian on |__PART_FAMILY_NAME__|. If the board is connected to a private network, setup the proxy to be able to access the Internet. For more info, refer to `apt.conf(5) man page `__ diff --git a/source/devices/AM62PX/debian/Getting_Started_Guide.rst b/source/devices/AM62PX/debian/Getting_Started_Guide.rst index bf37b0f1b..5b74d582e 100644 --- a/source/devices/AM62PX/debian/Getting_Started_Guide.rst +++ b/source/devices/AM62PX/debian/Getting_Started_Guide.rst @@ -65,7 +65,7 @@ Once the setup ends, reboot the board. Weston screen will appear on the display. .. image:: /images/debian_homescreen.png -You've successfully booted Debian on |__PART_FAMILY_DEVICE_NAMES__|. +You've successfully booted Debian on |__PART_FAMILY_NAME__|. If the board is connected to a private network, setup the proxy to be able to access the Internet. For more info, refer to `apt.conf(5) man page `__ diff --git a/source/devices/AM62X/debian/Getting_Started_Guide.rst b/source/devices/AM62X/debian/Getting_Started_Guide.rst index dee5da5aa..0b384fc24 100644 --- a/source/devices/AM62X/debian/Getting_Started_Guide.rst +++ b/source/devices/AM62X/debian/Getting_Started_Guide.rst @@ -65,7 +65,7 @@ Once the setup ends, reboot the board. Weston screen will appear on the display. .. image:: /images/debian_homescreen.png -You've successfully booted Debian on |__PART_FAMILY_DEVICE_NAMES__|. +You've successfully booted Debian on |__PART_FAMILY_NAME__|. If the board is connected to a private network, setup the proxy to be able to access the Internet. For more info, refer to `apt.conf(5) man page `__ diff --git a/source/devices/AM64X/debian/Getting_Started_Guide.rst b/source/devices/AM64X/debian/Getting_Started_Guide.rst index 3b3714ba5..6a42d4a5a 100644 --- a/source/devices/AM64X/debian/Getting_Started_Guide.rst +++ b/source/devices/AM64X/debian/Getting_Started_Guide.rst @@ -67,7 +67,7 @@ To verify the distro, connect via the UART console and try running ``neofetch`` .. image:: /images/debian_neofetch.png -You've successfully booted Debian on |__PART_FAMILY_DEVICE_NAMES__|. +You've successfully booted Debian on |__PART_FAMILY_NAME__|. If the board is connected to a private network, setup the proxy to be able to access the Internet. For more info, refer to `apt.conf(5) man page `__ diff --git a/source/devices/J7_Family/linux/index.rst b/source/devices/J7_Family/linux/index.rst index a2268369b..c5a40c6aa 100644 --- a/source/devices/J7_Family/linux/index.rst +++ b/source/devices/J7_Family/linux/index.rst @@ -5,7 +5,7 @@ Processor SDK Linux Software Developer's Guide ********************************************** -.. rubric:: Welcome to the Processor SDK Linux Software Developer's Guide for |__PART_FAMILY_DEVICE_NAMES__| +.. rubric:: Welcome to the Processor SDK Linux Software Developer's Guide for |__PART_FAMILY_NAME__| .. include:: /linux/Overview/_Processor_SDK_Linux_Software_Developers_Guide.rst diff --git a/source/linux/Demo_User_Guides/Chromium_Browser.rst b/source/linux/Demo_User_Guides/Chromium_Browser.rst index 3dae92433..b7a6933c1 100644 --- a/source/linux/Demo_User_Guides/Chromium_Browser.rst +++ b/source/linux/Demo_User_Guides/Chromium_Browser.rst @@ -203,7 +203,7 @@ Run as the weston user with the command line :console:`chromium https://webglsam +---------------------------------+----------------------+------------------------------------------------+ | **Platform** | **Performance FPS** | **GPU Utilisation** | +---------------------------------+----------------------+------------------------------------------------+ - | |__PART_FAMILY_DEVICE_NAMES__| | 36 @ 1080p60 | 72% | + | |__PART_FAMILY_NAME__| | 36 @ 1080p60 | 72% | +---------------------------------+----------------------+------------------------------------------------+ .. note:: @@ -219,7 +219,7 @@ Run as the weston user with the command line :console:`chromium https://webglsam +---------------------------------+----------------------+------------------------------------------------+ | **Platform** | **Performance FPS** | **GPU Utilisation** | +---------------------------------+----------------------+------------------------------------------------+ - | |__PART_FAMILY_DEVICE_NAMES__| | 11 @ 1080p60 | 100% | + | |__PART_FAMILY_NAME__| | 11 @ 1080p60 | 100% | +---------------------------------+----------------------+------------------------------------------------+ | Beagleplay | 11 @ 1080p60 | 100% | +---------------------------------+----------------------+------------------------------------------------+ @@ -238,7 +238,7 @@ Run as the weston user with the command line :console:`chromium https://webglsam +---------------------------------+-----------------------------------------------------------------------+ | **Platform** | **Performance FPS** | +---------------------------------+-----------------------------------------------------------------------+ - | |__PART_FAMILY_DEVICE_NAMES__| | 33 @ 1080p60 | + | |__PART_FAMILY_NAME__| | 33 @ 1080p60 | +---------------------------------+-----------------------------------------------------------------------+ .. ifconfig:: CONFIG_part_variant in ('J721S2') @@ -246,7 +246,7 @@ Run as the weston user with the command line :console:`chromium https://webglsam +---------------------------------+-----------------------------------------------------------------------+ | **Platform** | **Performance FPS** | +---------------------------------+-----------------------------------------------------------------------+ - | |__PART_FAMILY_DEVICE_NAMES__| | 53 @ 1080p60 | + | |__PART_FAMILY_NAME__| | 53 @ 1080p60 | +---------------------------------+-----------------------------------------------------------------------+ .. ifconfig:: CONFIG_part_variant in ('J784S4') @@ -254,7 +254,7 @@ Run as the weston user with the command line :console:`chromium https://webglsam +---------------------------------+-----------------------------------------------------------------------+ | **Platform** | **Performance FPS** | +---------------------------------+-----------------------------------------------------------------------+ - | |__PART_FAMILY_DEVICE_NAMES__| | 60 @ 1080p60 | + | |__PART_FAMILY_NAME__| | 60 @ 1080p60 | +---------------------------------+-----------------------------------------------------------------------+ **Performance of MotionMarkv1.3** @@ -269,7 +269,7 @@ use the mouse to click the "Run Benchmark" button. +---------------------------------+-----------------------------------------------------------------------+ | **Platform** | **MotionMark v1.3** | +---------------------------------+-----------------------------------------------------------------------+ - | |__PART_FAMILY_DEVICE_NAMES__| | 51.56 @ 1080p60 | + | |__PART_FAMILY_NAME__| | 51.56 @ 1080p60 | +---------------------------------+-----------------------------------------------------------------------+ .. ifconfig:: CONFIG_part_variant in ('AM62X') @@ -277,7 +277,7 @@ use the mouse to click the "Run Benchmark" button. +---------------------------------+-----------------------------------------------------------------------+ | **Platform** | **MotionMark v1.3** | +---------------------------------+-----------------------------------------------------------------------+ - | |__PART_FAMILY_DEVICE_NAMES__| | 1.51 @ 1080p60 | + | |__PART_FAMILY_NAME__| | 1.51 @ 1080p60 | +---------------------------------+-----------------------------------------------------------------------+ | Beagleplay | 1.77 @ 1080p60 | +---------------------------------+-----------------------------------------------------------------------+ @@ -287,7 +287,7 @@ use the mouse to click the "Run Benchmark" button. +---------------------------------+-----------------------------------------------------------------------+ | **Platform** | **MotionMark v1.3** | +---------------------------------+-----------------------------------------------------------------------+ - | |__PART_FAMILY_DEVICE_NAMES__| | 37.56 @ 1080p60 | + | |__PART_FAMILY_NAME__| | 37.56 @ 1080p60 | +---------------------------------+-----------------------------------------------------------------------+ .. ifconfig:: CONFIG_part_variant in ('J721S2') @@ -295,7 +295,7 @@ use the mouse to click the "Run Benchmark" button. +---------------------------------+-----------------------------------------------------------------------+ | **Platform** | **MotionMark v1.3** | +---------------------------------+-----------------------------------------------------------------------+ - | |__PART_FAMILY_DEVICE_NAMES__| | 67.88 @ 1080p60 | + | |__PART_FAMILY_NAME__| | 67.88 @ 1080p60 | +---------------------------------+-----------------------------------------------------------------------+ .. ifconfig:: CONFIG_part_variant in ('J784S4') @@ -303,6 +303,6 @@ use the mouse to click the "Run Benchmark" button. +---------------------------------+-----------------------------------------------------------------------+ | **Platform** | **MotionMark v1.3** | +---------------------------------+-----------------------------------------------------------------------+ - | |__PART_FAMILY_DEVICE_NAMES__| | 177.11 @ 1080p60 | + | |__PART_FAMILY_NAME__| | 177.11 @ 1080p60 | +---------------------------------+-----------------------------------------------------------------------+ diff --git a/source/linux/Demo_User_Guides/Edge_AI_Gallery_User_Guide.rst b/source/linux/Demo_User_Guides/Edge_AI_Gallery_User_Guide.rst index 841df3c28..d7694bd0d 100644 --- a/source/linux/Demo_User_Guides/Edge_AI_Gallery_User_Guide.rst +++ b/source/linux/Demo_User_Guides/Edge_AI_Gallery_User_Guide.rst @@ -6,14 +6,14 @@ Edge AI Gallery - User Guide Overview -------- -The |__PART_FAMILY_DEVICE_NAMES__| SK board has a QT based Out of Box application setup so that user can test the prepackaged models, with sample images, videos and optionally with a connected camera. The Demo also allows users to add their custom models, images, and videos to extend the functionality. +The |__PART_FAMILY_NAME__| SK board has a QT based Out of Box application setup so that user can test the prepackaged models, with sample images, videos and optionally with a connected camera. The Demo also allows users to add their custom models, images, and videos to extend the functionality. All of the necessary equipment requirement and instructions are provided here. Hardware Prerequisites ---------------------- -- TI |__PART_FAMILY_DEVICE_NAMES__| SK +- TI |__PART_FAMILY_NAME__| SK - PC (Windows or Linux, to use serial terminal console) diff --git a/source/linux/Demo_User_Guides/TI_Apps_Launcher_User_Guide.rst b/source/linux/Demo_User_Guides/TI_Apps_Launcher_User_Guide.rst index 538a3ebe7..b307405e6 100644 --- a/source/linux/Demo_User_Guides/TI_Apps_Launcher_User_Guide.rst +++ b/source/linux/Demo_User_Guides/TI_Apps_Launcher_User_Guide.rst @@ -24,7 +24,7 @@ TI Apps Launcher is a QT Based Application launcher for TI Platforms. Currently, .. ifconfig:: CONFIG_part_variant in ('AM62X') - Additionally, The below demos are also available on the |__PART_FAMILY_DEVICE_NAMES__| platform specifically: + Additionally, The below demos are also available on the |__PART_FAMILY_NAME__| platform specifically: - ARM Analytics @@ -45,13 +45,13 @@ Hardware Prerequisites .. ifconfig:: CONFIG_part_variant in ('J721S2','J784S4','J722S') - - TI |__PART_FAMILY_DEVICE_NAMES__| SK + - TI |__PART_FAMILY_NAME__| SK - PC (Windows or Linux, to use serial terminal console) - HDMI Monitor (to view the Demo on Display) -- Ethernet Cable (to connect |__PART_FAMILY_DEVICE_NAMES__| SK to internet) +- Ethernet Cable (to connect |__PART_FAMILY_NAME__| SK to internet) - USB Camera or OV5640 camera sensor module (for Live Camera) @@ -155,7 +155,7 @@ Launching the Camera App .. ifconfig:: CONFIG_part_variant not in ('AM62X') - 1. |__PART_FAMILY_DEVICE_NAMES__| has hardware codecs which are capable of encoding and decoding H.246 and H.265 Videos. + 1. |__PART_FAMILY_NAME__| has hardware codecs which are capable of encoding and decoding H.246 and H.265 Videos. 2. The Camera app supports recording and playback of video in H264 and H265 formats. @@ -250,7 +250,7 @@ Launching the Benchmarks Demo .. ifconfig:: CONFIG_sdk in ('j7_foundational') - 3. User will now see the list of Benchmarks available to test on TI |__PART_FAMILY_DEVICE_NAMES__|. Click on the `play button` infront of the benchmark you like to test. The image below is captured while running the `dhrystone`. + 3. User will now see the list of Benchmarks available to test on TI |__PART_FAMILY_NAME__|. Click on the `play button` infront of the benchmark you like to test. The image below is captured while running the `dhrystone`. .. Image:: /images/benchmarks-system.png :height: 400 diff --git a/source/linux/Demo_User_Guides/TI_LVGL_Demo_User_Guide.rst b/source/linux/Demo_User_Guides/TI_LVGL_Demo_User_Guide.rst index b436155ab..47dfd788a 100644 --- a/source/linux/Demo_User_Guides/TI_LVGL_Demo_User_Guide.rst +++ b/source/linux/Demo_User_Guides/TI_LVGL_Demo_User_Guide.rst @@ -42,7 +42,7 @@ Hardware Prerequisites .. ifconfig:: CONFIG_part_variant in ('AM62PX') - - TI |__PART_FAMILY_DEVICE_NAMES__| SK + - TI |__PART_FAMILY_NAME__| SK - PC (Windows or Linux, to use serial terminal console) @@ -322,11 +322,11 @@ Building the TI LVGL Demo from Sources .. ifconfig:: CONFIG_sdk in ('SITARA') - The TI LVGL Demo is enabled in :file:`tisdk-default-image` yocto filesystem for |__PART_FAMILY_DEVICE_NAMES__| by default. + The TI LVGL Demo is enabled in :file:`tisdk-default-image` yocto filesystem for |__PART_FAMILY_NAME__| by default. .. ifconfig:: CONFIG_sdk in ('DebianSDK') - The TI LVGL Demo is packaged in :file:`tisdk-debian-trixie` wic image for |__PART_FAMILY_DEVICE_NAMES__| by default. + The TI LVGL Demo is packaged in :file:`tisdk-debian-trixie` wic image for |__PART_FAMILY_NAME__| by default. Note, that the binary itself does not have asset images and slides built in it. The image contains the required assets within :file:`/usr/share/ti-lvgl-demo/`. Place any additional diff --git a/source/linux/Foundational_Components/Graphics/Rogue/Overview.rst b/source/linux/Foundational_Components/Graphics/Rogue/Overview.rst index b38f35f05..83e422203 100644 --- a/source/linux/Foundational_Components/Graphics/Rogue/Overview.rst +++ b/source/linux/Foundational_Components/Graphics/Rogue/Overview.rst @@ -7,7 +7,7 @@ Introduction .. ifconfig:: CONFIG_gpu_ip in ('Rogue_8XE') - |__PART_FAMILY_DEVICE_NAMES__| device is enabled with 3D graphics + |__PART_FAMILY_NAME__| device is enabled with 3D graphics accelerator based on the Rogue 8XE series from Imagination Technologies Inc. It enables the support of 3D graphics rendering using OpenGL\ |reg| ES API's. The OpenGL\ |reg| ES API's up to and including version 3.2 with @@ -21,7 +21,7 @@ Introduction .. ifconfig:: CONFIG_gpu_ip in ('Rogue_AXE') - |__PART_FAMILY_DEVICE_NAMES__| device is enabled with 3D graphics + |__PART_FAMILY_NAME__| device is enabled with 3D graphics accelerator based on the A-Series AXE-1-16M from Imagination Technologies Inc. It enables the support of 3D graphics rendering using OpenGL\ |reg| ES API's. The OpenGL\ |reg| ES API's up to and including version 3.1 with @@ -35,7 +35,7 @@ Introduction .. ifconfig:: CONFIG_gpu_ip in ('Rogue_BXS') - |__PART_FAMILY_DEVICE_NAMES__| device is enabled with 3D graphics + |__PART_FAMILY_NAME__| device is enabled with 3D graphics accelerator based on the B-Series BXS-4-64 from Imagination Technologies Inc. It enables the support of 3D graphics rendering using OpenGL\ |reg| ES API's. The OpenGL\ |reg| ES API's up to and including version 3.2 with diff --git a/source/linux/Foundational_Components/Hypervisor/Jailhouse.rst b/source/linux/Foundational_Components/Hypervisor/Jailhouse.rst index 60ca9bfc2..2cb8ff3f2 100644 --- a/source/linux/Foundational_Components/Hypervisor/Jailhouse.rst +++ b/source/linux/Foundational_Components/Hypervisor/Jailhouse.rst @@ -34,9 +34,9 @@ Jailhouse consists of three parts: The tools helps in enabling the hypervisor on the device at runtime, in creating a cell, to load inmate a binary, to run the inmate binary and to stop the hypervisor itself. -************************************************************** -Enabling hypervisor on |__PART_FAMILY_DEVICE_NAMES__| platform -************************************************************** +****************************************************** +Enabling hypervisor on |__PART_FAMILY_NAME__| platform +****************************************************** Jailhouse is an example of Asynchronous Multiprocessing (AMP) architecture. When we boot Linux on a multi-core ARM processor, Linux initially utilizes @@ -58,11 +58,11 @@ The open source Jailhouse project from https://github.com/siemens/jailhouse is i - U-Boot port for Jailhouse can be found here `U-Boot git.ti `__. This repository contains the fix for error message during boot after memory for Jailhouse is reserved in device tree. -******************************************************************** -Building Jailhouse Image for |__PART_FAMILY_DEVICE_NAMES__| platform -******************************************************************** +************************************************************ +Building Jailhouse Image for |__PART_FAMILY_NAME__| platform +************************************************************ -The list of components which should be built to get Jailhouse Image for |__PART_FAMILY_DEVICE_NAMES__| are: +The list of components which should be built to get Jailhouse Image for |__PART_FAMILY_NAME__| are: * U-Boot ( :file:`tiboot3.bin`, :file:`tispl.bin`, :file:`u-boot.img` ). * Kernel ( with Jailhouse and shared memory module ). @@ -77,7 +77,7 @@ Building Jailhouse Image using Yocto Refer to prerequisites for Yocto build for an Ubuntu host: :ref:`Host Setup - ubuntu (Recommended)`. -The steps to download and build the |__PART_FAMILY_DEVICE_NAMES__| wic Image containing Jailhouse (tisdk- +The steps to download and build the |__PART_FAMILY_NAME__| wic Image containing Jailhouse (tisdk- jailhouse-image) using Yocto build environment are as listed below : .. code-block:: console @@ -102,7 +102,7 @@ inmate cell. Building Jailhouse using TI SDK Installer ========================================= -The latest Processor SDK Linux |__PART_FAMILY_DEVICE_NAMES__| installer is available on |__SDK_DOWNLOAD_URL__|. +The latest Processor SDK Linux |__PART_FAMILY_NAME__| installer is available on |__SDK_DOWNLOAD_URL__|. The installer should be downloaded on a Linux ubuntu host machine. The steps to install the sources using installer are: @@ -182,13 +182,13 @@ Booting the SD Card Image ************************* After the tisdk-jailhouse-image-|__SDK_BUILD_MACHINE__|.rootfs.wic.xz is flashed to SD Card. Change -the boot mode pins in |__PART_FAMILY_DEVICE_NAMES__| board for SD Card boot. +the boot mode pins in |__PART_FAMILY_NAME__| board for SD Card boot. .. code-block:: console SW1[1:8] = 11000010 and SW2[1:8] = 01000000 -Insert the SD Card in SD Card slot in |__PART_FAMILY_DEVICE_NAMES__| board. Use a +Insert the SD Card in SD Card slot in |__PART_FAMILY_NAME__| board. Use a USB Micro-B cable to connect the host PC to the USB Micro-B interface for UART on the EVM then power on the board, the following logs can be observed on the terminal window: @@ -290,7 +290,7 @@ on the EVM then power on the board, the following logs can be observed on the te Pre-built components in Jailhouse Image *************************************** -The target filesystem on |__PART_FAMILY_DEVICE_NAMES__| platform will consists +The target filesystem on |__PART_FAMILY_NAME__| platform will consists of the following Jailhouse components: #. :file:`jailhouse.ko` : kernel module at @@ -430,15 +430,15 @@ below: root@am62lxx-evm: jailhouse disable -********************************************************* -Running Jailhouse Demos on |__PART_FAMILY_DEVICE_NAMES__| -********************************************************* +************************************************* +Running Jailhouse Demos on |__PART_FAMILY_NAME__| +************************************************* Host Setup ========== Flash tisdk-jailhouse-image-|__SDK_BUILD_MACHINE__|.rootfs.wic.xz to SD card using balena -and boot |__PART_FAMILY_DEVICE_NAMES__| from the SD card. As we will be running +and boot |__PART_FAMILY_NAME__| from the SD card. As we will be running two instances ,two terminals are required. Connect one terminal to the primary UART (e.g. :file:`/dev/ttyUSB0`) and the other to the secondary UART (e.g. :file:`/dev/ttyUSB1`). diff --git a/source/linux/Foundational_Components/IPC/_RPMsg_char_driver.rst b/source/linux/Foundational_Components/IPC/_RPMsg_char_driver.rst index d5af64bef..0f38096d7 100644 --- a/source/linux/Foundational_Components/IPC/_RPMsg_char_driver.rst +++ b/source/linux/Foundational_Components/IPC/_RPMsg_char_driver.rst @@ -45,7 +45,7 @@ char driver usage from userspace. This library provides an easy means to identify and open rpmsg character devices created by the kernel rpmsg-char driver. -This library support TI K3 family of devices including |__PART_FAMILY_DEVICE_NAMES__|. +This library support TI K3 family of devices including |__PART_FAMILY_NAME__|. The library provides 4 basic APIs wrapping all the rpmsg char driver calls. `Please check documentation in 'include/ti_rpmsg_char.h' for details. diff --git a/source/linux/Foundational_Components/Kernel/Kernel_Drivers/Crypto/DTHEv2.rst b/source/linux/Foundational_Components/Kernel/Kernel_Drivers/Crypto/DTHEv2.rst index d3df0f0f1..1dc005162 100644 --- a/source/linux/Foundational_Components/Kernel/Kernel_Drivers/Crypto/DTHEv2.rst +++ b/source/linux/Foundational_Components/Kernel/Kernel_Drivers/Crypto/DTHEv2.rst @@ -30,7 +30,7 @@ driver and additionally a Cryptodev kernel module (for OpenSSL) is used to access them. Other devices use the pure software implementation of these cryptographic operations. -|__PART_FAMILY_DEVICE_NAMES__| SoC supports a hardware accelerator called +|__PART_FAMILY_NAME__| SoC supports a hardware accelerator called DATA TRANSFORM AND HASHING ENGINE (DTHE) v2 for crypto operations. The kernel configuration has already been set up in the SDK and no further diff --git a/source/linux/Foundational_Components/Kernel/Kernel_Drivers/Crypto/SA2UL_OMAP.rst b/source/linux/Foundational_Components/Kernel/Kernel_Drivers/Crypto/SA2UL_OMAP.rst index 0f67d8998..d5a82ed66 100644 --- a/source/linux/Foundational_Components/Kernel/Kernel_Drivers/Crypto/SA2UL_OMAP.rst +++ b/source/linux/Foundational_Components/Kernel/Kernel_Drivers/Crypto/SA2UL_OMAP.rst @@ -35,7 +35,7 @@ cryptographic operations. .. ifconfig:: CONFIG_crypto in ('sa2ul') - |__PART_FAMILY_DEVICE_NAMES__| SoCs support a hardware accelerator called + |__PART_FAMILY_NAME__| SoCs support a hardware accelerator called Security Accelerator 2/3 Ultra Light (SA2UL/SA3UL) for crypto operations. The kernel configuration has already been set up in the SDK and no further diff --git a/source/linux/Foundational_Components/Kernel/Kernel_Drivers/Display/DSS7.rst b/source/linux/Foundational_Components/Kernel/Kernel_Drivers/Display/DSS7.rst index 877bf4fe8..2d16b7e94 100644 --- a/source/linux/Foundational_Components/Kernel/Kernel_Drivers/Display/DSS7.rst +++ b/source/linux/Foundational_Components/Kernel/Kernel_Drivers/Display/DSS7.rst @@ -88,7 +88,7 @@ The timing generator part of the video port is responsible for providing the pix SoC Hardware Description ------------------------ -SoC Family: |__PART_FAMILY_DEVICE_NAMES__| +SoC Family: |__PART_FAMILY_NAME__| .. ifconfig:: CONFIG_part_variant in ('AM62X', 'AM65X') diff --git a/source/linux/Foundational_Components/Kernel/Kernel_Drivers/E5010_JPEG_Encoder.rst b/source/linux/Foundational_Components/Kernel/Kernel_Drivers/E5010_JPEG_Encoder.rst index 65f3415d1..8ca30c66a 100644 --- a/source/linux/Foundational_Components/Kernel/Kernel_Drivers/E5010_JPEG_Encoder.rst +++ b/source/linux/Foundational_Components/Kernel/Kernel_Drivers/E5010_JPEG_Encoder.rst @@ -102,7 +102,7 @@ of video encoding based use-cases utilizing this driver as demonstrated in below Building the driver =================== -The E5010 JPEG driver is already enabled as a kernel module on |__PART_FAMILY_DEVICE_NAMES__| as part of the default defconfig being used for the board. +The E5010 JPEG driver is already enabled as a kernel module on |__PART_FAMILY_NAME__| as part of the default defconfig being used for the board. If using a separate defconfig, it can be enabled explicitly for compilation by setting corresponding Kconfig as shown below: .. code-block:: kconfig @@ -422,7 +422,7 @@ Buffer alignment requirements Performance and Latency Benchmarking ==================================== -The E5010 core is clocked at 250Mhz on |__PART_FAMILY_DEVICE_NAMES__| and theoretical performance expectation +The E5010 core is clocked at 250Mhz on |__PART_FAMILY_NAME__| and theoretical performance expectation with this clocking is as below : +-------------------+--------------------+ @@ -436,7 +436,7 @@ with this clocking is as below : With these numbers theoretically E5010 core can handle 3840x2160@60fps equivalent load for 4:2:2 video formats and 3840x2160@75fps equivalent load for 4:2:0 video formats. -This however requires the upstream element (for e.g. camera) to support above rates. On |__PART_FAMILY_DEVICE_NAMES__| board fastest locally available upstream element source is :ref:`wave5 VPU decoder ` which provides maximum performance of 3840x2160@59 fps with low bitrate files and we were able to achieve same performance after passing this decoded data to E5010 JPEG Encoder as shown in below example : +This however requires the upstream element (for e.g. camera) to support above rates. On |__PART_FAMILY_NAME__| board fastest locally available upstream element source is :ref:`wave5 VPU decoder ` which provides maximum performance of 3840x2160@59 fps with low bitrate files and we were able to achieve same performance after passing this decoded data to E5010 JPEG Encoder as shown in below example : .. code-block:: console diff --git a/source/linux/Foundational_Components/Kernel/Kernel_Drivers/MCRC64.rst b/source/linux/Foundational_Components/Kernel/Kernel_Drivers/MCRC64.rst index a979bebdc..7201a58ac 100644 --- a/source/linux/Foundational_Components/Kernel/Kernel_Drivers/MCRC64.rst +++ b/source/linux/Foundational_Components/Kernel/Kernel_Drivers/MCRC64.rst @@ -5,7 +5,7 @@ MCRC64 :name: introduction-linux-mcrc64 The MCRC64 driver provides access to the hardware MCRC64 engine -available on |__PART_FAMILY_DEVICE_NAMES__| devices. This driver is +available on |__PART_FAMILY_NAME__| devices. This driver is available as kernel module in the current SDK release. It supports crc64 hardware acceleration. @@ -19,7 +19,7 @@ Other devices use the pure software implementation of these crc64 calculations. .. ifconfig:: CONFIG_mcrc64 in ('mcrc64') - |__PART_FAMILY_DEVICE_NAMES__| SoCs support a hardware accelerator called + |__PART_FAMILY_NAME__| SoCs support a hardware accelerator called MCRC64 engine for crc64 calculations. The kernel configuration has already been set up in the SDK and no further diff --git a/source/linux/Foundational_Components/Kernel/Kernel_Drivers/Network/CPSW-Ethernet.rst b/source/linux/Foundational_Components/Kernel/Kernel_Drivers/Network/CPSW-Ethernet.rst index 33163a0c8..824062973 100644 --- a/source/linux/Foundational_Components/Kernel/Kernel_Drivers/Network/CPSW-Ethernet.rst +++ b/source/linux/Foundational_Components/Kernel/Kernel_Drivers/Network/CPSW-Ethernet.rst @@ -17,7 +17,7 @@ standard TSN features such as PTP, EST, CBS and IET. Instances of the CPSW Subsystem """""""""""""""""""""""""""""""" -The TI |__PART_FAMILY_DEVICE_NAMES__| family of devices contain the following instances +The TI |__PART_FAMILY_NAME__| family of devices contain the following instances of the CPSW Ethernet Subsystem: .. ifconfig:: CONFIG_part_family in ('J7_family') diff --git a/source/linux/Foundational_Components/Kernel/Kernel_Drivers/Network/CPSW-PTP.rst b/source/linux/Foundational_Components/Kernel/Kernel_Drivers/Network/CPSW-PTP.rst index a8535132a..6612e0c71 100644 --- a/source/linux/Foundational_Components/Kernel/Kernel_Drivers/Network/CPSW-PTP.rst +++ b/source/linux/Foundational_Components/Kernel/Kernel_Drivers/Network/CPSW-PTP.rst @@ -385,7 +385,7 @@ The second command is used to specify that /dev/ptpN has to be used as the clock .. rubric:: PPS Pulse Per Second support :name: k3-cpts-pps-support -The PPS support for |__PART_FAMILY_DEVICE_NAMES__| can be enabled with the following steps: +The PPS support for |__PART_FAMILY_NAME__| can be enabled with the following steps: 1. Route the output of the CPSWxG CPTS timestamp generator function (GENFy) to one of the CPSWxG CPTS timestamp generator inputs (HWx_TS_PUSH) using the Time Sync Router, by diff --git a/source/linux/Foundational_Components/Kernel/Kernel_Drivers/Network/CPSW2g.rst b/source/linux/Foundational_Components/Kernel/Kernel_Drivers/Network/CPSW2g.rst index 27e5a7ca4..57203a804 100644 --- a/source/linux/Foundational_Components/Kernel/Kernel_Drivers/Network/CPSW2g.rst +++ b/source/linux/Foundational_Components/Kernel/Kernel_Drivers/Network/CPSW2g.rst @@ -9,11 +9,11 @@ CPSW2g Ethernet Introduction ============ -The TI |__PART_FAMILY_DEVICE_NAMES__| SoC has integrated two-port Gigabit Ethernet Switch subsystem +The TI |__PART_FAMILY_NAME__| SoC has integrated two-port Gigabit Ethernet Switch subsystem with selectable RGMII and RMII interfaces and an internal Communications Port Programming Interface (CPPI) port (Host port 0). Host Port 0 CPPI Packet Streaming Interface interface supports 8 TX channels and one RX channel -operating by TI |__PART_FAMILY_DEVICE_NAMES__| NAVSS Unified DMA Peripheral Root Complex (UDMA-P) controller. +operating by TI |__PART_FAMILY_NAME__| NAVSS Unified DMA Peripheral Root Complex (UDMA-P) controller. The driver follows the standard Linux network interface architecture and supports the following features: @@ -46,7 +46,7 @@ Supported platforms Driver Configuration ==================== -The TI Processor SDK has |__PART_FAMILY_DEVICE_NAMES__| CPSW2g driver enabled by default. +The TI Processor SDK has |__PART_FAMILY_NAME__| CPSW2g driver enabled by default. In case of custom builds, please ensure following configs are enabled. .. code:: Kconfig diff --git a/source/linux/Foundational_Components/Kernel/Kernel_Drivers/Network/CPSW3g.rst b/source/linux/Foundational_Components/Kernel/Kernel_Drivers/Network/CPSW3g.rst index 73ab24909..9962a421c 100644 --- a/source/linux/Foundational_Components/Kernel/Kernel_Drivers/Network/CPSW3g.rst +++ b/source/linux/Foundational_Components/Kernel/Kernel_Drivers/Network/CPSW3g.rst @@ -11,7 +11,7 @@ CPSW3g Introduction ************ -The TI |__PART_FAMILY_DEVICE_NAMES__| family of devices have multi port +The TI |__PART_FAMILY_NAME__| family of devices have multi port Gigabit Ethernet Switch subsystem. SoCs may have more than 2 external port with selectable RGMII and RMII interfaces and an internal Communications Port Programming Interface (CPPI) port (Host port 0). diff --git a/source/linux/Foundational_Components/Kernel/Kernel_Drivers/Network/CPSWng.rst b/source/linux/Foundational_Components/Kernel/Kernel_Drivers/Network/CPSWng.rst index 822256ccd..04bf1049b 100644 --- a/source/linux/Foundational_Components/Kernel/Kernel_Drivers/Network/CPSWng.rst +++ b/source/linux/Foundational_Components/Kernel/Kernel_Drivers/Network/CPSWng.rst @@ -9,7 +9,7 @@ CPSWng Ethernet Introduction """""""""""" -The TI |__PART_FAMILY_DEVICE_NAMES__| family of devices have Multi Port +The TI |__PART_FAMILY_NAME__| family of devices have Multi Port Gigabit Ethernet Switch Subsystem CPSWng. SoCs may have more than 4 external ports with selectable RGMII, QSGMII and SGMII interfaces and an internal Communications Port Programming Interface (CPPI) port (Host port 0). diff --git a/source/linux/Foundational_Components/Kernel/Kernel_Drivers/Network/_K3-CPSW-common.rst b/source/linux/Foundational_Components/Kernel/Kernel_Drivers/Network/_K3-CPSW-common.rst index 7fcaf8653..3a2e81288 100644 --- a/source/linux/Foundational_Components/Kernel/Kernel_Drivers/Network/_K3-CPSW-common.rst +++ b/source/linux/Foundational_Components/Kernel/Kernel_Drivers/Network/_K3-CPSW-common.rst @@ -125,7 +125,7 @@ updating the :file:`am65-cpsw-nuss.c` driver with the following change: .. note:: TX checksum offload is implemented, but it is disabled by default - on affected |__PART_FAMILY_DEVICE_NAMES__| SR1.0 due to errata i2027. + on affected |__PART_FAMILY_NAME__| SR1.0 due to errata i2027. .. rubric:: **VLAN Config** :name: k3-vlan-config @@ -637,7 +637,7 @@ The main difference of the hard irqs deferral feature from ethtool interrupt pac The TI Processor SDK includes precompiled correct version of |__PART_FAMILY_NAME__| switch-config tool. -The TI |__PART_FAMILY_NAME__| switch-config tool sources for |__PART_FAMILY_DEVICE_NAMES__| SoC can be found at +The TI |__PART_FAMILY_NAME__| switch-config tool sources for |__PART_FAMILY_NAME__| SoC can be found at .. code-block:: text diff --git a/source/linux/Foundational_Components/Kernel/Kernel_Drivers/PCIe/PCIe_End_Point.rst b/source/linux/Foundational_Components/Kernel/Kernel_Drivers/PCIe/PCIe_End_Point.rst index ae461a165..816b2f525 100644 --- a/source/linux/Foundational_Components/Kernel/Kernel_Drivers/PCIe/PCIe_End_Point.rst +++ b/source/linux/Foundational_Components/Kernel/Kernel_Drivers/PCIe/PCIe_End_Point.rst @@ -109,7 +109,7 @@ PCIe End Point .. ifconfig:: CONFIG_part_family in ('AM64X_family','J7_family') - |__PART_FAMILY_DEVICE_NAMES__| is, by default, intended to be operated in + |__PART_FAMILY_NAME__| is, by default, intended to be operated in Root Complex mode. So in order to connect two boards, a specialized cable like below is required. diff --git a/source/linux/Foundational_Components/Kernel/Kernel_Drivers/PCIe/PCIe_Root_Complex.rst b/source/linux/Foundational_Components/Kernel/Kernel_Drivers/PCIe/PCIe_Root_Complex.rst index 8999274d8..d1e45105e 100644 --- a/source/linux/Foundational_Components/Kernel/Kernel_Drivers/PCIe/PCIe_Root_Complex.rst +++ b/source/linux/Foundational_Components/Kernel/Kernel_Drivers/PCIe/PCIe_Root_Complex.rst @@ -99,7 +99,7 @@ including desktop, mobile, server, storage and embedded communications. .. rubric:: **Hardware Setup Details** :name: hardware-setup-details - |__PART_FAMILY_DEVICE_NAMES__| is, by default, intended to be operated in + |__PART_FAMILY_NAME__| is, by default, intended to be operated in Root Complex mode. .. ifconfig:: CONFIG_part_variant in ('AM64X') @@ -152,7 +152,7 @@ Following is a brief explanation of layers shown in the diagram: .. rubric:: *DTS Modification* :name: rc-dts-modification - The default dts for |__PART_FAMILY_DEVICE_NAMES__| is configured to be used in + The default dts for |__PART_FAMILY_NAME__| is configured to be used in root complex mode. .. rubric:: *Linux Driver Configuration* @@ -202,16 +202,16 @@ Following is a brief explanation of layers shown in the diagram: The RC should enumerate any off-the-shelf PCIe cards. It has been tested with Ethernet cards, NVMe cards, PCIe USB card, PCIe WiFi card, PCIe SATA - card and also to |__PART_FAMILY_DEVICE_NAMES__| in loopback mode. + card and also to |__PART_FAMILY_NAME__| in loopback mode. In order to see if the connected card is detected, lspci utility should be used. Different utilities can be used depending on the cards. Following are the outputs for some of them: - - Loopback mode (|__PART_FAMILY_DEVICE_NAMES__| EVM to |__PART_FAMILY_DEVICE_NAMES__| EVM) + - Loopback mode (|__PART_FAMILY_NAME__| EVM to |__PART_FAMILY_NAME__| EVM) - Two |__PART_FAMILY_DEVICE_NAMES__| EVMs can be connected in loopback mode by following + Two |__PART_FAMILY_NAME__| EVMs can be connected in loopback mode by following the steps explained in `End Point (EP) Device Configuration `_ section for End Point (EP) and diff --git a/source/linux/Foundational_Components/Kernel/Kernel_Drivers/SERDES/SERDES.rst b/source/linux/Foundational_Components/Kernel/Kernel_Drivers/SERDES/SERDES.rst index fabe5f9a3..7887717ce 100644 --- a/source/linux/Foundational_Components/Kernel/Kernel_Drivers/SERDES/SERDES.rst +++ b/source/linux/Foundational_Components/Kernel/Kernel_Drivers/SERDES/SERDES.rst @@ -29,7 +29,7 @@ Types of SERDES .. ifconfig:: CONFIG_part_variant in ('AM64X') - The TI |__PART_FAMILY_DEVICE_NAMES__| SoC has a 1 Lane SERDES. + The TI |__PART_FAMILY_NAME__| SoC has a 1 Lane SERDES. .. rubric:: *1 Lane Serdes* @@ -75,7 +75,7 @@ Types of SERDES .. ifconfig:: CONFIG_part_variant in ('J7200','J721S2','J784S4','J742S2') - The TI |__PART_FAMILY_DEVICE_NAMES__| SoC has a 4 Lane SERDES. + The TI |__PART_FAMILY_NAME__| SoC has a 4 Lane SERDES. .. ifconfig:: CONFIG_part_variant in ('J721E','J7200','J721S2','J784S4','J742S2') @@ -171,7 +171,7 @@ modified based on the instructions mentioned in the SERDES Muxing section. .. rubric:: *Supported 4 Lane Serdes Configurations* - The 4 Lane SERDES instances in |__PART_FAMILY_DEVICE_NAMES__| SoC are configured by the + The 4 Lane SERDES instances in |__PART_FAMILY_NAME__| SoC are configured by the Torrent Serdes kernel driver: .. code-block:: text diff --git a/source/linux/Foundational_Components/Kernel/Kernel_Drivers/Storage/MMC-SD.rst b/source/linux/Foundational_Components/Kernel/Kernel_Drivers/Storage/MMC-SD.rst index 6d654c676..708003c63 100644 --- a/source/linux/Foundational_Components/Kernel/Kernel_Drivers/Storage/MMC-SD.rst +++ b/source/linux/Foundational_Components/Kernel/Kernel_Drivers/Storage/MMC-SD.rst @@ -7,7 +7,7 @@ MMCSD .. warning:: - There is important information on multimedia card (MMC) support for |__PART_FAMILY_DEVICE_NAMES__| device, go + There is important information on multimedia card (MMC) support for |__PART_FAMILY_NAME__| device, go :ref:`here ` for more information. Introduction @@ -278,7 +278,7 @@ Driver configuration The default kernel configuration enables support for MMCSD driver as built-in to kernel. TI SDHCI driver is used. Following options need to be configured in Linux Kernel for successfully selecting SDHCI driver for - |__PART_FAMILY_DEVICE_NAMES__|. + |__PART_FAMILY_NAME__|. - Enable SDHCI support (CONFIG_MMC_SDHCI) @@ -409,7 +409,7 @@ MMC support in Linux .. ifconfig:: CONFIG_part_family not in ('AM62X_family', 'AM62PX_family') - There is no missing MMC support for |__PART_FAMILY_DEVICE_NAMES__| device. + There is no missing MMC support for |__PART_FAMILY_NAME__| device. Steps for working around SD card issues in Linux ************************************************ @@ -529,7 +529,7 @@ Steps for working around SD card issues in Linux .. ifconfig:: CONFIG_part_family in ('AM57X_family', 'AM335X_family', 'AM437X_family') - Steps for working around SD card issues in Linux documentation is pending for |__PART_FAMILY_DEVICE_NAMES__| + Steps for working around SD card issues in Linux documentation is pending for |__PART_FAMILY_NAME__| please reach out to: `Help e2e `__ for additional information. | diff --git a/source/linux/Foundational_Components/Kernel/Kernel_Drivers/UART.rst b/source/linux/Foundational_Components/Kernel/Kernel_Drivers/UART.rst index 9ef401bf9..dcf2c627e 100644 --- a/source/linux/Foundational_Components/Kernel/Kernel_Drivers/UART.rst +++ b/source/linux/Foundational_Components/Kernel/Kernel_Drivers/UART.rst @@ -14,7 +14,7 @@ This documentation applies to Kernel v4.14 and higher. .. rubric:: Suppported Devices -• |__PART_FAMILY_DEVICE_NAMES__| +• |__PART_FAMILY_NAME__| Driver Features ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ diff --git a/source/linux/Foundational_Components/Kernel/Kernel_Drivers/USB/AM62_DWC3.rst b/source/linux/Foundational_Components/Kernel/Kernel_Drivers/USB/AM62_DWC3.rst index 2b8e9a0bc..83ff192a2 100644 --- a/source/linux/Foundational_Components/Kernel/Kernel_Drivers/USB/AM62_DWC3.rst +++ b/source/linux/Foundational_Components/Kernel/Kernel_Drivers/USB/AM62_DWC3.rst @@ -15,7 +15,7 @@ with on-chip HS/FS/LS (USB2.0) PHY. TI SoC Integration ****************** -The USB subsystem is integrated in TI |__PART_FAMILY_DEVICE_NAMES__| devices. +The USB subsystem is integrated in TI |__PART_FAMILY_NAME__| devices. Starter Kit (SK) **************** diff --git a/source/linux/Foundational_Components/Kernel/Kernel_Drivers/USB/CDNS3.rst b/source/linux/Foundational_Components/Kernel/Kernel_Drivers/USB/CDNS3.rst index b7f0232a7..a05c3e6b2 100644 --- a/source/linux/Foundational_Components/Kernel/Kernel_Drivers/USB/CDNS3.rst +++ b/source/linux/Foundational_Components/Kernel/Kernel_Drivers/USB/CDNS3.rst @@ -14,7 +14,7 @@ controller with on-chip SS (USB3.1 Gen1) PHY and HS/FS/LS (USB2.0) PHY. TI SoC Integration ****************** -The USB subsystem is integrated in TI |__PART_FAMILY_DEVICE_NAMES__| devices. +The USB subsystem is integrated in TI |__PART_FAMILY_NAME__| devices. EVM *** @@ -43,7 +43,7 @@ EVM .. ifconfig:: CONFIG_part_variant in ('J784S4, J742S2') - The following diagram depicts USB integration in |__PART_FAMILY_DEVICE_NAMES__| EVM. + The following diagram depicts USB integration in |__PART_FAMILY_NAME__| EVM. .. image:: /images/usb_j784s4_j742s2_evm.png @@ -62,7 +62,7 @@ EVM .. ifconfig:: CONFIG_part_variant in ('J721S2') - The following diagram depicts USB integration in |__PART_FAMILY_DEVICE_NAMES__| EVM. + The following diagram depicts USB integration in |__PART_FAMILY_NAME__| EVM. .. image:: /images/usb_j721s2_evm.png @@ -81,7 +81,7 @@ EVM .. ifconfig:: CONFIG_part_variant in ('J7200') - The following diagram depicts USB integration in |__PART_FAMILY_DEVICE_NAMES__| EVM. + The following diagram depicts USB integration in |__PART_FAMILY_NAME__| EVM. .. image:: /images/usb_j7200_evm.png @@ -106,7 +106,7 @@ EVM .. ifconfig:: CONFIG_part_variant in ('J722S') - The following diagram depicts USB integration in |__PART_FAMILY_DEVICE_NAMES__| EVM. + The following diagram depicts USB integration in |__PART_FAMILY_NAME__| EVM. .. image:: /images/usb_j722s_evm.png @@ -130,18 +130,18 @@ EVM **AM64X_EVM** - The following diagram depicts USB integration in |__PART_FAMILY_DEVICE_NAMES__| EVM. + The following diagram depicts USB integration in |__PART_FAMILY_NAME__| EVM. .. image:: /images/usb_am64xx_evm.png - The following image shows the top view of |__PART_FAMILY_DEVICE_NAMES__| EVM. + The following image shows the top view of |__PART_FAMILY_NAME__| EVM. .. image:: /images/am64xx_evm.png - The USB controller operates in USB2.0 dual role mode on |__PART_FAMILY_DEVICE_NAMES__| + The USB controller operates in USB2.0 dual role mode on |__PART_FAMILY_NAME__| EVM with a microAB receptacle (labeled as J24). - A 2x3 header (labeled as J23) is provided on |__PART_FAMILY_DEVICE_NAMES__| + A 2x3 header (labeled as J23) is provided on |__PART_FAMILY_NAME__| EVM to configure the port for host-only mode. Connecting Pin 1 and 2 to enable bulk capacitance on VBUS, and connecting Pin 5 and 6 to ground the ID pin. diff --git a/source/linux/Foundational_Components/PRU-ICSS/Linux_Drivers/pruss-uart.rst b/source/linux/Foundational_Components/PRU-ICSS/Linux_Drivers/pruss-uart.rst index 5b850fbc2..c530a96f6 100644 --- a/source/linux/Foundational_Components/PRU-ICSS/Linux_Drivers/pruss-uart.rst +++ b/source/linux/Foundational_Components/PRU-ICSS/Linux_Drivers/pruss-uart.rst @@ -10,7 +10,7 @@ The kernel driver is at drivers/tty/serial/8250/8250_pruss.c. .. rubric:: Support Devices -- |__PART_FAMILY_DEVICE_NAMES__| +- |__PART_FAMILY_NAME__| .. rubric:: Supported Driver Features diff --git a/source/linux/Foundational_Components/Power_Management/pm_cpuidle.rst b/source/linux/Foundational_Components/Power_Management/pm_cpuidle.rst index 2ee47daac..f4d75d5ba 100644 --- a/source/linux/Foundational_Components/Power_Management/pm_cpuidle.rst +++ b/source/linux/Foundational_Components/Power_Management/pm_cpuidle.rst @@ -20,7 +20,7 @@ transition to the selected state. .. rubric:: Standby Mode - On |__PART_FAMILY_DEVICE_NAMES__| platforms, "Standby" mode is implemented through the Linux CPUIdle + On |__PART_FAMILY_NAME__| platforms, "Standby" mode is implemented through the Linux CPUIdle framework. Standby is the default low-power state that the system enters automatically when idle, using the WFI (Wait For Interrupt) C-state. This power-saving mechanism activates whenever the system is "just sitting idle" without requiring any special configuration or activation from @@ -39,7 +39,7 @@ transition to the selected state. .. rubric:: Standby Implementation Architecture - For |__PART_FAMILY_DEVICE_NAMES__|, the Standby implementation involves a multi-layer architecture: + For |__PART_FAMILY_NAME__|, the Standby implementation involves a multi-layer architecture: 1. **Linux CPUIdle Framework**: - Determines when to place CPUs into idle states based on system activity diff --git a/source/linux/Foundational_Components/Power_Management/pm_overview.rst b/source/linux/Foundational_Components/Power_Management/pm_overview.rst index d89077a07..c3a2e5392 100644 --- a/source/linux/Foundational_Components/Power_Management/pm_overview.rst +++ b/source/linux/Foundational_Components/Power_Management/pm_overview.rst @@ -18,7 +18,7 @@ consumption of the SoC when the system is actively performing tasks. Dynamic PM also optimizes the idle power consumption in between tasks, when an individual device or CPU is idle for relatively short duration. -The dynamic power management features enabled on |__PART_FAMILY_DEVICE_NAMES__| are as follows: +The dynamic power management features enabled on |__PART_FAMILY_NAME__| are as follows: .. ifconfig:: CONFIG_part_family in ('AM335X_family', 'AM437X_family') @@ -39,7 +39,7 @@ The dynamic power management features enabled on |__PART_FAMILY_DEVICE_NAMES__| .. note:: - Dynamic Frequency Scaling and runtime PM are not fully supported on |__PART_FAMILY_DEVICE_NAMES__| as of today, + Dynamic Frequency Scaling and runtime PM are not fully supported on |__PART_FAMILY_NAME__| as of today, and shall be enabled in a future release. .. rubric:: Static Power Management @@ -52,7 +52,7 @@ supported by the Linux kernel. .. ifconfig:: CONFIG_part_variant in ('AM62X', 'AM62AX', 'AM62PX') - The static power management features on |__PART_FAMILY_DEVICE_NAMES__| are: + The static power management features on |__PART_FAMILY_NAME__| are: #. Partial I/O #. I/O Only Plus DDR @@ -61,7 +61,7 @@ supported by the Linux kernel. .. ifconfig:: CONFIG_part_variant in ('AM62LX') - The static power management features on |__PART_FAMILY_DEVICE_NAMES__| are: + The static power management features on |__PART_FAMILY_NAME__| are: #. RTC Only Plus DDR #. Deep Sleep diff --git a/source/linux/Foundational_Components/Power_Management/pm_wakeup_sources.rst b/source/linux/Foundational_Components/Power_Management/pm_wakeup_sources.rst index 24862b1ce..d677d238a 100644 --- a/source/linux/Foundational_Components/Power_Management/pm_wakeup_sources.rst +++ b/source/linux/Foundational_Components/Power_Management/pm_wakeup_sources.rst @@ -4,8 +4,8 @@ Wakeup Sources ############## -This section talks about the multiple ways in which we can wakeup the |__PART_FAMILY_DEVICE_NAMES__| SoC from various low power modes. -The |__PART_FAMILY_DEVICE_NAMES__| SoC support various wakeup sources like GP Timers, RTC Timer, UART, I2C, WKUP GPIO, and I/O Daisy Chain. +This section talks about the multiple ways in which we can wakeup the |__PART_FAMILY_NAME__| SoC from various low power modes. +The |__PART_FAMILY_NAME__| SoC support various wakeup sources like GP Timers, RTC Timer, UART, I2C, WKUP GPIO, and I/O Daisy Chain. The table below lists the wakeup sources supported in this SDK release and whether that source is valid for given low power modes: @@ -421,11 +421,11 @@ I/O Power Management and Daisy Chaining section in the TRM. .. note:: - |__PART_FAMILY_DEVICE_NAMES__| supports the ability to wakeup using pad based wake event ONLY in Deep Sleep or MCU Only Mode. + |__PART_FAMILY_NAME__| supports the ability to wakeup using pad based wake event ONLY in Deep Sleep or MCU Only Mode. During active system usage, even if the wake_enable bit is set the system will be unresponsive to any wakeup activity on that pad. - To demonstrate I/O daisy chain wakeup as part of |__PART_FAMILY_DEVICE_NAMES__| offering, two reference examples are provided: + To demonstrate I/O daisy chain wakeup as part of |__PART_FAMILY_NAME__| offering, two reference examples are provided: #. main_uart0 is used where a key press on the Linux console can wakeup the system. #. main_gpio is used where activity on configured GPIO pin can wakeup the system. @@ -434,11 +434,11 @@ I/O Power Management and Daisy Chaining section in the TRM. .. note:: - |__PART_FAMILY_DEVICE_NAMES__| supports the ability to wakeup using pad based wake event ONLY in Deep Sleep. + |__PART_FAMILY_NAME__| supports the ability to wakeup using pad based wake event ONLY in Deep Sleep. During active system usage, even if the wake_enable bit is set the system will be unresponsive to any wakeup activity on that pad. - To demonstrate I/O daisy chain wakeup as part of |__PART_FAMILY_DEVICE_NAMES__| offering, a reference example is provided: + To demonstrate I/O daisy chain wakeup as part of |__PART_FAMILY_NAME__| offering, a reference example is provided: #. main_uart0 is used where a key press on the Linux console can wakeup the system. @@ -917,7 +917,7 @@ RTC Ext Pin .. ifconfig:: CONFIG_part_variant in ('AM62X', 'AM62AX', 'AM62PX') - This is not applicable for |__PART_FAMILY_DEVICE_NAMES__|. + This is not applicable for |__PART_FAMILY_NAME__|. .. ifconfig:: CONFIG_part_variant in ('AM62LX') diff --git a/source/linux/Foundational_Components/Sysfw.rst b/source/linux/Foundational_Components/Sysfw.rst index 57eb4fed5..2cefac741 100644 --- a/source/linux/Foundational_Components/Sysfw.rst +++ b/source/linux/Foundational_Components/Sysfw.rst @@ -5,7 +5,7 @@ System Firmware System Firmware is a collective term used to describe the TI Foundational Security (TIFS) and Resource Management (RM)/ Power Management (PM) services. System Firmware executes on the Security Manager and Device Manager Core (DMSC) -on |__PART_FAMILY_DEVICE_NAMES__|. +on |__PART_FAMILY_NAME__|. System Firmware provides foundational security management and centralized device management. diff --git a/source/linux/Foundational_Components/U-Boot/UG-DDRSS-J7.rst b/source/linux/Foundational_Components/U-Boot/UG-DDRSS-J7.rst index 460869f10..575f0fc8d 100644 --- a/source/linux/Foundational_Components/U-Boot/UG-DDRSS-J7.rst +++ b/source/linux/Foundational_Components/U-Boot/UG-DDRSS-J7.rst @@ -16,7 +16,7 @@ ECC data is calculated over 64-bit data quanta. For every 256-byte data block for ECC storage and the remaining 8/9th of the SDRAM data space are seen as consecutive byte addresses. Even if there are non-ECC protected regions the previously described 1/9th-8/9th rule still applies and consecutive byte -addresses are seen from system point of view. |__PART_FAMILY_DEVICE_NAMES__| +addresses are seen from system point of view. |__PART_FAMILY_NAME__| supports up to 3 ECC protected non-overlapping memory ranges. The current U-Boot release supports a single region covering the entire SDRAM space. diff --git a/source/linux/Foundational_Components/U-Boot/UG-DDRSS.rst b/source/linux/Foundational_Components/U-Boot/UG-DDRSS.rst index 4d2c658c2..f59df4d49 100644 --- a/source/linux/Foundational_Components/U-Boot/UG-DDRSS.rst +++ b/source/linux/Foundational_Components/U-Boot/UG-DDRSS.rst @@ -16,7 +16,7 @@ ECC data is calculated over 64-bit data quanta. For every 256-byte data block for ECC storage and the remaining 8/9th of the SDRAM data space are seen as consecutive byte addresses. Even if there are non-ECC protected regions the previously described 1/9th-8/9th rule still applies and consecutive byte -addresses are seen from system point of view. |__PART_FAMILY_DEVICE_NAMES__| +addresses are seen from system point of view. |__PART_FAMILY_NAME__| supports up to 3 ECC protected non-overlapping memory ranges. The current U-Boot release supports a single region covering the entire SDRAM space. diff --git a/source/linux/Foundational_Components/U-Boot/UG-DFU.rst b/source/linux/Foundational_Components/U-Boot/UG-DFU.rst index 361643acb..11e3f1033 100644 --- a/source/linux/Foundational_Components/U-Boot/UG-DFU.rst +++ b/source/linux/Foundational_Components/U-Boot/UG-DFU.rst @@ -155,11 +155,11 @@ platform that support USB Peripheral boot mode. .. ifconfig:: CONFIG_part_family not in ('AM62X_family', 'AM62AX_family', 'AM62PX_family', 'AM57X_family') - .. rubric:: USB Peripheral boot mode on |__PART_FAMILY_DEVICE_NAMES__| EVM (SPL-DFU boot mode) + .. rubric:: USB Peripheral boot mode on |__PART_FAMILY_NAME__| EVM (SPL-DFU boot mode) .. ifconfig:: CONFIG_part_family in ('AM62X_family', 'AM62AX_family', 'AM62PX_family') - .. rubric:: USB Peripheral boot mode on |__PART_FAMILY_DEVICE_NAMES__| SK (SPL-DFU boot mode) + .. rubric:: USB Peripheral boot mode on |__PART_FAMILY_NAME__| SK (SPL-DFU boot mode) .. ifconfig:: CONFIG_part_variant in ('J721E') diff --git a/source/linux/Foundational_Components/U-Boot/UG-Falcon-Mode.rst b/source/linux/Foundational_Components/U-Boot/UG-Falcon-Mode.rst index 8c7948821..4b8253118 100644 --- a/source/linux/Foundational_Components/U-Boot/UG-Falcon-Mode.rst +++ b/source/linux/Foundational_Components/U-Boot/UG-Falcon-Mode.rst @@ -4,7 +4,7 @@ U-Boot Falcon Mode ################## -U-Boot's falcon mode on |__PART_FAMILY_DEVICE_NAMES__| bypasses the A-core SPL +U-Boot's falcon mode on |__PART_FAMILY_NAME__| bypasses the A-core SPL and U-Boot stage, which allows for booting straight to Linux kernel after OP-TEE and ATF. diff --git a/source/linux/Foundational_Components/U-Boot/UG-Memory-K3.rst b/source/linux/Foundational_Components/U-Boot/UG-Memory-K3.rst index 001ca3e0b..af2b27da8 100644 --- a/source/linux/Foundational_Components/U-Boot/UG-Memory-K3.rst +++ b/source/linux/Foundational_Components/U-Boot/UG-Memory-K3.rst @@ -5,7 +5,7 @@ SD, eMMC and USB .. warning:: - There is important information on multimedia card (MMC) support for |__PART_FAMILY_DEVICE_NAMES__| device, go + There is important information on multimedia card (MMC) support for |__PART_FAMILY_NAME__| device, go :ref:`here ` for more information. Overview @@ -261,7 +261,7 @@ Configuring USB in Host Mode .. ifconfig:: CONFIG_part_variant not in ('J721E', 'J7200', 'J721S2', 'AM64X', 'AM62X', 'AM65X') - Configuring USB in host mode documentation is pending for |__PART_FAMILY_DEVICE_NAMES__| + Configuring USB in host mode documentation is pending for |__PART_FAMILY_NAME__| reach out to: `Help e2e `__ for additional information. .. ifconfig:: CONFIG_part_variant in ('J721E', 'J7200', 'J721S2') @@ -413,7 +413,7 @@ Flash and boot SPL from USB storage .. ifconfig:: CONFIG_part_variant not in ('J7200', 'J721E', 'AM64X', 'AM65X', 'J722S') - Boot SPL from USB storage documentation is pending for |__PART_FAMILY_DEVICE_NAMES__| + Boot SPL from USB storage documentation is pending for |__PART_FAMILY_NAME__| reach out to: `Help e2e `__ for additional information. .. ifconfig:: CONFIG_part_variant in ('J7200', 'J721E') @@ -496,7 +496,7 @@ Boot Linux from USB storage .. ifconfig:: CONFIG_part_family not in ('J7_family', 'AM62X_family', 'AM64X_family') - Booting Linux from USB storage documentation is pending for |__PART_FAMILY_DEVICE_NAMES__|, + Booting Linux from USB storage documentation is pending for |__PART_FAMILY_NAME__|, reach out to: `Help e2e `__ for additional information. .. ifconfig:: CONFIG_part_family in ('J7_family') @@ -785,7 +785,7 @@ MMC support in u-boot .. ifconfig:: CONFIG_part_family not in ('AM62X_family', 'AM62PX_family') - There is no missing MMC support for |__PART_FAMILY_DEVICE_NAMES__| device. + There is no missing MMC support for |__PART_FAMILY_NAME__| device. | diff --git a/source/linux/Foundational_Components/U-Boot/UG-Memory-OMAP.rst b/source/linux/Foundational_Components/U-Boot/UG-Memory-OMAP.rst index 24fbb68b9..037bff1fd 100644 --- a/source/linux/Foundational_Components/U-Boot/UG-Memory-OMAP.rst +++ b/source/linux/Foundational_Components/U-Boot/UG-Memory-OMAP.rst @@ -262,7 +262,7 @@ USB Configuring USB in Host Mode ============================ -Configuring USB in host mode documentation is pending for |__PART_FAMILY_DEVICE_NAMES__|, +Configuring USB in host mode documentation is pending for |__PART_FAMILY_NAME__|, please reach out to: `Help e2e `__ for additional information. .. _uboot-usb-msc-boot: @@ -272,7 +272,7 @@ Flash and boot SPL from USB storage .. ifconfig:: CONFIG_part_variant not in ('AM437X') - Boot SPL from USB storage documentation is pending for |__PART_FAMILY_DEVICE_NAMES__|, + Boot SPL from USB storage documentation is pending for |__PART_FAMILY_NAME__|, please reach out to: `Help e2e `__ for additional information. .. ifconfig:: CONFIG_part_variant in ('AM437X') @@ -296,7 +296,7 @@ Boot Linux from USB storage .. ifconfig:: CONFIG_part_family not in ('AM57X_family') - Booting Linux from USB storage documentation is pending for |__PART_FAMILY_DEVICE_NAMES__|, + Booting Linux from USB storage documentation is pending for |__PART_FAMILY_NAME__|, please reach out to: `Help e2e `__ for additional information. .. ifconfig:: CONFIG_part_family in ('AM57X_family') diff --git a/source/linux/Foundational_Components/U-Boot/UG-QSPI.rst b/source/linux/Foundational_Components/U-Boot/UG-QSPI.rst index 4aeb961a2..66902f2a9 100644 --- a/source/linux/Foundational_Components/U-Boot/UG-QSPI.rst +++ b/source/linux/Foundational_Components/U-Boot/UG-QSPI.rst @@ -1431,7 +1431,7 @@ Flash properties: .. ifconfig:: CONFIG_part_variant in ('J784S4','J742S2', 'J722S') - |__PART_FAMILY_DEVICE_NAMES__| is similar to J721S2, only difference + |__PART_FAMILY_NAME__| is similar to J721S2, only difference being that OSPI0 is muxed externally between a NOR and a NAND flash through a physical switch. OSPI NOR and OSPI NAND can't be used at the same time, they need to be selected by changing a physical configuration diff --git a/source/linux/Foundational_Components/U-Boot/UG-Splash-Screen.rst b/source/linux/Foundational_Components/U-Boot/UG-Splash-Screen.rst index 9c56cdf19..b748f2016 100644 --- a/source/linux/Foundational_Components/U-Boot/UG-Splash-Screen.rst +++ b/source/linux/Foundational_Components/U-Boot/UG-Splash-Screen.rst @@ -8,7 +8,7 @@ Splash screens are typically used to provide feedback to the user that the board to showcase the vendor logo which helps with branding and identification of which boot image is being used for the bootup. -The |__PART_FAMILY_DEVICE_NAMES__| offers out-of-box splash screen experience with OLDI display. +The |__PART_FAMILY_NAME__| offers out-of-box splash screen experience with OLDI display. It also supports displaying a splash screen until kernel is booted up with flicker-free transition across different boot stages. ------------------ @@ -23,7 +23,7 @@ The following features are supported for splash screen in U-Boot: #. Supports MMC and OSPI as bmp image sources. #. Supports splash screen only on OLDI panel. -The |__PART_FAMILY_DEVICE_NAMES__| supports splash screen at both U-Boot proper and A53 SPL with A53 SPL displaying +The |__PART_FAMILY_NAME__| supports splash screen at both U-Boot proper and A53 SPL with A53 SPL displaying splash screen **~1.4 seconds** earlier than U-Boot proper. Enabling the splash screen on ti-u-boot @@ -196,9 +196,9 @@ Display custom logo as splash screen CONFIG_VIDEO_BMP_GZIP=y CONFIG_VIDEO_LOGO=y -Enabling splash screen on custom board based on |__PART_FAMILY_DEVICE_NAMES__| SoC +Enabling splash screen on custom board based on |__PART_FAMILY_NAME__| SoC ----------------------------------------------------------------------------------- -To enable splash screen on custom board based on |__PART_FAMILY_DEVICE_NAMES__| SoC, follow the below steps: +To enable splash screen on custom board based on |__PART_FAMILY_NAME__| SoC, follow the below steps: .. ifconfig:: CONFIG_part_variant in ('AM62PX') @@ -214,14 +214,14 @@ To enable splash screen on custom board based on |__PART_FAMILY_DEVICE_NAMES__| .. ifconfig:: CONFIG_part_variant in ('AM62PX') - 2. Enable the A53 SPL splash screen related configurations in the |__PART_FAMILY_DEVICE_NAMES__| defconfig by referring to below patches and files: + 2. Enable the A53 SPL splash screen related configurations in the |__PART_FAMILY_NAME__| defconfig by referring to below patches and files: * `configs: am62px: Enable A53 splashscreen `_ * `Splash screen config fragment for AM62x and AM62P `_ .. ifconfig:: CONFIG_part_variant in ('AM62X') - 2. Enable the A53 SPL splash screen related configurations in the |__PART_FAMILY_DEVICE_NAMES__| defconfig by referring to below patches and files: + 2. Enable the A53 SPL splash screen related configurations in the |__PART_FAMILY_NAME__| defconfig by referring to below patches and files: * `configs: am62x_evm_a53_defconfig: Enable A53 splashscreen at U-Boot SPL `_ * `Splash screen config fragment for AM62x and AM62P `_ diff --git a/source/linux/Foundational_Components_Multimedia_D5520_VXE384.rst b/source/linux/Foundational_Components_Multimedia_D5520_VXE384.rst index def58c8b4..d3e52444c 100644 --- a/source/linux/Foundational_Components_Multimedia_D5520_VXE384.rst +++ b/source/linux/Foundational_Components_Multimedia_D5520_VXE384.rst @@ -7,7 +7,7 @@ Multimedia Video Codec Introduction ============ -TI's embedded processors such as |__PART_FAMILY_DEVICE_NAMES__| have the +TI's embedded processors such as |__PART_FAMILY_NAME__| have the following hardware accelerators: #. Multi-Standard HD Video Decoder (DECODER) based on D5520MP2 from @@ -332,7 +332,7 @@ GStreamer pipelines that enable the use of hardware-accelerated video decoding through the V4L2 GStreamer plugin. Below is a list of GStreamer plugins that utilize the hardware-accelerated -video decoding in the |__PART_FAMILY_DEVICE_NAMES__|. +video decoding in the |__PART_FAMILY_NAME__|. - DECODER diff --git a/source/linux/Foundational_Components_Multimedia_wave5.rst b/source/linux/Foundational_Components_Multimedia_wave5.rst index 2956d938f..a54241aef 100644 --- a/source/linux/Foundational_Components_Multimedia_wave5.rst +++ b/source/linux/Foundational_Components_Multimedia_wave5.rst @@ -10,7 +10,7 @@ Multimedia Video Codec Introduction ************ -The Wave5 Codec IP is a combined H.264 and H.265 stateful encoder/decoder. It is found on the Texas Instruments |__PART_FAMILY_DEVICE_NAMES__| SoC. +The Wave5 Codec IP is a combined H.264 and H.265 stateful encoder/decoder. It is found on the Texas Instruments |__PART_FAMILY_NAME__| SoC. Hardware capabilities: - Maximum resolution: 8192x8192 (It can handle this resolution, but not @@ -347,7 +347,7 @@ GStreamer pipelines that enable the use of hardware-accelerated video decoding through the V4L2 GStreamer plugin. Below is a list of GStreamer plugins that utilize the hardware-accelerated -video decoding/encoding in the |__PART_FAMILY_DEVICE_NAMES__|. +video decoding/encoding in the |__PART_FAMILY_NAME__|. - ENCODER #. v4l2h264enc diff --git a/source/linux/How_to_Guides/Target/How_to_boot_quickly.rst b/source/linux/How_to_Guides/Target/How_to_boot_quickly.rst index e233febe1..f8ea47e0d 100644 --- a/source/linux/How_to_Guides/Target/How_to_boot_quickly.rst +++ b/source/linux/How_to_Guides/Target/How_to_boot_quickly.rst @@ -4,7 +4,7 @@ Boot Time Optimizations Introduction ------------ -In today's fast-paced automotive industry, the ability to achieve quick processor boot times is more crucial than ever. This guide will walk you through the necessary steps and considerations for achieving faster boot times on |__PRODUCT_LINE_NAME__| |__PART_FAMILY_DEVICE_NAMES__| devices. From adjusting configurations to implementing best practices, you'll gain the insights needed to deliver a seamless, responsive user experience in your automotive applications. By implementing specific modifications, the default SDK offering can be optimized to boot much faster. +In today's fast-paced automotive industry, the ability to achieve quick processor boot times is more crucial than ever. This guide will walk you through the necessary steps and considerations for achieving faster boot times on |__PRODUCT_LINE_NAME__| |__PART_FAMILY_NAME__| devices. From adjusting configurations to implementing best practices, you'll gain the insights needed to deliver a seamless, responsive user experience in your automotive applications. By implementing specific modifications, the default SDK offering can be optimized to boot much faster. Reducing boot time is essential for enhancing user experience and operational efficiency. Quick boot times lead to more responsive systems, which are critical in automotive applications where every second counts. This ensures that drivers and passengers have immediate access to essential features and systems, contributing to overall safety and satisfaction. @@ -385,7 +385,7 @@ The following section displays the time taken by each stage to start and end. Fo | It is not convenient to measure this range since it is dependent on the hardware to provide the power to the PMIC quickly. While TI experts can give suggestions to reduce the time, it will not be TI's commitment. | Range 2 (MCU_PORz to SBL_start): -| MCU_PORz is the Power-On-Reset pin that is set HIGH as soon as the PMIC powers the voltage rails. This can be probed using Pin #28 on the MCU Header (J11) of the |__PART_FAMILY_DEVICE_NAMES__|. All pins are automatically set HIGH at this point. +| MCU_PORz is the Power-On-Reset pin that is set HIGH as soon as the PMIC powers the voltage rails. This can be probed using Pin #28 on the MCU Header (J11) of the |__PART_FAMILY_NAME__|. All pins are automatically set HIGH at this point. .. ifconfig:: CONFIG_part_variant in ('AM62PX') diff --git a/source/linux/How_to_Guides/Target/How_to_enable_DT_overlays_in_linux.rst b/source/linux/How_to_Guides/Target/How_to_enable_DT_overlays_in_linux.rst index cd5d5267f..6d9c08a29 100644 --- a/source/linux/How_to_Guides/Target/How_to_enable_DT_overlays_in_linux.rst +++ b/source/linux/How_to_Guides/Target/How_to_enable_DT_overlays_in_linux.rst @@ -44,4 +44,4 @@ Steps to enable DT overlays: name_overlays=ti/k3-.dtbo ti/k3-.dtbo ti/k3-.dtbo -#. Unmount and eject the SD card. Plug it back in the |__PART_FAMILY_DEVICE_NAMES__| board and turn the board on. +#. Unmount and eject the SD card. Plug it back in the |__PART_FAMILY_NAME__| board and turn the board on. diff --git a/source/linux/How_to_Guides/Target/How_to_playback_audio_over_HDMI.rst b/source/linux/How_to_Guides/Target/How_to_playback_audio_over_HDMI.rst index ca2cfcc5f..3e8f0425a 100644 --- a/source/linux/How_to_Guides/Target/How_to_playback_audio_over_HDMI.rst +++ b/source/linux/How_to_Guides/Target/How_to_playback_audio_over_HDMI.rst @@ -4,7 +4,7 @@ How to playback audio over HDMI ******************************* -SK-|__PART_FAMILY_DEVICE_NAMES__| supports audio playback over HDMI. This +SK-|__PART_FAMILY_NAME__| supports audio playback over HDMI. This requires shorting a jumper on the board, and applying an additional DT overlay (.dtbo) file: :file:`k3-am62x-sk-hdmi-audio.dtbo`. @@ -13,7 +13,7 @@ Steps to enable audio over HDMI #. Toggle the FET switch that shares audio lines between the 3.5mm Jack and HDMI connector. For this you have to short a jumper on the - SK-|__PART_FAMILY_DEVICE_NAMES__|, at the location marked below: + SK-|__PART_FAMILY_NAME__|, at the location marked below: .. Image:: ../../../images/AM62x_HDMI_Audio_Jumper.jpg :scale: 10% diff --git a/source/linux/Overview/_Top_Level_Makefile.rst b/source/linux/Overview/_Top_Level_Makefile.rst index 367f3c779..88ff121e2 100644 --- a/source/linux/Overview/_Top_Level_Makefile.rst +++ b/source/linux/Overview/_Top_Level_Makefile.rst @@ -11,7 +11,7 @@ Overview Inside of the |__SDK_FULL_NAME__| package, there is a top-level Makefile that can be used to build some of the sub-components found within the SDK. This Makefile uses the Rules.make file and gives an example of how the -various components can be built and the parameters to use for |__PART_FAMILY_DEVICE_NAMES__|. +various components can be built and the parameters to use for |__PART_FAMILY_NAME__|. .. note:: @@ -146,7 +146,7 @@ of the |__SDK_FULL_NAME__| package. This file is used not only by the top-level Makefile, but also by many of the sub-component Makefiles to gain access to common shared variables and settings. The variables defined in here are all of the required flags/parameters that will be required to -build/compile any of the sub-component makefile targets for |__PART_FAMILY_DEVICE_NAMES__|. +build/compile any of the sub-component makefile targets for |__PART_FAMILY_NAME__|. .. rubric:: Key Variables Defined :name: variables-defined @@ -160,7 +160,7 @@ OR can be specified over command line when calling the make command. can be set to 'gp', 'hs', and 'hs-fs'. It is used when building u-boot and linux to use unsigned or signed images as required. - **KERNEL\_DEVICETREE\_PREFIX** - This is a regex filter to parse which dtb[o]s - should be built for |__PART_FAMILY_DEVICE_NAMES__| SOC, when building linux kernel. + should be built for |__PART_FAMILY_NAME__| SOC, when building linux kernel. - **ROOTFS\_PART** - This points to the base installation directory that applications/drivers should be installed to. This is usually the root of a target file system but can be changed to point anywhere. From e30d19742e9d1a8754ce64803bc7913eece0fb7c Mon Sep 17 00:00:00 2001 From: Randolph Sapp Date: Tue, 11 Nov 2025 17:48:04 -0600 Subject: [PATCH 3/3] refactor(names): remove __PART_FAMILY_DEVICE_NAMES__ Remove the __PART_FAMILY_DEVICE_NAMES__ replacement definition since it is no longer used. Signed-off-by: Randolph Sapp --- .rstcheck.cfg | 2 +- configs/AM335X/AM335X_linux_config.txt | 1 - configs/AM437X/AM437X_linux_config.txt | 1 - configs/AM57X/AM57X_linux_config.txt | 1 - configs/AM62AX/AM62AX_edgeai_config.txt | 1 - configs/AM62AX/AM62AX_linux_config.txt | 1 - configs/AM62DX/AM62DX_linux_config.txt | 1 - configs/AM62LX/AM62LX_buildroot_config.txt | 1 - configs/AM62LX/AM62LX_debian_config.txt | 1 - configs/AM62LX/AM62LX_linux_config.txt | 1 - configs/AM62PX/AM62PX_android_config.txt | 1 - configs/AM62PX/AM62PX_debian_config.txt | 1 - configs/AM62PX/AM62PX_linux_config.txt | 1 - configs/AM62X/AM62X_android_config.txt | 1 - configs/AM62X/AM62X_buildroot_config.txt | 1 - configs/AM62X/AM62X_debian_config.txt | 1 - configs/AM62X/AM62X_linux_config.txt | 1 - configs/AM64X/AM64X_debian_config.txt | 1 - configs/AM64X/AM64X_linux_config.txt | 1 - configs/AM65X/AM65X_linux_config.txt | 1 - configs/AM67/AM67_linux_config.txt | 1 - configs/AM67A/AM67A_android_config.txt | 1 - configs/AM67A/AM67A_linux_config.txt | 1 - configs/AM68/AM68_linux_config.txt | 1 - configs/AM68A/AM68A_linux_config.txt | 1 - configs/AM69/AM69_linux_config.txt | 1 - configs/AM69A/AM69A_linux_config.txt | 1 - configs/DRA821A/DRA821A_linux_config.txt | 1 - configs/J7200/J7200_linux_config.txt | 1 - configs/J721E/J721E_linux_config.txt | 1 - configs/J721S2/J721S2_linux_config.txt | 1 - configs/J722S/J722S_linux_config.txt | 1 - configs/J742S2/J742S2_linux_config.txt | 1 - configs/J784S4/J784S4_linux_config.txt | 1 - configs/TDA4VM/TDA4VM_linux_config.txt | 1 - 35 files changed, 1 insertion(+), 35 deletions(-) diff --git a/.rstcheck.cfg b/.rstcheck.cfg index 781c9511f..1fee8060f 100644 --- a/.rstcheck.cfg +++ b/.rstcheck.cfg @@ -3,5 +3,5 @@ ignore_directives = ifconfig # ignore the following languages because they require external compilers and # snippets in this repo depend on external code ignore_languages = c,cpp,c++ -ignore_substitutions = __PART_FAMILY_NAME__,__PART_FAMILY_DEVICE_NAMES__,__PRODUCT_LINE_NAME__,__SDK_BUILD_MACHINE__,__SDK_FULL_NAME__,__SDK_SHORT_NAME__,__SDK_INSTALL_FILE__,__SDK_INSTALL_DIR__,__SDK_DOWNLOAD_URL__,__LINUX_UBUNTU_VERSION_LONG__,__LINUX_UBUNTU_VERSION_SHORT__,__OPTEE_PLATFORM_FLAVOR__,__RTOS_UBUNTU_VERSION_LONG__,__WINDOWS_SUPPORTED_LONG__,__FEATURINGMATRIX__,__SYSFW_CORE_NAME__,__PCIE_BASE_ADDRESS__,__PCIE_DEVICE_ID__,__IMAGE_TYPE__,__SDK_OS_NAME__ +ignore_substitutions = __PART_FAMILY_NAME__,__PRODUCT_LINE_NAME__,__SDK_BUILD_MACHINE__,__SDK_FULL_NAME__,__SDK_SHORT_NAME__,__SDK_INSTALL_FILE__,__SDK_INSTALL_DIR__,__SDK_DOWNLOAD_URL__,__LINUX_UBUNTU_VERSION_LONG__,__LINUX_UBUNTU_VERSION_SHORT__,__OPTEE_PLATFORM_FLAVOR__,__RTOS_UBUNTU_VERSION_LONG__,__WINDOWS_SUPPORTED_LONG__,__FEATURINGMATRIX__,__SYSFW_CORE_NAME__,__PCIE_BASE_ADDRESS__,__PCIE_DEVICE_ID__,__IMAGE_TYPE__,__SDK_OS_NAME__ ignore_messages = (Hyperlink target.*is not referenced\.) diff --git a/configs/AM335X/AM335X_linux_config.txt b/configs/AM335X/AM335X_linux_config.txt index e2fe88243..f6954bbd9 100644 --- a/configs/AM335X/AM335X_linux_config.txt +++ b/configs/AM335X/AM335X_linux_config.txt @@ -14,7 +14,6 @@ Replacement Variables --------------------- '__PART_FAMILY_NAME__' : 'AM335x' -'__PART_FAMILY_DEVICE_NAMES__' : 'AM335x' '__PRODUCT_LINE_NAME__' : 'Sitara' '__SDK_BUILD_MACHINE__' : 'am335x-evm' '__SDK_FULL_NAME__' : 'Processor SDK Linux' diff --git a/configs/AM437X/AM437X_linux_config.txt b/configs/AM437X/AM437X_linux_config.txt index 9f38443a3..67b3d6377 100644 --- a/configs/AM437X/AM437X_linux_config.txt +++ b/configs/AM437X/AM437X_linux_config.txt @@ -14,7 +14,6 @@ Replacement Variables --------------------- '__PART_FAMILY_NAME__' : 'AM437x' -'__PART_FAMILY_DEVICE_NAMES__' : 'AM437x' '__PRODUCT_LINE_NAME__' : 'Sitara' '__SDK_BUILD_MACHINE__' : 'am437x-evm' '__SDK_FULL_NAME__' : 'Processor SDK Linux' diff --git a/configs/AM57X/AM57X_linux_config.txt b/configs/AM57X/AM57X_linux_config.txt index e19decf41..6ea8d73f3 100644 --- a/configs/AM57X/AM57X_linux_config.txt +++ b/configs/AM57X/AM57X_linux_config.txt @@ -14,7 +14,6 @@ Replacement Variables --------------------- '__PART_FAMILY_NAME__' : 'AM57x' -'__PART_FAMILY_DEVICE_NAMES__' : 'AM57x' '__PRODUCT_LINE_NAME__' : 'Jacinto' '__SDK_BUILD_MACHINE__' : 'am57xx-evm' '__SDK_FULL_NAME__' : 'Processor SDK Linux AM57X' diff --git a/configs/AM62AX/AM62AX_edgeai_config.txt b/configs/AM62AX/AM62AX_edgeai_config.txt index 31fd4a687..add684b06 100644 --- a/configs/AM62AX/AM62AX_edgeai_config.txt +++ b/configs/AM62AX/AM62AX_edgeai_config.txt @@ -14,7 +14,6 @@ Replacement Variables --------------------- '__PART_FAMILY_NAME__' : 'AM62Ax' -'__PART_FAMILY_DEVICE_NAMES__' : 'AM62Ax' '__PRODUCT_LINE_NAME__' : 'Sitara MPU' '__SDK_BUILD_MACHINE__' : 'am62a-sk' '__SDK_FULL_NAME__' : 'Processor SDK Linux Edge AI AM62Ax' diff --git a/configs/AM62AX/AM62AX_linux_config.txt b/configs/AM62AX/AM62AX_linux_config.txt index 7007232d1..f3279f96f 100644 --- a/configs/AM62AX/AM62AX_linux_config.txt +++ b/configs/AM62AX/AM62AX_linux_config.txt @@ -14,7 +14,6 @@ Replacement Variables --------------------- '__PART_FAMILY_NAME__' : 'AM62Ax' -'__PART_FAMILY_DEVICE_NAMES__' : 'AM62Ax' '__PRODUCT_LINE_NAME__' : 'Sitara MPU' '__SDK_BUILD_MACHINE__' : 'am62axx-evm' '__SDK_FULL_NAME__' : 'Processor SDK Linux AM62Ax' diff --git a/configs/AM62DX/AM62DX_linux_config.txt b/configs/AM62DX/AM62DX_linux_config.txt index 39aea40d0..d266bdc94 100644 --- a/configs/AM62DX/AM62DX_linux_config.txt +++ b/configs/AM62DX/AM62DX_linux_config.txt @@ -14,7 +14,6 @@ Replacement Variables --------------------- '__PART_FAMILY_NAME__' : 'AM62Dx' -'__PART_FAMILY_DEVICE_NAMES__' : 'AM62Dx' '__PRODUCT_LINE_NAME__' : 'Sitara MPU' '__SDK_BUILD_MACHINE__' : 'am62dxx-evm' '__SDK_FULL_NAME__' : 'AM62D-Linux-SDK' diff --git a/configs/AM62LX/AM62LX_buildroot_config.txt b/configs/AM62LX/AM62LX_buildroot_config.txt index 1e0d552c5..7d2d28298 100644 --- a/configs/AM62LX/AM62LX_buildroot_config.txt +++ b/configs/AM62LX/AM62LX_buildroot_config.txt @@ -14,7 +14,6 @@ Replacement Variables --------------------- '__PART_FAMILY_NAME__' : 'AM62Lx' -'__PART_FAMILY_DEVICE_NAMES__' : 'AM62Lx' '__PRODUCT_LINE_NAME__' : 'Sitara MPU' '__SDK_BUILD_MACHINE__' : 'am62lxx-evm' '__SDK_FULL_NAME__' : 'Buildroot for AM62L' diff --git a/configs/AM62LX/AM62LX_debian_config.txt b/configs/AM62LX/AM62LX_debian_config.txt index 795409724..333ef221c 100644 --- a/configs/AM62LX/AM62LX_debian_config.txt +++ b/configs/AM62LX/AM62LX_debian_config.txt @@ -14,7 +14,6 @@ Replacement Variables --------------------- '__PART_FAMILY_NAME__' : 'AM62Lx' -'__PART_FAMILY_DEVICE_NAMES__' : 'AM62Lx' '__PRODUCT_LINE_NAME__' : 'Sitara MPU' '__SDK_BUILD_MACHINE__' : 'am62lxx-evm' '__SDK_FULL_NAME__' : 'Debian for AM62Lx' diff --git a/configs/AM62LX/AM62LX_linux_config.txt b/configs/AM62LX/AM62LX_linux_config.txt index e72afd02e..5f1855858 100644 --- a/configs/AM62LX/AM62LX_linux_config.txt +++ b/configs/AM62LX/AM62LX_linux_config.txt @@ -14,7 +14,6 @@ Replacement Variables --------------------- '__PART_FAMILY_NAME__' : 'AM62Lx' -'__PART_FAMILY_DEVICE_NAMES__' : 'AM62Lx' '__PRODUCT_LINE_NAME__' : 'Sitara MPU' '__SDK_BUILD_MACHINE__' : 'am62lxx-evm' '__SDK_FULL_NAME__' : 'AM62L-Linux-SDK' diff --git a/configs/AM62PX/AM62PX_android_config.txt b/configs/AM62PX/AM62PX_android_config.txt index c355b94bb..d03ab438d 100644 --- a/configs/AM62PX/AM62PX_android_config.txt +++ b/configs/AM62PX/AM62PX_android_config.txt @@ -14,7 +14,6 @@ Replacement Variables --------------------- '__PART_FAMILY_NAME__' : 'AM62Px' -'__PART_FAMILY_DEVICE_NAMES__' : 'AM62Px' '__PRODUCT_LINE_NAME__' : 'Sitara MPU' '__SDK_OS_NAME__' : 'Processor SDK Android' '__SDK_FULL_NAME__' : 'Processor SDK Android AM62Px' diff --git a/configs/AM62PX/AM62PX_debian_config.txt b/configs/AM62PX/AM62PX_debian_config.txt index 20e08d647..d49a3eb12 100644 --- a/configs/AM62PX/AM62PX_debian_config.txt +++ b/configs/AM62PX/AM62PX_debian_config.txt @@ -14,7 +14,6 @@ Replacement Variables --------------------- '__PART_FAMILY_NAME__' : 'AM62Px' -'__PART_FAMILY_DEVICE_NAMES__' : 'AM62Px' '__PRODUCT_LINE_NAME__' : 'Sitara MPU' '__SDK_BUILD_MACHINE__' : 'am62pxx-evm' '__SDK_FULL_NAME__' : 'Debian for AM62Px' diff --git a/configs/AM62PX/AM62PX_linux_config.txt b/configs/AM62PX/AM62PX_linux_config.txt index f95320981..867963f2e 100644 --- a/configs/AM62PX/AM62PX_linux_config.txt +++ b/configs/AM62PX/AM62PX_linux_config.txt @@ -14,7 +14,6 @@ Replacement Variables --------------------- '__PART_FAMILY_NAME__' : 'AM62Px' -'__PART_FAMILY_DEVICE_NAMES__' : 'AM62Px' '__PRODUCT_LINE_NAME__' : 'Sitara MPU' '__SDK_BUILD_MACHINE__' : 'am62pxx-evm' '__SDK_FULL_NAME__' : 'Processor SDK Linux AM62Px' diff --git a/configs/AM62X/AM62X_android_config.txt b/configs/AM62X/AM62X_android_config.txt index f988583d5..5a22856af 100644 --- a/configs/AM62X/AM62X_android_config.txt +++ b/configs/AM62X/AM62X_android_config.txt @@ -14,7 +14,6 @@ Replacement Variables --------------------- '__PART_FAMILY_NAME__' : 'AM62x' -'__PART_FAMILY_DEVICE_NAMES__' : 'AM62x' '__PRODUCT_LINE_NAME__' : 'Sitara MPU' '__SDK_OS_NAME__' : 'Processor SDK Android' '__SDK_FULL_NAME__' : 'Processor SDK Android AM62x' diff --git a/configs/AM62X/AM62X_buildroot_config.txt b/configs/AM62X/AM62X_buildroot_config.txt index 6e5f031b6..ea42f0d49 100644 --- a/configs/AM62X/AM62X_buildroot_config.txt +++ b/configs/AM62X/AM62X_buildroot_config.txt @@ -14,7 +14,6 @@ Replacement Variables --------------------- '__PART_FAMILY_NAME__' : 'AM62x' -'__PART_FAMILY_DEVICE_NAMES__' : 'AM62x' '__PRODUCT_LINE_NAME__' : 'Sitara MPU' '__SDK_BUILD_MACHINE__' : 'am62xx-evm' '__SDK_FULL_NAME__' : 'Buildroot for AM62x' diff --git a/configs/AM62X/AM62X_debian_config.txt b/configs/AM62X/AM62X_debian_config.txt index dd541b290..9612f4ef1 100644 --- a/configs/AM62X/AM62X_debian_config.txt +++ b/configs/AM62X/AM62X_debian_config.txt @@ -14,7 +14,6 @@ Replacement Variables --------------------- '__PART_FAMILY_NAME__' : 'AM62x' -'__PART_FAMILY_DEVICE_NAMES__' : 'AM62x' '__PRODUCT_LINE_NAME__' : 'Sitara MPU' '__SDK_BUILD_MACHINE__' : 'am62xx-evm' '__SDK_FULL_NAME__' : 'Debian for AM62x' diff --git a/configs/AM62X/AM62X_linux_config.txt b/configs/AM62X/AM62X_linux_config.txt index a58761499..281aa880f 100644 --- a/configs/AM62X/AM62X_linux_config.txt +++ b/configs/AM62X/AM62X_linux_config.txt @@ -14,7 +14,6 @@ Replacement Variables --------------------- '__PART_FAMILY_NAME__' : 'AM62x' -'__PART_FAMILY_DEVICE_NAMES__' : 'AM62x' '__PRODUCT_LINE_NAME__' : 'Sitara MPU' '__SDK_BUILD_MACHINE__' : 'am62xx-evm' '__SDK_FULL_NAME__' : 'Processor SDK Linux AM62x' diff --git a/configs/AM64X/AM64X_debian_config.txt b/configs/AM64X/AM64X_debian_config.txt index 217c0b276..5cc56b432 100644 --- a/configs/AM64X/AM64X_debian_config.txt +++ b/configs/AM64X/AM64X_debian_config.txt @@ -14,7 +14,6 @@ Replacement Variables --------------------- '__PART_FAMILY_NAME__' : 'AM64x' -'__PART_FAMILY_DEVICE_NAMES__' : 'AM64x' '__PRODUCT_LINE_NAME__' : 'Sitara MPU' '__SDK_BUILD_MACHINE__' : 'am64xx-evm' '__SDK_FULL_NAME__' : 'Debian for AM64x' diff --git a/configs/AM64X/AM64X_linux_config.txt b/configs/AM64X/AM64X_linux_config.txt index 54be98b93..7f4e25de9 100644 --- a/configs/AM64X/AM64X_linux_config.txt +++ b/configs/AM64X/AM64X_linux_config.txt @@ -14,7 +14,6 @@ Replacement Variables --------------------- '__PART_FAMILY_NAME__' : 'AM64x' -'__PART_FAMILY_DEVICE_NAMES__' : 'AM64x' '__PRODUCT_LINE_NAME__' : 'Sitara MPU' '__SDK_BUILD_MACHINE__' : 'am64xx-evm' '__SDK_FULL_NAME__' : 'Processor SDK AM64x' diff --git a/configs/AM65X/AM65X_linux_config.txt b/configs/AM65X/AM65X_linux_config.txt index 1e7305af0..3cb0e82a3 100644 --- a/configs/AM65X/AM65X_linux_config.txt +++ b/configs/AM65X/AM65X_linux_config.txt @@ -14,7 +14,6 @@ Replacement Variables --------------------- '__PART_FAMILY_NAME__' : 'AM65x' -'__PART_FAMILY_DEVICE_NAMES__' : 'AM65x' '__PRODUCT_LINE_NAME__' : 'Sitara MPU' '__SDK_BUILD_MACHINE__' : 'am65xx-evm' '__SDK_FULL_NAME__' : 'Processor SDK Linux AM65xx' diff --git a/configs/AM67/AM67_linux_config.txt b/configs/AM67/AM67_linux_config.txt index 9ed398e89..d0c75a0c6 100644 --- a/configs/AM67/AM67_linux_config.txt +++ b/configs/AM67/AM67_linux_config.txt @@ -14,7 +14,6 @@ Replacement Variables --------------------- '__PART_FAMILY_NAME__' : 'J722S' -'__PART_FAMILY_DEVICE_NAMES__' : 'AM67' '__PRODUCT_LINE_NAME__' : 'Jacinto' '__SDK_BUILD_MACHINE__' : 'j722s-evm' '__SDK_FULL_NAME__' : 'Processor SDK Linux AM67' diff --git a/configs/AM67A/AM67A_android_config.txt b/configs/AM67A/AM67A_android_config.txt index 9a5c96c3a..dedbd3fdb 100644 --- a/configs/AM67A/AM67A_android_config.txt +++ b/configs/AM67A/AM67A_android_config.txt @@ -14,7 +14,6 @@ Replacement Variables --------------------- '__PART_FAMILY_NAME__' : 'AM67A' -'__PART_FAMILY_DEVICE_NAMES__' : 'AM67A' '__PRODUCT_LINE_NAME__' : 'Sitara MPU' '__SDK_OS_NAME__' : 'Processor SDK Android' '__SDK_FULL_NAME__' : 'Processor SDK Android AM67A' diff --git a/configs/AM67A/AM67A_linux_config.txt b/configs/AM67A/AM67A_linux_config.txt index 473317fc8..92cb14070 100644 --- a/configs/AM67A/AM67A_linux_config.txt +++ b/configs/AM67A/AM67A_linux_config.txt @@ -14,7 +14,6 @@ Replacement Variables --------------------- '__PART_FAMILY_NAME__' : 'Jacinto 7 AEN' -'__PART_FAMILY_DEVICE_NAMES__' : 'AM67A' '__PRODUCT_LINE_NAME__' : 'Jacinto' '__SDK_BUILD_MACHINE__' : 'j722s-evm' '__SDK_FULL_NAME__' : 'Processor SDK Linux AM67A' diff --git a/configs/AM68/AM68_linux_config.txt b/configs/AM68/AM68_linux_config.txt index 952403d0a..c8548109e 100644 --- a/configs/AM68/AM68_linux_config.txt +++ b/configs/AM68/AM68_linux_config.txt @@ -14,7 +14,6 @@ Replacement Variables --------------------- '__PART_FAMILY_NAME__' : 'J721S2' -'__PART_FAMILY_DEVICE_NAMES__' : 'AM68' '__PRODUCT_LINE_NAME__' : 'Jacinto' '__SDK_BUILD_MACHINE__' : 'am68-sk' '__SDK_FULL_NAME__' : 'Processor SDK Linux AM68' diff --git a/configs/AM68A/AM68A_linux_config.txt b/configs/AM68A/AM68A_linux_config.txt index f68c845b8..3c811308a 100755 --- a/configs/AM68A/AM68A_linux_config.txt +++ b/configs/AM68A/AM68A_linux_config.txt @@ -14,7 +14,6 @@ Replacement Variables --------------------- '__PART_FAMILY_NAME__' : 'Jacinto 7 AEP' -'__PART_FAMILY_DEVICE_NAMES__' : 'AM68A' '__PRODUCT_LINE_NAME__' : 'Jacinto' '__SDK_BUILD_MACHINE__' : 'am68-sk' '__SDK_FULL_NAME__' : 'Processor SDK Linux AM68A' diff --git a/configs/AM69/AM69_linux_config.txt b/configs/AM69/AM69_linux_config.txt index cd4d54ffd..82f3669cb 100644 --- a/configs/AM69/AM69_linux_config.txt +++ b/configs/AM69/AM69_linux_config.txt @@ -14,7 +14,6 @@ Replacement Variables --------------------- '__PART_FAMILY_NAME__' : 'J784S4' -'__PART_FAMILY_DEVICE_NAMES__' : 'AM69' '__PRODUCT_LINE_NAME__' : 'Jacinto' '__SDK_BUILD_MACHINE__' : 'am69-sk' '__SDK_FULL_NAME__' : 'Processor SDK Linux AM69' diff --git a/configs/AM69A/AM69A_linux_config.txt b/configs/AM69A/AM69A_linux_config.txt index 27f21572c..d99fe7d29 100755 --- a/configs/AM69A/AM69A_linux_config.txt +++ b/configs/AM69A/AM69A_linux_config.txt @@ -14,7 +14,6 @@ Replacement Variables --------------------- '__PART_FAMILY_NAME__' : 'Jacinto 7 AHP' -'__PART_FAMILY_DEVICE_NAMES__' : 'AM69A' '__PRODUCT_LINE_NAME__' : 'Jacinto' '__SDK_BUILD_MACHINE__' : 'am69-sk' '__SDK_FULL_NAME__' : 'Processor SDK Linux AM69A' diff --git a/configs/DRA821A/DRA821A_linux_config.txt b/configs/DRA821A/DRA821A_linux_config.txt index c82a05ff3..a8a664b63 100644 --- a/configs/DRA821A/DRA821A_linux_config.txt +++ b/configs/DRA821A/DRA821A_linux_config.txt @@ -14,7 +14,6 @@ Replacement Variables --------------------- '__PART_FAMILY_NAME__' : 'Jacinto 7 VCL MPU-Only' -'__PART_FAMILY_DEVICE_NAMES__' : 'DRA821A' '__PRODUCT_LINE_NAME__' : 'Jacinto' '__SDK_BUILD_MACHINE__' : 'j7200-evm' '__SDK_FULL_NAME__' : 'Processor SDK Linux DRA821A' diff --git a/configs/J7200/J7200_linux_config.txt b/configs/J7200/J7200_linux_config.txt index fe0e9ba55..c00e11414 100644 --- a/configs/J7200/J7200_linux_config.txt +++ b/configs/J7200/J7200_linux_config.txt @@ -14,7 +14,6 @@ Replacement Variables --------------------- '__PART_FAMILY_NAME__' : 'Jacinto 7 VCL' -'__PART_FAMILY_DEVICE_NAMES__' : 'J7200' '__PRODUCT_LINE_NAME__' : 'Jacinto' '__SDK_BUILD_MACHINE__' : 'j7200-evm' '__SDK_FULL_NAME__' : 'Processor SDK Linux J7200' diff --git a/configs/J721E/J721E_linux_config.txt b/configs/J721E/J721E_linux_config.txt index 3eef58a94..b548284ca 100644 --- a/configs/J721E/J721E_linux_config.txt +++ b/configs/J721E/J721E_linux_config.txt @@ -14,7 +14,6 @@ Replacement Variables --------------------- '__PART_FAMILY_NAME__' : 'Jacinto 7' -'__PART_FAMILY_DEVICE_NAMES__' : 'J721E' '__PRODUCT_LINE_NAME__' : 'Jacinto' '__SDK_BUILD_MACHINE__' : 'j721e-evm' '__SDK_FULL_NAME__' : 'Processor SDK Linux J721e' diff --git a/configs/J721S2/J721S2_linux_config.txt b/configs/J721S2/J721S2_linux_config.txt index 9c9cd98fe..642e668f5 100644 --- a/configs/J721S2/J721S2_linux_config.txt +++ b/configs/J721S2/J721S2_linux_config.txt @@ -14,7 +14,6 @@ Replacement Variables --------------------- '__PART_FAMILY_NAME__' : 'J721S2' -'__PART_FAMILY_DEVICE_NAMES__' : 'J721S2' '__PRODUCT_LINE_NAME__' : 'Jacinto' '__SDK_BUILD_MACHINE__' : 'j721s2-evm' '__SDK_FULL_NAME__' : 'Processor SDK Linux J721s2' diff --git a/configs/J722S/J722S_linux_config.txt b/configs/J722S/J722S_linux_config.txt index fff0a5229..fd619b5b9 100644 --- a/configs/J722S/J722S_linux_config.txt +++ b/configs/J722S/J722S_linux_config.txt @@ -14,7 +14,6 @@ Replacement Variables --------------------- '__PART_FAMILY_NAME__' : 'J722S' -'__PART_FAMILY_DEVICE_NAMES__' : 'J722S' '__PRODUCT_LINE_NAME__' : 'Jacinto' '__SDK_BUILD_MACHINE__' : 'j722s-evm' '__SDK_FULL_NAME__' : 'Processor SDK Linux J722S' diff --git a/configs/J742S2/J742S2_linux_config.txt b/configs/J742S2/J742S2_linux_config.txt index 95defe789..1d5c862b9 100644 --- a/configs/J742S2/J742S2_linux_config.txt +++ b/configs/J742S2/J742S2_linux_config.txt @@ -14,7 +14,6 @@ Replacement Variables --------------------- '__PART_FAMILY_NAME__' : 'J742S2' -'__PART_FAMILY_DEVICE_NAMES__' : 'J742S2' '__PRODUCT_LINE_NAME__' : 'Jacinto' '__SDK_BUILD_MACHINE__' : 'j742s2-evm' '__SDK_FULL_NAME__' : 'Processor SDK Linux J742s2' diff --git a/configs/J784S4/J784S4_linux_config.txt b/configs/J784S4/J784S4_linux_config.txt index dc6fba82b..9acb04ed3 100644 --- a/configs/J784S4/J784S4_linux_config.txt +++ b/configs/J784S4/J784S4_linux_config.txt @@ -14,7 +14,6 @@ Replacement Variables --------------------- '__PART_FAMILY_NAME__' : 'J784S4' -'__PART_FAMILY_DEVICE_NAMES__' : 'J784S4' '__PRODUCT_LINE_NAME__' : 'Jacinto' '__SDK_BUILD_MACHINE__' : 'j784s4-evm' '__SDK_FULL_NAME__' : 'Processor SDK Linux J784s4' diff --git a/configs/TDA4VM/TDA4VM_linux_config.txt b/configs/TDA4VM/TDA4VM_linux_config.txt index a5eaf7c48..877aa2fdb 100755 --- a/configs/TDA4VM/TDA4VM_linux_config.txt +++ b/configs/TDA4VM/TDA4VM_linux_config.txt @@ -14,7 +14,6 @@ Replacement Variables --------------------- '__PART_FAMILY_NAME__' : 'TDA4VM' -'__PART_FAMILY_DEVICE_NAMES__' : 'TDA4VM' '__PRODUCT_LINE_NAME__' : 'Jacinto' '__SDK_BUILD_MACHINE__' : 'j721e-evm' '__SDK_FULL_NAME__' : 'Processor SDK Linux SK TDA4VM'