<?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中的主题 video capure issue</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/video-capure-issue/m-p/408142#M60859</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN lang="EN-US" style="color: #1f497d;"&gt;Hi, &lt;/SPAN&gt;&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&lt;SPAN lang="EN-US" style="color: #1f497d;"&gt;&lt;/SPAN&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN lang="EN-US" style="color: #1f497d;"&gt;We have i.MX6S V4L2 video capture issue, we did further investigation and we report to you our new findings below,&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P align="left" style="text-align: left;"&gt;&lt;SPAN lang="EN-US" style="color: #1f497d;"&gt;We made a small test program which does V4L2 output to video17 device. The some problem happens even without involving the capture path. The test program calls VIDIOC_S_CROP&amp;nbsp; to set 1280*720 as display output range, and it calls VIDIOC_S_FMT to set 720*480 as input range. When the ioctl VIDIOC_S_FMT&amp;nbsp; is executed, we found out that the input is only valid for the range of 688*480, and the right most 32 pixels of each line are lost. &lt;/SPAN&gt;&lt;/P&gt;&lt;P align="left" style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P align="left" style="text-align: left;"&gt;&lt;SPAN lang="EN-US" style="color: #1f497d;"&gt;We did some kernel debugging and when VIDIOC_S_FMT&amp;nbsp; is executed,&lt;/SPAN&gt;&lt;/P&gt;&lt;P align="left" style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P align="left" style="text-align: left;"&gt;&lt;SPAN lang="EN-US" style="color: #1f497d;"&gt;mxc_vidioc_s_fmt_vid_out -&amp;gt;mxc_vout_try_format -&amp;gt;mxc_vout_try_task -&amp;gt;ipu_try_task -&amp;gt;ipu_check_task -&amp;gt;check_task -&amp;gt;update_split_setting -&amp;gt;ipu_calc_stripes_sizes &lt;/SPAN&gt;&lt;/P&gt;&lt;P align="left" style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P align="left" style="text-align: left;"&gt;&lt;SPAN lang="EN-US" style="color: #1f497d;"&gt;We noticed that return value of ipu_check_task() indicated 4 times of &lt;/SPAN&gt;&lt;SPAN lang="EN-US" style="color: red;"&gt;IPU_CHECK_ERR_SPLIT_INPUTW_OVER&lt;/SPAN&gt;&lt;SPAN lang="EN-US" style="color: #1f497d;"&gt; , and this causes 4*8=32 to be lost, that’s why the input image cannot be fully displayed. &lt;/SPAN&gt;&lt;/P&gt;&lt;P align="left" style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P align="left" style="text-align: left;"&gt;&lt;SPAN lang="EN-US" style="color: #1f497d;"&gt;Would you please give us advice such as, what causes this problem, and how to avoid it? (We have to use input image size of 720x480 because that is the only valid imput range from MHL input source (processed by TW8836), and we have to use output screen size of 1280x720&amp;nbsp; because that is the hardware TFT resolution).&lt;/SPAN&gt;&lt;/P&gt;&lt;P align="left" style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P align="left" style="text-align: left;"&gt;Best Regards.&lt;/P&gt;&lt;P align="left" style="text-align: left;"&gt;Kanou&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Original Attachment has been moved to: &lt;A _jive_internal="true" href="https://community.nxp.com/docs/DOC-336381"&gt;tvinout_test.zip&lt;/A&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 31 Aug 2015 02:57:50 GMT</pubDate>
    <dc:creator>kanoumamoru</dc:creator>
    <dc:date>2015-08-31T02:57:50Z</dc:date>
    <item>
      <title>video capure issue</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/video-capure-issue/m-p/408142#M60859</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN lang="EN-US" style="color: #1f497d;"&gt;Hi, &lt;/SPAN&gt;&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&lt;SPAN lang="EN-US" style="color: #1f497d;"&gt;&lt;/SPAN&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN lang="EN-US" style="color: #1f497d;"&gt;We have i.MX6S V4L2 video capture issue, we did further investigation and we report to you our new findings below,&lt;/SPAN&gt;&lt;/P&gt;&lt;P style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P align="left" style="text-align: left;"&gt;&lt;SPAN lang="EN-US" style="color: #1f497d;"&gt;We made a small test program which does V4L2 output to video17 device. The some problem happens even without involving the capture path. The test program calls VIDIOC_S_CROP&amp;nbsp; to set 1280*720 as display output range, and it calls VIDIOC_S_FMT to set 720*480 as input range. When the ioctl VIDIOC_S_FMT&amp;nbsp; is executed, we found out that the input is only valid for the range of 688*480, and the right most 32 pixels of each line are lost. &lt;/SPAN&gt;&lt;/P&gt;&lt;P align="left" style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P align="left" style="text-align: left;"&gt;&lt;SPAN lang="EN-US" style="color: #1f497d;"&gt;We did some kernel debugging and when VIDIOC_S_FMT&amp;nbsp; is executed,&lt;/SPAN&gt;&lt;/P&gt;&lt;P align="left" style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P align="left" style="text-align: left;"&gt;&lt;SPAN lang="EN-US" style="color: #1f497d;"&gt;mxc_vidioc_s_fmt_vid_out -&amp;gt;mxc_vout_try_format -&amp;gt;mxc_vout_try_task -&amp;gt;ipu_try_task -&amp;gt;ipu_check_task -&amp;gt;check_task -&amp;gt;update_split_setting -&amp;gt;ipu_calc_stripes_sizes &lt;/SPAN&gt;&lt;/P&gt;&lt;P align="left" style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P align="left" style="text-align: left;"&gt;&lt;SPAN lang="EN-US" style="color: #1f497d;"&gt;We noticed that return value of ipu_check_task() indicated 4 times of &lt;/SPAN&gt;&lt;SPAN lang="EN-US" style="color: red;"&gt;IPU_CHECK_ERR_SPLIT_INPUTW_OVER&lt;/SPAN&gt;&lt;SPAN lang="EN-US" style="color: #1f497d;"&gt; , and this causes 4*8=32 to be lost, that’s why the input image cannot be fully displayed. &lt;/SPAN&gt;&lt;/P&gt;&lt;P align="left" style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P align="left" style="text-align: left;"&gt;&lt;SPAN lang="EN-US" style="color: #1f497d;"&gt;Would you please give us advice such as, what causes this problem, and how to avoid it? (We have to use input image size of 720x480 because that is the only valid imput range from MHL input source (processed by TW8836), and we have to use output screen size of 1280x720&amp;nbsp; because that is the hardware TFT resolution).&lt;/SPAN&gt;&lt;/P&gt;&lt;P align="left" style="min-height: 8pt; padding: 0px;"&gt;&amp;nbsp;&lt;/P&gt;&lt;P align="left" style="text-align: left;"&gt;Best Regards.&lt;/P&gt;&lt;P align="left" style="text-align: left;"&gt;Kanou&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Original Attachment has been moved to: &lt;A _jive_internal="true" href="https://community.nxp.com/docs/DOC-336381"&gt;tvinout_test.zip&lt;/A&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 31 Aug 2015 02:57:50 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/video-capure-issue/m-p/408142#M60859</guid>
      <dc:creator>kanoumamoru</dc:creator>
      <dc:date>2015-08-31T02:57:50Z</dc:date>
    </item>
    <item>
      <title>Re: video capure issue</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/video-capure-issue/m-p/408143#M60860</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;if you use IC module, the ouput limit is 1024*1024, so you should split the input video then scale to the demands output.&lt;/P&gt;&lt;P&gt;I send the source sample code to you for reference, hope helpful for you.&lt;/P&gt;&lt;P&gt;&lt;A href="https://github.com/rogeriorps/ipu-examples" title="https://github.com/rogeriorps/ipu-examples"&gt;rogeriorps/ipu-examples · GitHub&lt;/A&gt; &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 02 Sep 2015 03:56:59 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/video-capure-issue/m-p/408143#M60860</guid>
      <dc:creator>joanxie</dc:creator>
      <dc:date>2015-09-02T03:56:59Z</dc:date>
    </item>
    <item>
      <title>Re: video capure issue</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/video-capure-issue/m-p/408144#M60861</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi, Guanqiong,&lt;/P&gt;&lt;P&gt;I&amp;nbsp; appreciate for your advice.&lt;/P&gt;&lt;P&gt;I'll try it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;kanou&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 04 Sep 2015 03:28:26 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/video-capure-issue/m-p/408144#M60861</guid>
      <dc:creator>kanoumamoru</dc:creator>
      <dc:date>2015-09-04T03:28:26Z</dc:date>
    </item>
  </channel>
</rss>

