<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>S32G中的主题 Regarding PFE Driver feature value on S32G2</title>
    <link>https://community.nxp.com/t5/S32G/Regarding-PFE-Driver-feature-value-on-S32G2/m-p/2062590#M12953</link>
    <description>&lt;P&gt;Hello NXP Support Team,&lt;/P&gt;&lt;P&gt;We are currently working with the PFE driver (version 1.5.0) and PFE firmware (version 1.7.0) on S32G2 , we have a query on the function &lt;STRONG&gt;pfe_hw_feature_get_val&lt;/STRONG&gt;&amp;nbsp;from PFE driver 1.5.0 shown below:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;/**
 * @brief Reads value of the feature enable variable
 * [in]  feature  Feature to read the value
 * [out] val      Value read from the DMEM
 * @return EOK or an error code.
 */
errno_t pfe_hw_feature_get_val(const pfe_hw_feature_t *feature, uint8_t *val)
{
    errno_t ret;
#if defined(PFE_CFG_NULL_ARG_CHECK)
    if ((NULL == feature) || (NULL == val))
    {
        NXP_LOG_ERROR("NULL argument received\n");
        ret = EINVAL;
    }
    else
#endif
    {
        NXP_LOG_ERROR("Getting feature value for: %s\n", feature-&amp;gt;name);
        *val = feature-&amp;gt;val;    // &amp;lt;----------- Value is set here
        ret = EOK;
    }
    return ret;
}&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We have observed that on S32G3, this function sets val to 1. Given that both the driver and feature name are the same on S32G2 and S32G3 (as referenced here: &lt;A href="https://github.com/nxp-auto-linux/pfeng/blob/release/linux_1.5.0/sw/pfe_platform/hw/s32g/pfe_tmu_csr.c" target="_blank" rel="noopener"&gt;linux_1.5.0/sw/pfe_platform/hw/s32g/pfe_tmu_csr.c&lt;/A&gt;&amp;nbsp;line 158 `if (FALSE == pfe_feature_mgr_is_available(PFE_HW_FEATURE_RUN_ON_G3))` ), we would like to confirm the correct value on S32G2.&lt;/P&gt;&lt;P&gt;Could you please clarify if this feature `&lt;SPAN&gt;drv_run_on_g3`&lt;/SPAN&gt; should also be set to 1 on S32G2, or if there is a different expected value for that platform? Any guidance or documentation you can provide would be greatly appreciated.&lt;/P&gt;&lt;P&gt;Thank you for your time and assistance. we look forward to hearing from you.&lt;/P&gt;&lt;P&gt;Best regards,&lt;/P&gt;</description>
    <pubDate>Mon, 17 Mar 2025 00:24:28 GMT</pubDate>
    <dc:creator>s153022</dc:creator>
    <dc:date>2025-03-17T00:24:28Z</dc:date>
    <item>
      <title>Regarding PFE Driver feature value on S32G2</title>
      <link>https://community.nxp.com/t5/S32G/Regarding-PFE-Driver-feature-value-on-S32G2/m-p/2062590#M12953</link>
      <description>&lt;P&gt;Hello NXP Support Team,&lt;/P&gt;&lt;P&gt;We are currently working with the PFE driver (version 1.5.0) and PFE firmware (version 1.7.0) on S32G2 , we have a query on the function &lt;STRONG&gt;pfe_hw_feature_get_val&lt;/STRONG&gt;&amp;nbsp;from PFE driver 1.5.0 shown below:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;/**
 * @brief Reads value of the feature enable variable
 * [in]  feature  Feature to read the value
 * [out] val      Value read from the DMEM
 * @return EOK or an error code.
 */
errno_t pfe_hw_feature_get_val(const pfe_hw_feature_t *feature, uint8_t *val)
{
    errno_t ret;
#if defined(PFE_CFG_NULL_ARG_CHECK)
    if ((NULL == feature) || (NULL == val))
    {
        NXP_LOG_ERROR("NULL argument received\n");
        ret = EINVAL;
    }
    else
#endif
    {
        NXP_LOG_ERROR("Getting feature value for: %s\n", feature-&amp;gt;name);
        *val = feature-&amp;gt;val;    // &amp;lt;----------- Value is set here
        ret = EOK;
    }
    return ret;
}&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We have observed that on S32G3, this function sets val to 1. Given that both the driver and feature name are the same on S32G2 and S32G3 (as referenced here: &lt;A href="https://github.com/nxp-auto-linux/pfeng/blob/release/linux_1.5.0/sw/pfe_platform/hw/s32g/pfe_tmu_csr.c" target="_blank" rel="noopener"&gt;linux_1.5.0/sw/pfe_platform/hw/s32g/pfe_tmu_csr.c&lt;/A&gt;&amp;nbsp;line 158 `if (FALSE == pfe_feature_mgr_is_available(PFE_HW_FEATURE_RUN_ON_G3))` ), we would like to confirm the correct value on S32G2.&lt;/P&gt;&lt;P&gt;Could you please clarify if this feature `&lt;SPAN&gt;drv_run_on_g3`&lt;/SPAN&gt; should also be set to 1 on S32G2, or if there is a different expected value for that platform? Any guidance or documentation you can provide would be greatly appreciated.&lt;/P&gt;&lt;P&gt;Thank you for your time and assistance. we look forward to hearing from you.&lt;/P&gt;&lt;P&gt;Best regards,&lt;/P&gt;</description>
      <pubDate>Mon, 17 Mar 2025 00:24:28 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32G/Regarding-PFE-Driver-feature-value-on-S32G2/m-p/2062590#M12953</guid>
      <dc:creator>s153022</dc:creator>
      <dc:date>2025-03-17T00:24:28Z</dc:date>
    </item>
    <item>
      <title>Re: Regarding PFE Driver feature value on S32G2</title>
      <link>https://community.nxp.com/t5/S32G/Regarding-PFE-Driver-feature-value-on-S32G2/m-p/2063319#M12970</link>
      <description>&lt;P&gt;hi,&lt;SPAN&gt;s153022&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;According to the definition in the source file, this is only applicable to the S32G3, it is recommended to check the driver and firmware user manual.&lt;/P&gt;
&lt;P&gt;BR&lt;/P&gt;
&lt;P&gt;Joey&lt;/P&gt;</description>
      <pubDate>Tue, 18 Mar 2025 02:03:26 GMT</pubDate>
      <guid>https://community.nxp.com/t5/S32G/Regarding-PFE-Driver-feature-value-on-S32G2/m-p/2063319#M12970</guid>
      <dc:creator>Joey_z</dc:creator>
      <dc:date>2025-03-18T02:03:26Z</dc:date>
    </item>
  </channel>
</rss>

