<?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: i.MX93 FlexSPI Linux driver optimisation</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/i-MX93-FlexSPI-Linux-driver-optimisation/m-p/1891695#M225305</link>
    <description>&lt;P&gt;Hello,&amp;nbsp;&lt;/P&gt;
&lt;P&gt;You can look in Reference Manual:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;36.4.15.4 Input timing for sampling with SCK output looped back from SCK pad&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;This section describes the input timing when sampling with the SCK output looped back from the SCK pad (MCR0[RXCLKSRC] = 2). The input timing is similar to sampling with a dummy read strobe. SCK output toggles for all types of instructions, but internal dummy strobe only toggles for read and learn instructions. In this case, FlexSPI receives more data bits when sampling with SCK output. FlexSPI automatically ignores the redundant data bits sampled.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The only restriction is in&amp;nbsp;SCKFREERUNEN&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Alejandro_Salas_0-1718921985110.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/285127iAE5F203CFD27C572/image-size/medium?v=v2&amp;amp;px=400" role="button" title="Alejandro_Salas_0-1718921985110.png" alt="Alejandro_Salas_0-1718921985110.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;When SCLK Free-running is enabled, the data sampling loopback clock from SCLK pad is not supported.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;There is not information available for&amp;nbsp;&lt;SPAN&gt;spi-mem dirmap implementation.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;I hope this can helps to you.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;BR,&lt;/P&gt;
&lt;P&gt;--... ...--&lt;/P&gt;
&lt;P&gt;Salas.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 20 Jun 2024 22:24:32 GMT</pubDate>
    <dc:creator>Manuel_Salas</dc:creator>
    <dc:date>2024-06-20T22:24:32Z</dc:date>
    <item>
      <title>i.MX93 FlexSPI Linux driver optimisation</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/i-MX93-FlexSPI-Linux-driver-optimisation/m-p/1889441#M225137</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;in datasheet MCR0[RXCLKSR] = 0x1 is documented to deal with clocks up to 166 MHz. In reference manual additionally&amp;nbsp;MCR0[RXCLKSR] = 0x2 is documented but no clock limit given. On a system with no STROBE pin available we try to enhance READ/WRITE performance.&lt;/P&gt;&lt;P&gt;Please clarify documentation for&amp;nbsp;MCR0[RXCLKSR] = 0x2 regarding usable SPI SCLK frequencies.&lt;/P&gt;&lt;P&gt;Are there further restrictions in using this mode?&lt;/P&gt;&lt;P&gt;Additionally: are there plans to implement spi-mem dirmap for flexspi driver?&lt;/P&gt;&lt;P&gt;&lt;a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/175204"&gt;@danny_john&lt;/a&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 18 Jun 2024 11:33:54 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/i-MX93-FlexSPI-Linux-driver-optimisation/m-p/1889441#M225137</guid>
      <dc:creator>Niebel-TQ</dc:creator>
      <dc:date>2024-06-18T11:33:54Z</dc:date>
    </item>
    <item>
      <title>Re: i.MX93 FlexSPI Linux driver optimisation</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/i-MX93-FlexSPI-Linux-driver-optimisation/m-p/1891695#M225305</link>
      <description>&lt;P&gt;Hello,&amp;nbsp;&lt;/P&gt;
&lt;P&gt;You can look in Reference Manual:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;36.4.15.4 Input timing for sampling with SCK output looped back from SCK pad&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;This section describes the input timing when sampling with the SCK output looped back from the SCK pad (MCR0[RXCLKSRC] = 2). The input timing is similar to sampling with a dummy read strobe. SCK output toggles for all types of instructions, but internal dummy strobe only toggles for read and learn instructions. In this case, FlexSPI receives more data bits when sampling with SCK output. FlexSPI automatically ignores the redundant data bits sampled.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The only restriction is in&amp;nbsp;SCKFREERUNEN&lt;/P&gt;
&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Alejandro_Salas_0-1718921985110.png" style="width: 400px;"&gt;&lt;img src="https://community.nxp.com/t5/image/serverpage/image-id/285127iAE5F203CFD27C572/image-size/medium?v=v2&amp;amp;px=400" role="button" title="Alejandro_Salas_0-1718921985110.png" alt="Alejandro_Salas_0-1718921985110.png" /&gt;&lt;/span&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;When SCLK Free-running is enabled, the data sampling loopback clock from SCLK pad is not supported.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;There is not information available for&amp;nbsp;&lt;SPAN&gt;spi-mem dirmap implementation.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;I hope this can helps to you.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;BR,&lt;/P&gt;
&lt;P&gt;--... ...--&lt;/P&gt;
&lt;P&gt;Salas.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 20 Jun 2024 22:24:32 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/i-MX93-FlexSPI-Linux-driver-optimisation/m-p/1891695#M225305</guid>
      <dc:creator>Manuel_Salas</dc:creator>
      <dc:date>2024-06-20T22:24:32Z</dc:date>
    </item>
  </channel>
</rss>

