<?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: VPU memory reservation and debugging with Device Trees</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/VPU-memory-reservation-and-debugging-with-Device-Trees/m-p/1007296#M149265</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thank you for your answer Joan.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm apparantly unauthorized to view your first link.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The second seems interesting, but I couldn't see any mention of device trees. The post is old, so maybe this was before device trees were introduced. They refer to patches that should probably be implemented with device trees today. Not sure how though. They also use an outdated VPU wrapper for gstreamer. The new one is called gstreamer-imx:&amp;nbsp;&lt;A class="link-titled" href="https://github.com/Freescale/gstreamer-imx" title="https://github.com/Freescale/gstreamer-imx"&gt;GitHub - Freescale/gstreamer-imx: GStreamer 1.0 plugins for i.MX platforms&lt;/A&gt;&amp;nbsp;.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 11 Feb 2020 10:14:26 GMT</pubDate>
    <dc:creator>erlend_eriksen</dc:creator>
    <dc:date>2020-02-11T10:14:26Z</dc:date>
    <item>
      <title>VPU memory reservation and debugging with Device Trees</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/VPU-memory-reservation-and-debugging-with-Device-Trees/m-p/1007294#M149263</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Are there any examples on how to configure how much memory is available / reserved for VPU and GPU, and what address range they use, using device tree files? I know that you can use the&amp;nbsp;&lt;SPAN style="color: #51626f; background-color: #ffffff;"&gt;CONFIG_CMA_SIZE_MBYTES option in the kernel configuration, but as I understand it, the device tree would give finer control over contiguous memory allocation.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #51626f; background-color: #ffffff;"&gt;The root of the problem is that I want to be able to debug the memory allocation better. I know that I can do real time 30 FPS FHD transcoding on my i.MX6, but memory hungry processes make the VPU lag behind. I want not only to reserve memory for the VPU, but also to debug whether it actually gets access to all the memory I reserve, or if it gets used by other processes on the arm cores.&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 10 Feb 2020 11:00:52 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/VPU-memory-reservation-and-debugging-with-Device-Trees/m-p/1007294#M149263</guid>
      <dc:creator>erlend_eriksen</dc:creator>
      <dc:date>2020-02-10T11:00:52Z</dc:date>
    </item>
    <item>
      <title>Re: VPU memory reservation and debugging with Device Trees</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/VPU-memory-reservation-and-debugging-with-Device-Trees/m-p/1007295#M149264</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;pls refer to the topic as below:&lt;/P&gt;&lt;P&gt;&lt;A href="https://community.nxp.com/thread/328039"&gt;MX6 GPU memory usage&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A _jive_internal="true" class="link-titled" href="https://community.nxp.com/thread/307038?commentID=341607#comment-341607" title="https://community.nxp.com/thread/307038?commentID=341607#comment-341607"&gt;https://community.nxp.com/thread/307038?commentID=341607#comment-341607&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 11 Feb 2020 05:54:00 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/VPU-memory-reservation-and-debugging-with-Device-Trees/m-p/1007295#M149264</guid>
      <dc:creator>joanxie</dc:creator>
      <dc:date>2020-02-11T05:54:00Z</dc:date>
    </item>
    <item>
      <title>Re: VPU memory reservation and debugging with Device Trees</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/VPU-memory-reservation-and-debugging-with-Device-Trees/m-p/1007296#M149265</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thank you for your answer Joan.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm apparantly unauthorized to view your first link.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The second seems interesting, but I couldn't see any mention of device trees. The post is old, so maybe this was before device trees were introduced. They refer to patches that should probably be implemented with device trees today. Not sure how though. They also use an outdated VPU wrapper for gstreamer. The new one is called gstreamer-imx:&amp;nbsp;&lt;A class="link-titled" href="https://github.com/Freescale/gstreamer-imx" title="https://github.com/Freescale/gstreamer-imx"&gt;GitHub - Freescale/gstreamer-imx: GStreamer 1.0 plugins for i.MX platforms&lt;/A&gt;&amp;nbsp;.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 11 Feb 2020 10:14:26 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/VPU-memory-reservation-and-debugging-with-Device-Trees/m-p/1007296#M149265</guid>
      <dc:creator>erlend_eriksen</dc:creator>
      <dc:date>2020-02-11T10:14:26Z</dc:date>
    </item>
    <item>
      <title>Re: VPU memory reservation and debugging with Device Trees</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/VPU-memory-reservation-and-debugging-with-Device-Trees/m-p/1007297#M149266</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;if you need to know how to set this memory in the kernel, you can refer to the board dtsi file, for example, imx6q board, you can find the &lt;A href="https://source.codeaurora.org/external/imx/linux-imx/tree/arch/arm/boot/dts/imx6q.dtsi?h=imx_4.14.98_2.0.0_ga" rel="nofollow noopener noreferrer" target="_blank"&gt;imx6q.dtsi:&lt;/A&gt;&lt;/P&gt;&lt;PRE&gt;&lt;PRE&gt;&lt;PRE&gt;reserved-memory {   
#address-cells = &amp;lt;1&amp;gt;;   
#size-cells = &amp;lt;1&amp;gt;;   
ranges;    
/* global autoconfigured region for contiguous allocations */   
linux,cma {    
compatible = "shared-dma-pool";    
reusable;    
size = &amp;lt;0x14000000&amp;gt;;    
linux,cma-default;   
};  
};&lt;/PRE&gt;&lt;/PRE&gt;
I got information about gpu settings:
”some continuous memory reserved for GPU, and the size can be changed rhrouhg u-boot arguments with
 "glacore.contiguousize=xxx" This memory can be accesses fast and cannot support cacheable attribute.“
for more detailed information about gpu memory, pls refer to the chapter Chapter 14 GPU Memory Introduction
of i.MX Graphics User’s Guide&lt;/PRE&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 14 Feb 2020 08:16:49 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/VPU-memory-reservation-and-debugging-with-Device-Trees/m-p/1007297#M149266</guid>
      <dc:creator>joanxie</dc:creator>
      <dc:date>2020-02-14T08:16:49Z</dc:date>
    </item>
  </channel>
</rss>

