<feed xmlns='http://www.w3.org/2005/Atom'>
<title>u-boot.git/board/ti, branch next</title>
<subtitle>Unnamed repository; edit this file 'description' to name the repository.
</subtitle>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/'/>
<entry>
<title>include: env: ti: move board specific scripts out of ti_common</title>
<updated>2026-03-23T15:15:10+00:00</updated>
<author>
<name>Anshul Dalal</name>
<email>anshuld@ti.com</email>
</author>
<published>2026-03-06T12:02:37+00:00</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=e853610b560c072dd7207f2ccff01772aff1b748'/>
<id>e853610b560c072dd7207f2ccff01772aff1b748</id>
<content type='text'>
bootcmd_ti_mmc had cpsw0_qsgmii_phyinit related scripts even though this
was only relevant for the j721e/j7200 SoCs. This patch instead factors
out those scripts into a generic 'board_init' which is called as part of
bootcmd_ti_mmc.

This allows boards to more easily add custom behaviour to the ti_mmc
bootflow instead of having to modify the ti_common.env file.

Signed-off-by: Anshul Dalal &lt;anshuld@ti.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
bootcmd_ti_mmc had cpsw0_qsgmii_phyinit related scripts even though this
was only relevant for the j721e/j7200 SoCs. This patch instead factors
out those scripts into a generic 'board_init' which is called as part of
bootcmd_ti_mmc.

This allows boards to more easily add custom behaviour to the ti_mmc
bootflow instead of having to modify the ti_common.env file.

Signed-off-by: Anshul Dalal &lt;anshuld@ti.com&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>board: ti: j7*: Update rm-cfg and tifs-rm-cfg</title>
<updated>2026-03-16T16:37:29+00:00</updated>
<author>
<name>Manorit Chawdhry</name>
<email>m-chawdhry@ti.com</email>
</author>
<published>2026-02-26T11:37:57+00:00</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=c4fcf9b806aefd6ab18edca59994c5a106d5e9ff'/>
<id>c4fcf9b806aefd6ab18edca59994c5a106d5e9ff</id>
<content type='text'>
Repurpose the allocated resources with version V11.02.07 of
k3-resource-partition.

Signed-off-by: Manorit Chawdhry &lt;m-chawdhry@ti.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Repurpose the allocated resources with version V11.02.07 of
k3-resource-partition.

Signed-off-by: Manorit Chawdhry &lt;m-chawdhry@ti.com&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>Merge patch series "k3_*: Add config fragments for inline ECC and BIST"</title>
<updated>2026-03-13T22:17:15+00:00</updated>
<author>
<name>Tom Rini</name>
<email>trini@konsulko.com</email>
</author>
<published>2026-03-13T20:59:38+00:00</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=1ad466eeae393b14fd70e5c414b37ca64413bf2b'/>
<id>1ad466eeae393b14fd70e5c414b37ca64413bf2b</id>
<content type='text'>
Neha Malcom Francis &lt;n-francis@ti.com&gt; says:

Typically we do not enable these configs by default but would still like to
have the option to start building them in our default build flow for
testing. Also there is the added advantage of users being able to see what
is needed in case they choose to enable these features.

Link: https://lore.kernel.org/r/20260226122508.2269682-1-n-francis@ti.com
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Neha Malcom Francis &lt;n-francis@ti.com&gt; says:

Typically we do not enable these configs by default but would still like to
have the option to start building them in our default build flow for
testing. Also there is the added advantage of users being able to see what
is needed in case they choose to enable these features.

Link: https://lore.kernel.org/r/20260226122508.2269682-1-n-francis@ti.com
</pre>
</div>
</content>
</entry>
<entry>
<title>configs: k3_*: Add config fragments for enabling inline ECC and/or BIST</title>
<updated>2026-03-13T22:17:15+00:00</updated>
<author>
<name>Neha Malcom Francis</name>
<email>n-francis@ti.com</email>
</author>
<published>2026-02-26T12:25:07+00:00</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=e56228f32dec59d446a3f12bc1c1d7680d458f68'/>
<id>e56228f32dec59d446a3f12bc1c1d7680d458f68</id>
<content type='text'>
Add config fragment support for enabling inline ECC and/or BIST on TI K3
supported platforms.

Signed-off-by: Neha Malcom Francis &lt;n-francis@ti.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Add config fragment support for enabling inline ECC and/or BIST on TI K3
supported platforms.

Signed-off-by: Neha Malcom Francis &lt;n-francis@ti.com&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>Merge patch series "board: k3: Sync rm-cfg with TIFS v11.02.09 firmware"</title>
<updated>2026-03-13T20:58:17+00:00</updated>
<author>
<name>Tom Rini</name>
<email>trini@konsulko.com</email>
</author>
<published>2026-03-13T20:58:17+00:00</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=7403d26bea36315f2008ed3ef80125b094c0bafb'/>
<id>7403d26bea36315f2008ed3ef80125b094c0bafb</id>
<content type='text'>
Sparsh Kumar &lt;sparsh-kumar@ti.com&gt; says:

This series updates the Resource Management (RM) configuration files
for AM62 family devices to align with the TIFS v11.02.09 firmware.

Background
----------
With the latest TIFS firmware (v11.02.09), an additional virtual
interrupt and event is reserved for MCU cores to DM usage on am62x,
am62ax, and am62px devices. This series brings the rm-cfg and
tifs-rm-cfg files in sync with these firmware changes across both
TI reference boards and vendor boards.

These changes are backward compatible with older TIFS firmware versions.

Additionally, the am62x platform was originally introduced without a
tifs-rm-cfg.yaml file, unlike other platforms in the AM62 family.
This series addresses that gap and enables tifs-rm-cfg in binman for
am625-sk and am62p-sk platforms.

Changes
-------
TI reference boards (patches 1-4):
  - Update rm-cfg.yaml for am62x, am62ax, am62px
  - Sync am62px tifs-rm-cfg.yaml with TIFS firmware template
  - Add missing tifs-rm-cfg.yaml for am62x
  - Enable tifs-rm-cfg in binman for am625-sk and am62p-sk

Vendor boards (patches 5-9):
  - beagleplay (am62x-based)
  - phytec phycore_am62x
  - toradex verdin-am62
  - phytec phycore_am62ax
  - toradex verdin-am62p

with the required interrupt reservation. The tifs-rm-cfg.yaml files
cannot be updated without access to the corresponding SysConfig files,
as both rm-cfg.yaml and tifs-rm-cfg.yaml must remain in sync.

Link: https://lore.kernel.org/r/20260225132425.3096103-1-sparsh-kumar@ti.com
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Sparsh Kumar &lt;sparsh-kumar@ti.com&gt; says:

This series updates the Resource Management (RM) configuration files
for AM62 family devices to align with the TIFS v11.02.09 firmware.

Background
----------
With the latest TIFS firmware (v11.02.09), an additional virtual
interrupt and event is reserved for MCU cores to DM usage on am62x,
am62ax, and am62px devices. This series brings the rm-cfg and
tifs-rm-cfg files in sync with these firmware changes across both
TI reference boards and vendor boards.

These changes are backward compatible with older TIFS firmware versions.

Additionally, the am62x platform was originally introduced without a
tifs-rm-cfg.yaml file, unlike other platforms in the AM62 family.
This series addresses that gap and enables tifs-rm-cfg in binman for
am625-sk and am62p-sk platforms.

Changes
-------
TI reference boards (patches 1-4):
  - Update rm-cfg.yaml for am62x, am62ax, am62px
  - Sync am62px tifs-rm-cfg.yaml with TIFS firmware template
  - Add missing tifs-rm-cfg.yaml for am62x
  - Enable tifs-rm-cfg in binman for am625-sk and am62p-sk

Vendor boards (patches 5-9):
  - beagleplay (am62x-based)
  - phytec phycore_am62x
  - toradex verdin-am62
  - phytec phycore_am62ax
  - toradex verdin-am62p

with the required interrupt reservation. The tifs-rm-cfg.yaml files
cannot be updated without access to the corresponding SysConfig files,
as both rm-cfg.yaml and tifs-rm-cfg.yaml must remain in sync.

Link: https://lore.kernel.org/r/20260225132425.3096103-1-sparsh-kumar@ti.com
</pre>
</div>
</content>
</entry>
<entry>
<title>board: ti: am62x: tifs-rm-cfg: Add the missing tifs-rm-cfg:</title>
<updated>2026-03-13T20:57:20+00:00</updated>
<author>
<name>Sparsh Kumar</name>
<email>sparsh-kumar@ti.com</email>
</author>
<published>2026-02-25T13:24:19+00:00</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=964bda9e805de2716b9aba8d67759218feb5a7ab'/>
<id>964bda9e805de2716b9aba8d67759218feb5a7ab</id>
<content type='text'>
The am62x platform was originally introduced without a
tifs-rm-cfg.yaml file. Add the tifs-rm-cfg to bring am62x
in line with other am62 family of devices (am62px and am62a)
which all include this file.

This complements the rm-cfg update earlier in this series.

Signed-off-by: Sparsh Kumar &lt;sparsh-kumar@ti.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
The am62x platform was originally introduced without a
tifs-rm-cfg.yaml file. Add the tifs-rm-cfg to bring am62x
in line with other am62 family of devices (am62px and am62a)
which all include this file.

This complements the rm-cfg update earlier in this series.

Signed-off-by: Sparsh Kumar &lt;sparsh-kumar@ti.com&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>board: ti: am62px: tifs-rm-cfg: Sync tifs-rm-cfg with TIFS firmware updates</title>
<updated>2026-03-13T20:57:20+00:00</updated>
<author>
<name>Sparsh Kumar</name>
<email>sparsh-kumar@ti.com</email>
</author>
<published>2026-02-25T13:24:18+00:00</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=f2c4fb442d058be9acefe61ed64d7abcdad885e3'/>
<id>f2c4fb442d058be9acefe61ed64d7abcdad885e3</id>
<content type='text'>
Synchronize tifs-rm-cfg file with the latest v11.02.09
TIFS firmware rm configuration:

 - Update am62px tifs-rm-cfg with revised resource allocations
 - Apply formatting updates to align with TIFS template

This brings tifs-rm-cfg in sync with the rm-cfg changes
earlier in this series.

Signed-off-by: Sparsh Kumar &lt;sparsh-kumar@ti.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Synchronize tifs-rm-cfg file with the latest v11.02.09
TIFS firmware rm configuration:

 - Update am62px tifs-rm-cfg with revised resource allocations
 - Apply formatting updates to align with TIFS template

This brings tifs-rm-cfg in sync with the rm-cfg changes
earlier in this series.

Signed-off-by: Sparsh Kumar &lt;sparsh-kumar@ti.com&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>board: ti: rm-cfg: Update rm-cfg to reflect new resource reservation</title>
<updated>2026-03-13T20:57:20+00:00</updated>
<author>
<name>Sparsh Kumar</name>
<email>sparsh-kumar@ti.com</email>
</author>
<published>2026-02-25T13:24:17+00:00</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=7f9c2a6f7be787cdd87a4d640354ca205dc8ccb3'/>
<id>7f9c2a6f7be787cdd87a4d640354ca205dc8ccb3</id>
<content type='text'>
With the latest v11.02.09 TIFS firmware, an additional
virtual interrupt and event is reserved for MCU cores
to DM usage on am62x, am62ax and am62px devices.

Update the rm-cfg to reflect this new reservation.

Signed-off-by: Sparsh Kumar &lt;sparsh-kumar@ti.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
With the latest v11.02.09 TIFS firmware, an additional
virtual interrupt and event is reserved for MCU cores
to DM usage on am62x, am62ax and am62px devices.

Update the rm-cfg to reflect this new reservation.

Signed-off-by: Sparsh Kumar &lt;sparsh-kumar@ti.com&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>arm: k3: Kconfig: Enable fTPM and RPMB support</title>
<updated>2026-03-10T18:35:18+00:00</updated>
<author>
<name>Shiva Tripathi</name>
<email>s-tripathi1@ti.com</email>
</author>
<published>2026-02-25T11:24:38+00:00</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=8bc2a5196c1c0bb5dbdaca073323da0015a0de37'/>
<id>8bc2a5196c1c0bb5dbdaca073323da0015a0de37</id>
<content type='text'>
Enable firmware TPM (fTPM) support via OP-TEE for K3 platforms with
MMC hardware. This provides TPM 2.0 functionality through
Microsoft's fTPM Trusted Application running in OP-TEE secure world,
using eMMC RPMB as persistent storage.

fTPM support in U-Boot provides the foundation for measured boot
and disk encryption use cases.

The ARM64 condition ensures these apply only to A53/A72 cores and the
MMC condition ensures fTPM is enabled only on platforms with eMMC
hardware support.

Signed-off-by: Shiva Tripathi &lt;s-tripathi1@ti.com&gt;
Acked-by: Andrew Davis &lt;afd@ti.com&gt;
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Enable firmware TPM (fTPM) support via OP-TEE for K3 platforms with
MMC hardware. This provides TPM 2.0 functionality through
Microsoft's fTPM Trusted Application running in OP-TEE secure world,
using eMMC RPMB as persistent storage.

fTPM support in U-Boot provides the foundation for measured boot
and disk encryption use cases.

The ARM64 condition ensures these apply only to A53/A72 cores and the
MMC condition ensures fTPM is enabled only on platforms with eMMC
hardware support.

Signed-off-by: Shiva Tripathi &lt;s-tripathi1@ti.com&gt;
Acked-by: Andrew Davis &lt;afd@ti.com&gt;
</pre>
</div>
</content>
</entry>
<entry>
<title>Merge tag 'v2026.04-rc3' into next</title>
<updated>2026-02-23T19:45:55+00:00</updated>
<author>
<name>Tom Rini</name>
<email>trini@konsulko.com</email>
</author>
<published>2026-02-23T19:45:55+00:00</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=15bd3258174b8c8791d7779f66d26ece9545b1c0'/>
<id>15bd3258174b8c8791d7779f66d26ece9545b1c0</id>
<content type='text'>
Prepare v2026.04-rc3
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Prepare v2026.04-rc3
</pre>
</div>
</content>
</entry>
</feed>
