<?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>i.MX ProcessorsのトピックRe: LVDS_PHY_CTRL sharing</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/LVDS-PHY-CTRL-sharing/m-p/1768053#M216777</link>
    <description>&lt;P&gt;Thanks for the reply, but we need to share it as the subject is&lt;/P&gt;</description>
    <pubDate>Mon, 04 Dec 2023 08:00:36 GMT</pubDate>
    <dc:creator>krassimirestoya</dc:creator>
    <dc:date>2023-12-04T08:00:36Z</dc:date>
    <item>
      <title>LVDS_PHY_CTRL sharing</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/LVDS-PHY-CTRL-sharing/m-p/1760654#M216079</link>
      <description>&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;We are trying to share access to LVDS_PHY_CTRL regster, owner by the A35 partition under Linux (Yocto). We want to access it via SCU board_ioctl or CM4 directly, if possible:&lt;/P&gt;&lt;P&gt;this is from board_ioctl:&lt;/P&gt;&lt;P&gt;        BRD_ERR(rm_set_peripheral_permissions(PWR_PT_6, SC_R_MIPI_0, SC_RM_PT_ALL, SC_RM_PERM_FULL)); // success&lt;BR /&gt;        BRD_ERR(rm_set_peripheral_permissions(PWR_PT_6, SC_R_MIPI_1, SC_RM_PT_ALL, SC_RM_PERM_FULL)); // success&lt;BR /&gt;        BRD_ERR(rm_set_peripheral_permissions(PWR_PT_6, SC_R_LVDS_0, SC_RM_PT_ALL, SC_RM_PERM_FULL)); // Fails with SC_ERR_PARM&lt;BR /&gt;        BRD_ERR(rm_set_peripheral_permissions(PWR_PT_6, SC_R_LVDS_1, SC_RM_PT_ALL, SC_RM_PERM_FULL)); // Fails with SC_ERR_PARM&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;        volatile int *p = (volatile int *)0x56221000; //LVDS_PHY_CTRL&lt;BR /&gt;        *p = 0;&lt;BR /&gt;        p = (volatile int *)0x56241000;&lt;BR /&gt;        *p = 0;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This code causes SCU to crash&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 21 Nov 2023 10:21:15 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/LVDS-PHY-CTRL-sharing/m-p/1760654#M216079</guid>
      <dc:creator>krassimirestoya</dc:creator>
      <dc:date>2023-11-21T10:21:15Z</dc:date>
    </item>
    <item>
      <title>Re: LVDS_PHY_CTRL sharing</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/LVDS-PHY-CTRL-sharing/m-p/1767402#M216714</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;There are few hints that can help narrow this issue:&lt;/P&gt;
&lt;P&gt;1. They suggestion is to ensure is to enabled power domain to access the register.&lt;/P&gt;
&lt;P&gt;2. SC_ERR_PARM means bad parameter or combination of parameters&lt;/P&gt;
&lt;P&gt;I am looking into SDK. I am working on getting to run example (dpu_blitblend) which controls register LVDS_PHY_CTRL from M4 core - Visteon's use-case. You have to try to extract specific setting needed.&lt;/P&gt;
&lt;P&gt;But in the meantime, you&amp;nbsp; can see into example source code (attached) and use it as inspiration, what needs to be done to write the register.&lt;/P&gt;
&lt;P&gt;Regards&lt;/P&gt;</description>
      <pubDate>Fri, 01 Dec 2023 16:15:54 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/LVDS-PHY-CTRL-sharing/m-p/1767402#M216714</guid>
      <dc:creator>Bio_TICFSL</dc:creator>
      <dc:date>2023-12-01T16:15:54Z</dc:date>
    </item>
    <item>
      <title>Re: LVDS_PHY_CTRL sharing</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/LVDS-PHY-CTRL-sharing/m-p/1768053#M216777</link>
      <description>&lt;P&gt;Thanks for the reply, but we need to share it as the subject is&lt;/P&gt;</description>
      <pubDate>Mon, 04 Dec 2023 08:00:36 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/LVDS-PHY-CTRL-sharing/m-p/1768053#M216777</guid>
      <dc:creator>krassimirestoya</dc:creator>
      <dc:date>2023-12-04T08:00:36Z</dc:date>
    </item>
  </channel>
</rss>

