<?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>Layerscape中的主题 How to keep cache coherency between DPAA and Ctx-A53 on LS1043A</title>
    <link>https://community.nxp.com/t5/Layerscape/How-to-keep-cache-coherency-between-DPAA-and-Ctx-A53-on-LS1043A/m-p/671814#M2527</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am trying to use DPAA to transmit ethernet packet on LS1043ARDB board.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I use cache-enabled memory to encapsulate the ethernet packet data. When doing the qman portal enqueue operation, I have to flush the cache of this memory in order that DPAA can get proper data.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My question is: to avoid the load introduced by cache flush, is there an&amp;nbsp;implement of the cache coherency between DPAA and ARM core in hardware?&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 02 Jun 2017 05:03:11 GMT</pubDate>
    <dc:creator>uncoldice</dc:creator>
    <dc:date>2017-06-02T05:03:11Z</dc:date>
    <item>
      <title>How to keep cache coherency between DPAA and Ctx-A53 on LS1043A</title>
      <link>https://community.nxp.com/t5/Layerscape/How-to-keep-cache-coherency-between-DPAA-and-Ctx-A53-on-LS1043A/m-p/671814#M2527</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am trying to use DPAA to transmit ethernet packet on LS1043ARDB board.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I use cache-enabled memory to encapsulate the ethernet packet data. When doing the qman portal enqueue operation, I have to flush the cache of this memory in order that DPAA can get proper data.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My question is: to avoid the load introduced by cache flush, is there an&amp;nbsp;implement of the cache coherency between DPAA and ARM core in hardware?&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 02 Jun 2017 05:03:11 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Layerscape/How-to-keep-cache-coherency-between-DPAA-and-Ctx-A53-on-LS1043A/m-p/671814#M2527</guid>
      <dc:creator>uncoldice</dc:creator>
      <dc:date>2017-06-02T05:03:11Z</dc:date>
    </item>
    <item>
      <title>Re: How to keep cache coherency between DPAA and Ctx-A53 on LS1043A</title>
      <link>https://community.nxp.com/t5/Layerscape/How-to-keep-cache-coherency-between-DPAA-and-Ctx-A53-on-LS1043A/m-p/671815#M2528</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;FMAN DMA always issues snoopable transactions for buffers. If you are working with Linux SDK, make sure you did&lt;/P&gt;&lt;P&gt;not alter the kernel configuration to disable CCI-400 and SMMU support. If you are working in a non-Linux environment,&lt;/P&gt;&lt;P&gt;check Linux kernel source code, files arm-cci.c and arch/arm64/mm/dma-mapping.c (links below) for the corresponding attributes setting procedures:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-external-small" href="https://community.nxp.com/external-link.jspa?url=http%3A%2F%2Fgit.freescale.com%2Fgit%2Fcgit.cgi%2Fppc%2Fsdk%2Flinux.git%2Ftree%2Fdrivers%2Fbus%2Farm-cci.c%3Fid%3Dfsl-sdk-v2.0-1703" rel="nofollow" target="_blank"&gt;http://git.freescale.com/git/cgit.cgi/ppc/sdk/linux.git/tree/drivers/bus/arm-cci.c?id=fsl-sdk-v2.0-1703&lt;/A&gt;&lt;BR /&gt;&lt;A class="jive-link-external-small" href="https://community.nxp.com/external-link.jspa?url=http%3A%2F%2Fgit.freescale.com%2Fgit%2Fcgit.cgi%2Fppc%2Fsdk%2Flinux.git%2Ftree%2Farch%2Farm64%2Fmm%2Fdma-mapping.c%3Fid%3Dfsl-sdk-v2.0-1703" rel="nofollow" target="_blank"&gt;http://git.freescale.com/git/cgit.cgi/ppc/sdk/linux.git/tree/arch/arm64/mm/dma-mapping.c?id=fsl-sdk-v2.0-1703&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Have a great day,&lt;BR /&gt;Platon&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-----------------------------------------------------------------------------------------------------------------------&lt;BR /&gt;Note: If this post answers your question, please click the Correct Answer button. Thank you!&lt;BR /&gt;-----------------------------------------------------------------------------------------------------------------------&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 07 Jun 2017 10:09:16 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Layerscape/How-to-keep-cache-coherency-between-DPAA-and-Ctx-A53-on-LS1043A/m-p/671815#M2528</guid>
      <dc:creator>bpe</dc:creator>
      <dc:date>2017-06-07T10:09:16Z</dc:date>
    </item>
    <item>
      <title>Re: How to keep cache coherency between DPAA and Ctx-A53 on LS1043A</title>
      <link>https://community.nxp.com/t5/Layerscape/How-to-keep-cache-coherency-between-DPAA-and-Ctx-A53-on-LS1043A/m-p/671816#M2529</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have a new question about the CCI-400.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In LS1043ARM.pdf chapter 9.1.3, for the BMAN/QMAN/FMAN snoop transaction configuration, it says "Refer LS1043ADPAARM for more details". However, I cannot find any related information from LS1043ADPAARM Rev.0 04/2016.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is there any updated DPAARM that contains this configuration? If yes, please share the way to get it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 12 Jun 2017 07:04:45 GMT</pubDate>
      <guid>https://community.nxp.com/t5/Layerscape/How-to-keep-cache-coherency-between-DPAA-and-Ctx-A53-on-LS1043A/m-p/671816#M2529</guid>
      <dc:creator>uncoldice</dc:creator>
      <dc:date>2017-06-12T07:04:45Z</dc:date>
    </item>
  </channel>
</rss>

