<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="/rss.xsl.xml"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
    <title>Changes in versal_net_nvm.c</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2025</copyright>
    <generator>Java</generator><item>
        <title>b1fc8c0d90a9e10d1724acb84cd0eb70ef0f96a0 - drivers: versal_net: nvm: Add support for Versal NET</title>
        <link>http://opengrok.muzhidianzi.cn:8080/history/optee_os/core/drivers/versal_net_nvm.c#b1fc8c0d90a9e10d1724acb84cd0eb70ef0f96a0</link>
        <description>drivers: versal_net: nvm: Add support for Versal NETThe XilNvm API has heavily changed between Versal and Versal NET.Largely based on previous work byJeremie Corbier &lt;jeremie.corbier@provenrun.com&gt;.In contrast to the previous work, this commit does NOT change the in-kernelAPI (versal_nvm.h) regarding functions versal_efuse_read_revoke_id() andversal_efuse_read_offchip_revoke_id(). These functions reflect what can befound in the &quot;client&quot; side API of XilNvm for Versal _and_ Versal NET(release v2025.1). There is no difference between the two platform flavors.However, regarding function versal_efuse_write_offchip_ids(), correspondingXilNvm &quot;client&quot; side API is indeed different between Versal and VersalNET. To keep the API towards OP-TEE OS unchanged, the Versal NET versiontranslates the argument of type struct versal_efuse_offchip_ids into asingle OffChip Revoke Id eFuse bit number. Writing multiple eFuse bits isnot supported.Moreover, generally use variable names &quot;low&quot; and &quot;hi&quot; instead of &quot;a&quot; and&quot;b&quot; when handling 64 bit PLM Firmware API id parameters.Signed-off-by: Joachim Foerster &lt;joachim.foerster@missinglinkelectronics.com&gt;Signed-off-by: Dennis Ries &lt;dennis.ries@missinglinkelectronics.com&gt;Reviewed-by: Nathan Menhorn &lt;nathan.menhorn@amd.com&gt;Tested-by: Nathan Menhorn &lt;nathan.menhorn@amd.com&gt;Reviewed-by: Sean McGinn &lt;sean.mcginn@amd.com&gt;Reviewed-by: Lucas Kiker &lt;lucas.kiker@amd.com&gt;Reviewed-by: Sindhu Raveendra &lt;Sindhu.Raveendra@amd.com&gt;Reviewed-by: Clemens Nasenberg &lt;clemens.nasenberg@amd.com&gt;Reviewed-by: Jorge Ramirez-Ortiz &lt;jorge.ramirez@oss.qualcomm.com&gt;

            List of files:
            /optee_os/core/drivers/versal_net_nvm.c</description>
        <pubDate>Mon, 27 Oct 2025 10:24:39 +0000</pubDate>
        <dc:creator>Joachim Foerster &lt;joachim.foerster@missinglinkelectronics.com&gt;</dc:creator>
    </item>
<item>
        <title>13dee78b1497ac9f99654a62bdcbc0c5206d2d9d - drivers: versal_net: nvm: Duplicate Versal driver for Versal NET</title>
        <link>http://opengrok.muzhidianzi.cn:8080/history/optee_os/core/drivers/versal_net_nvm.c#13dee78b1497ac9f99654a62bdcbc0c5206d2d9d</link>
        <description>drivers: versal_net: nvm: Duplicate Versal driver for Versal NETThe XilNvm API has heavily changed between Versal and Versal NET.Signed-off-by: Joachim Foerster &lt;joachim.foerster@missinglinkelectronics.com&gt;Reviewed-by: Nathan Menhorn &lt;nathan.menhorn@amd.com&gt;Tested-by: Nathan Menhorn &lt;nathan.menhorn@amd.com&gt;Reviewed-by: Sean McGinn &lt;sean.mcginn@amd.com&gt;Reviewed-by: Lucas Kiker &lt;lucas.kiker@amd.com&gt;Reviewed-by: Sindhu Raveendra &lt;Sindhu.Raveendra@amd.com&gt;Reviewed-by: Clemens Nasenberg &lt;clemens.nasenberg@amd.com&gt;Reviewed-by: Jorge Ramirez-Ortiz &lt;jorge.ramirez@oss.qualcomm.com&gt;

            List of files:
            /optee_os/core/drivers/versal_net_nvm.c</description>
        <pubDate>Mon, 27 Oct 2025 10:30:23 +0000</pubDate>
        <dc:creator>Joachim Foerster &lt;joachim.foerster@missinglinkelectronics.com&gt;</dc:creator>
    </item>
</channel>
</rss>
