<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/meta-ti.git/meta-ti-bsp/conf/machine/include/am62axx.inc, branch master</title>
<subtitle>Mirror of git.yoctoproject.org/meta-ti.git</subtitle>
<id>https://git.enea.com/cgit/linux/meta-ti.git/atom?h=master</id>
<link rel='self' href='https://git.enea.com/cgit/linux/meta-ti.git/atom?h=master'/>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-ti.git/'/>
<updated>2026-05-12T13:33:48+00:00</updated>
<entry>
<title>trusted-firmware-a: Remove TFA_K3_SYSTEM_SUSPEND build flag</title>
<updated>2026-05-12T13:33:48+00:00</updated>
<author>
<name>Andrew Davis</name>
<email>afd@ti.com</email>
</author>
<published>2026-05-05T18:33:58+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-ti.git/commit/?id=06a120f251492bb85a85ff5919879d535091ba06'/>
<id>urn:sha1:06a120f251492bb85a85ff5919879d535091ba06</id>
<content type='text'>
All supported TF-A handle this automatically based on the firmware, the
flag no longer does anything as it isn't checked in TF-A now. Remove this.

Signed-off-by: Andrew Davis &lt;afd@ti.com&gt;
Signed-off-by: Ryan Eatmon &lt;reatmon@ti.com&gt;
</content>
</entry>
<entry>
<title>ti-core-initramfs: Rework logic</title>
<updated>2026-02-12T14:56:40+00:00</updated>
<author>
<name>Ryan Eatmon</name>
<email>reatmon@ti.com</email>
</author>
<published>2026-02-11T17:58:17+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-ti.git/commit/?id=300f2a8d00287c79919e73b4692797b0a9f82f23'/>
<id>urn:sha1:300f2a8d00287c79919e73b4692797b0a9f82f23</id>
<content type='text'>
Clean up the logic of the new ti-core-initramfs to reduce the impact on
downstream layers.

- Flip the logic in the machine .conf files to track the list of
  required kernel modules for that platform, but if the variable is set
  to "" then the ti-core-initramfs will not be created.

- Redo the logic of when we require creation/usage of the initramfs to
  just platforms that need it (ie that set TI_CORE_INITRAMFS_KERNEL_MODULES).

- Add a big switch to disable the initramfs entirely.  In that case, the
  user is on their own to make sure that the kernel has everything it
  needs to boot either via config fragments to turn on the needed
  modules, or by using the TI_CORE_INITRAMFS_KERNEL_MODULES
  variable to populate their own initramfs.

Signed-off-by: Ryan Eatmon &lt;reatmon@ti.com&gt;
</content>
</entry>
<entry>
<title>conf: Add support for bsp-ti-6_18 to ti-core-initramfs</title>
<updated>2026-01-12T21:01:47+00:00</updated>
<author>
<name>Ryan Eatmon</name>
<email>reatmon@ti.com</email>
</author>
<published>2026-01-09T18:14:13+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-ti.git/commit/?id=ce6dccea3b3a16329f6b444300d5b163a09b3c0d'/>
<id>urn:sha1:ce6dccea3b3a16329f6b444300d5b163a09b3c0d</id>
<content type='text'>
With the 6.18 we are moving to using an initramfs to provide non-default
modules for booting.  So add that override to the machines that need it.

Signed-off-by: Ryan Eatmon &lt;reatmon@ti.com&gt;
</content>
</entry>
<entry>
<title>am62axx.inc: Add TPS6594 regulator and core modules to initramfs image</title>
<updated>2025-12-19T15:57:39+00:00</updated>
<author>
<name>Moteen Shah</name>
<email>m-shah@ti.com</email>
</author>
<published>2025-12-02T05:59:07+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-ti.git/commit/?id=3073bf9e290b9199baa4b35b5c684c3e1ca211ef'/>
<id>urn:sha1:3073bf9e290b9199baa4b35b5c684c3e1ca211ef</id>
<content type='text'>
Add TPS6594 core and regulator driver modules in the initramfs image so
that the SD card can be probed for am62axx as it is dependent on regulator
to get the SD card probing and eventually boot from it.

Signed-off-by: Moteen Shah &lt;m-shah@ti.com&gt;
Signed-off-by: Ryan Eatmon &lt;reatmon@ti.com&gt;
</content>
</entry>
<entry>
<title>am62axx: Add whitespace to append assignment</title>
<updated>2025-10-24T18:59:24+00:00</updated>
<author>
<name>Ryan Eatmon</name>
<email>reatmon@ti.com</email>
</author>
<published>2025-10-24T16:17:26+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-ti.git/commit/?id=f308333e689570603cc74662e0ddfe7098915381'/>
<id>urn:sha1:f308333e689570603cc74662e0ddfe7098915381</id>
<content type='text'>
Add missing whitespace on append assignment since the list is space
separated.

Signed-off-by: Ryan Eatmon &lt;reatmon@ti.com&gt;
</content>
</entry>
<entry>
<title>meta-ti-bsp: conf: machine: include: Add common module variable for TI Initramfs image</title>
<updated>2025-10-21T23:43:29+00:00</updated>
<author>
<name>Moteen Shah</name>
<email>m-shah@ti.com</email>
</author>
<published>2025-10-15T12:00:29+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-ti.git/commit/?id=d9a2eb289ba4d6b0d33ace0c8e3d29607fa5b6f6'/>
<id>urn:sha1:d9a2eb289ba4d6b0d33ace0c8e3d29607fa5b6f6</id>
<content type='text'>
Add a new variable in ti-soc.inc which would be populated by individual
platforms with the required modules which would later be packaged inside
the initramfs image.

Signed-off-by: Moteen Shah &lt;m-shah@ti.com&gt;
Signed-off-by: Ryan Eatmon &lt;reatmon@ti.com&gt;
</content>
</entry>
<entry>
<title>meta-ti-bsp: Add all tiboot3.bin and sysfw.itb variants by wildcard</title>
<updated>2025-08-19T14:00:28+00:00</updated>
<author>
<name>Andrew Davis</name>
<email>afd@ti.com</email>
</author>
<published>2025-08-18T19:01:46+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-ti.git/commit/?id=10436a27a2e0aec4eedc6aab82b9e1911cf79155'/>
<id>urn:sha1:10436a27a2e0aec4eedc6aab82b9e1911cf79155</id>
<content type='text'>
U-Boot generates all the valid versions of tiboot3.bin and sysfw.itb
based on the given defconfig. The defaults are also picked based on
the board's binman files. No need to duplicate this logic here,
simply deploy what U-Boot generates.

Signed-off-by: Andrew Davis &lt;afd@ti.com&gt;
Signed-off-by: Ryan Eatmon &lt;reatmon@ti.com&gt;
</content>
</entry>
<entry>
<title>conf: machine: am62axx: Exclude tiboot3.bin for GP</title>
<updated>2025-04-23T19:21:16+00:00</updated>
<author>
<name>Chirag Shilwant</name>
<email>c-shilwant@ti.com</email>
</author>
<published>2025-04-23T01:35:10+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-ti.git/commit/?id=c80e3d4b8171a0bcc205cf5b47067779981a9829'/>
<id>urn:sha1:c80e3d4b8171a0bcc205cf5b47067779981a9829</id>
<content type='text'>
* The GP variant of AM62A SoC was only used internally
for initial device bring-up and is not publicly available.
Hence, drop it from IMAGE_BOOT_FILES to ensure
tiboot3-am62ax-gp-evm.bin is not packaged inside vfat boot
partition of wic image

Signed-off-by: Chirag Shilwant &lt;c-shilwant@ti.com&gt;
Reviewed-by: Denys Dmytriyenko &lt;denys@konsulko.com&gt;
Signed-off-by: Ryan Eatmon &lt;reatmon@ti.com&gt;
</content>
</entry>
<entry>
<title>conf: machine: Remove multiconfig compulsion for k3 platforms</title>
<updated>2024-09-13T15:38:39+00:00</updated>
<author>
<name>Chirag Shilwant</name>
<email>c-shilwant@ti.com</email>
</author>
<published>2024-09-12T20:07:51+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-ti.git/commit/?id=82e8543cdcec09f1fe95fd2c937121ed3c513c22'/>
<id>urn:sha1:82e8543cdcec09f1fe95fd2c937121ed3c513c22</id>
<content type='text'>
- While implementing k3.inc, there was an assumption that all
k3 based TI SOC's would always have a Cortex-R5F core [1]. This
assumption is not true.

- Hence, create a new mc_k3r5 include file &amp; move the multiconfig
dependencies to it. Also, include this file only in those k3 platforms
which needs the R5 multiconfig support.

[1]: https://git.ti.com/cgit/arago-project/meta-ti/commit/conf/machine/include/k3.inc?h=scarthgap&amp;id=f814840465358a6b5429ad20165742ac6e6e6a29

Signed-off-by: Chirag Shilwant &lt;c-shilwant@ti.com&gt;
Signed-off-by: Ryan Eatmon &lt;reatmon@ti.com&gt;
</content>
</entry>
<entry>
<title>conf: machine: move RDEPENDS and RRECOMMENDS from kernel-rdepends.inc</title>
<updated>2023-10-24T14:56:09+00:00</updated>
<author>
<name>Denys Dmytriyenko</name>
<email>denys@konsulko.com</email>
</author>
<published>2023-10-23T22:38:16+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/meta-ti.git/commit/?id=ef80a01ba0294d9f9c045c252ecef7883198b0cb'/>
<id>urn:sha1:ef80a01ba0294d9f9c045c252ecef7883198b0cb</id>
<content type='text'>
Instead of making kernel RDEPENDS on devicetree and different FW images with
lots of machine-override appends that are hard to modify downstream, use proper
MACHINE_ESSENTIAL_EXTRA_RDEPENDS and MACHINE_ESSENTIAL_EXTRA_RRECOMMENDS vars
that are specifically designed for this purpose.

This also makes such dependencies generic and not tied to a particular kernel
recipe including kernel-rdepends.inc with the entire machine-specific list.

Signed-off-by: Denys Dmytriyenko &lt;denys@konsulko.com&gt;
Acked-by: Andrew Davis &lt;afd@ti.com&gt;
Acked-by: Ryan Eatmon &lt;reatmon@ti.com&gt;
Signed-off-by: Ryan Eatmon &lt;reatmon@ti.com&gt;
</content>
</entry>
</feed>
