<feed xmlns='http://www.w3.org/2005/Atom'>
<title>u-boot.git/drivers/firmware/scmi, branch v2026.04</title>
<subtitle>Unnamed repository; edit this file 'description' to name the repository.</subtitle>
<id>http://cgit.235523.xyz/u-boot.git/atom/drivers/firmware/scmi?h=v2026.04</id>
<link rel='self' href='http://cgit.235523.xyz/u-boot.git/atom/drivers/firmware/scmi?h=v2026.04'/>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/'/>
<updated>2026-02-26T15:04:46Z</updated>
<entry>
<title>firmware: scmi: Validate device tree node before setup channel</title>
<updated>2026-02-26T15:04:46Z</updated>
<author>
<name>Peng Fan</name>
<email>peng.fan@nxp.com</email>
</author>
<published>2026-02-10T08:12:14Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=3ee1408eeb7352d770bbf063df85fa23cd6b79a4'/>
<id>urn:sha1:3ee1408eeb7352d770bbf063df85fa23cd6b79a4</id>
<content type='text'>
SCMI base protocol device does not have a device tree, it should use and
need to use the agent base channel.

For scmi_base.[x], there is no real device tree node for it. ofnode_null() is
assigned as the device tree node for scmi base protocol device:
commit 7eb4eb541c14 ("firmware: scmi: install base protocol to SCMI agent")

However with recent update in commit 0535e46d55d7
("scripts/dtc: Update to upstream version v1.7.2-35-g52f07dcca47c"),
SPL panic in fdt_check_node_offset_()-&gt;fdt_next_tag(), because offset is -1
and SPL_OF_LIBFDT_ASSUME_MASK is 0xFF.

So add a check in x_get_channel() to validate the protocol devices'
ofnode.

Reported-by: Ye Li &lt;ye.li@nxp.com&gt;
Closes: https://lore.kernel.org/u-boot/939a9696-27fa-45a1-b428-feffe21ac6d5@oss.nxp.com/
Signed-off-by: Peng Fan &lt;peng.fan@nxp.com&gt;
</content>
</entry>
<entry>
<title>firmware: scmi: sandbox: Use scmi_clk_state_in_v2</title>
<updated>2026-01-28T06:28:01Z</updated>
<author>
<name>Peng Fan</name>
<email>peng.fan@nxp.com</email>
</author>
<published>2025-12-17T08:13:23Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=8e918cbe7a1cb87d0b18df91ed1edec9fff2f941'/>
<id>urn:sha1:8e918cbe7a1cb87d0b18df91ed1edec9fff2f941</id>
<content type='text'>
The sandbox scmi clock protocol use version 3.0, so need to use
scmi_clk_state_in_v2.

Signed-off-by: Peng Fan &lt;peng.fan@nxp.com&gt;
Reviewed-by: Marek Vasut &lt;marek.vasut+renesas@mailbox.org&gt;
</content>
</entry>
<entry>
<title>firmware: scmi: Add clock v3.2 CONFIG_SET support</title>
<updated>2025-11-10T12:57:42Z</updated>
<author>
<name>Vinh Nguyen</name>
<email>vinh.nguyen.xz@renesas.com</email>
</author>
<published>2025-11-05T03:42:26Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=0619cb32030b1d78379f3181d3e1103bb86124fb'/>
<id>urn:sha1:0619cb32030b1d78379f3181d3e1103bb86124fb</id>
<content type='text'>
SCMI v3.2 introduces a new clock CONFIG_SET message format that can
optionally carry also OEM specific configuration values beside the usual
clock enable/disable requests. Add support to use such new format when
talking to a v3.2 compliant SCMI platform.

Support existing enable/disable operations across different clock protocol
versions: this patch still does not add protocol operations to support the
new OEM specific optional configuration capabilities.

No functional change for the SCMI drivers users of the related enable and
disable clock operations.

[Marek: Remodel after Linux e49e314a2cf7 ("firmware: arm_scmi: Add clock v3.2 CONFIG_SET support")
        Support both old &lt; 2.1 and new &gt;= 2.1 protocol versions.
	Update commit message based on Linux one]

Signed-off-by: Vinh Nguyen &lt;vinh.nguyen.xz@renesas.com&gt;
Signed-off-by: Marek Vasut &lt;marek.vasut+renesas@mailbox.org&gt;
Reviewed-by: Alice Guo &lt;alice.guo@nxp.com&gt;
Signed-off-by: Peng Fan &lt;peng.fan@nxp.com&gt;
</content>
</entry>
<entry>
<title>firmware: scmi: Drop mmu_set_region_dcache_behaviour() misuse</title>
<updated>2025-11-10T12:57:42Z</updated>
<author>
<name>Marek Vasut</name>
<email>marek.vasut+renesas@mailbox.org</email>
</author>
<published>2025-10-25T21:35:09Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=a5a0134570c88cd49a6fc97256764cb7fbb93dff'/>
<id>urn:sha1:a5a0134570c88cd49a6fc97256764cb7fbb93dff</id>
<content type='text'>
MMU region cache behavior configuration for SCMI/SMT mailboxes is
platform specific. Even on ARM systems, the mailbox memory may not
even be located in any cacheable MMU region and may instead reside
in some SRAM. Remove this non-generic cache behavior configuration
code from generic code path.

It is unlikely that any platform is affected by this change if it
did configure its MMU regions correctly on start up. Platforms
which might be affected are i.MX94/95 and STM32MP.

Fixes: 240720e9052f ("firmware: scmi: mailbox/smt agent device")
Fixes: 2a3f161c8b16 ("scmi: correctly configure MMU for SCMI buffer")
Fixes: b2ae10970d40 ("firmware: scmi: use PAGE_SIZE alignment for ARM64")
Signed-off-by: Marek Vasut &lt;marek.vasut+renesas@mailbox.org&gt;
Tested-by: Alice Guo &lt;alice.guo@nxp.com&gt;
Tested-by: Patrice Chotard &lt;patrice.chotard@foss.st.com&gt;
Signed-off-by: Peng Fan &lt;peng.fan@nxp.com&gt;
</content>
</entry>
<entry>
<title>firmware: scmi: Add i.MX95 SCMI CPU Protocol</title>
<updated>2025-10-24T19:47:50Z</updated>
<author>
<name>Peng Fan</name>
<email>peng.fan@nxp.com</email>
</author>
<published>2025-10-17T09:32:34Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=ac9b02dd1028d14b6326970c93dfc3c50daa16f1'/>
<id>urn:sha1:ac9b02dd1028d14b6326970c93dfc3c50daa16f1</id>
<content type='text'>
This protocol allows an agent to start, stop a CPU or set reset vector.
It is used to manage auxiliary CPUs in an LM (e.g. additional cores in an
AP cluster).

Signed-off-by: Peng Fan &lt;peng.fan@nxp.com&gt;
Reviewed-by: Alice Guo &lt;alice.guo@nxp.com&gt;
</content>
</entry>
<entry>
<title>firmware: scmi: Add i.MX95 SCMI LMM protocol driver</title>
<updated>2025-10-24T19:47:50Z</updated>
<author>
<name>Peng Fan</name>
<email>peng.fan@nxp.com</email>
</author>
<published>2025-10-17T09:32:33Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=3f20ea3675c466ab16761c9b280e6c382bae02c3'/>
<id>urn:sha1:3f20ea3675c466ab16761c9b280e6c382bae02c3</id>
<content type='text'>
Add Logical Machine Management(LMM) protocol which is intended for boot,
shutdown, and reset of other logical machines (LM). It is usually used to
allow one LM to manager another used as an offload or accelerator engine.

Following Linux Kernel, created a separate folder for holding vendor
protocol drivers.

Signed-off-by: Peng Fan &lt;peng.fan@nxp.com&gt;
Reviewed-by: Alice Guo &lt;alice.guo@nxp.com&gt;
</content>
</entry>
<entry>
<title>firmware: scmi: Support probe vendor ID 0x80 and 0x82</title>
<updated>2025-10-24T19:47:50Z</updated>
<author>
<name>Peng Fan</name>
<email>peng.fan@nxp.com</email>
</author>
<published>2025-10-17T09:32:32Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=7830ccc77a13dd2a9880a942734bb5687416c4d8'/>
<id>urn:sha1:7830ccc77a13dd2a9880a942734bb5687416c4d8</id>
<content type='text'>
Preparing to add i.MX LMM and CPU protocol driver, support probe SCMI
vendor ID 0x80(i.MX SCMI LMM ID) and 0x82(i.MX SCMI CPU ID). And use
Kconfig option to support conditional compilation.

Signed-off-by: Peng Fan &lt;peng.fan@nxp.com&gt;
Reviewed-by: Alice Guo &lt;alice.guo@nxp.com&gt;
</content>
</entry>
<entry>
<title>firmware: scmi: Conditionally compile protocol support</title>
<updated>2025-10-24T19:47:50Z</updated>
<author>
<name>Peng Fan</name>
<email>peng.fan@nxp.com</email>
</author>
<published>2025-10-17T09:32:30Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=251dd6bf0e89a587710fa7bfa320088617f8854e'/>
<id>urn:sha1:251dd6bf0e89a587710fa7bfa320088617f8854e</id>
<content type='text'>
Add conditional compilation for SCMI protocol support in scmi_get_protocol()
and scmi_add_protocol() based on corresponding Kconfig options. This ensures
that only the enabled protocols are compiled and accessed, and reducing binary
size.

Signed-off-by: Peng Fan &lt;peng.fan@nxp.com&gt;
Reviewed-by: Alice Guo &lt;alice.guo@nxp.com&gt;
</content>
</entry>
<entry>
<title>firmware: scmi: mailbox: Support arm,max_rx_timeout_ms</title>
<updated>2025-10-09T20:16:11Z</updated>
<author>
<name>Peng Fan</name>
<email>peng.fan@nxp.com</email>
</author>
<published>2025-09-26T16:06:20Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=5e9fb0e5835ace9f9f7c6eceb3dd4cabc17487d4'/>
<id>urn:sha1:5e9fb0e5835ace9f9f7c6eceb3dd4cabc17487d4</id>
<content type='text'>
Per devicetree bindings:
arm,max-rx-timeout-ms indicates an optional time value, expressed in
milliseconds, representing the transport maximum timeout value for the
receive channel. The value should be a non-zero value if set.

Support this property if platform set it to a non-default value. This
property is a per SCMI property, so all channels share same value.

Signed-off-by: Peng Fan &lt;peng.fan@nxp.com&gt;
Reviewed-by: Tom Rini &lt;trini@konsulko.com&gt;
</content>
</entry>
<entry>
<title>firmware: scmi: mailbox: Update timeout to 30ms</title>
<updated>2025-10-09T20:16:11Z</updated>
<author>
<name>Peng Fan</name>
<email>peng.fan@nxp.com</email>
</author>
<published>2025-09-26T16:06:19Z</published>
<link rel='alternate' type='text/html' href='http://cgit.235523.xyz/u-boot.git/commit/?id=f116ec5b9105ffa4792bfced12aab822e492ff5f'/>
<id>urn:sha1:f116ec5b9105ffa4792bfced12aab822e492ff5f</id>
<content type='text'>
Following Linux Kernel drivers/firmware/arm_scmi/transports/mailbox.c to
set the default timeout to 30ms.

Signed-off-by: Peng Fan &lt;peng.fan@nxp.com&gt;
</content>
</entry>
</feed>
