All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>
To: Krishan Nilanga <krishan@tengriaero.com>
Cc: Lucas Stach <l.stach@pengutronix.de>,
	Anuradha Ranasinghe <anuradha@tengriaero.com>,
	linux-media <linux-media@vger.kernel.org>,
	Lakshitha Dayasena <lakshitha@tengriaero.com>,
	linux-pci@vger.kernel.org, Richard.Zhu@freescale.com
Subject: Re: TW686x Linux Main Line Driver Issue
Date: Tue, 25 Apr 2017 11:15:06 -0300	[thread overview]
Message-ID: <CAAEAJfBEqFYtKLHuNBBbc8+RteM8rhRNs3PFvAnGsVWRpxEGNw@mail.gmail.com> (raw)
In-Reply-To: <CAKXQXwKeA6YCaepmjJJBf+Nc3bOO9aEnGmnHfnb2aDX3f6YXzw@mail.gmail.com>

Hi Krishan,

On 25 April 2017 at 03:46, Krishan Nilanga <krishan@tengriaero.com> wrote:
> Hi All,
>
> gst-launch-1.0 --gst-debug=3 v4l2src device=/dev/video0 !
> video/x-raw,width=640,height=480,pixelformat=UYVY ! imxeglvivsink
>
> I have tried to run the above gstreamer pipeline and I'm getting
>
> [   97.392807] tw686x 0000:01:00.0: DMA timeout. Resetting DMA for all
> channels
> [   97.392827] tw686x 0000:01:00.0: reset: stopping DMA
>
> for most IRQ calls of tw686x driver.
>
> for some other IRQ calls I'm getting
>
> [   99.592901] tw686x 0000:01:00.0: video0: unexpected p-b buffer!
> [   99.592924] tw686x 0000:01:00.0: reset: stopping DMA
>
> in dmesg.
>
> I hope above details will help to understand the problem.
>

This does not provide much info. It merely says there is some hardware
problem or the signal is being problematic. FWIW, when we get those
messages on our platform it's always correlated to a bad cable
or poor signal.

What is your dma-mode configuration?
-- 
Ezequiel García, VanguardiaSur
www.vanguardiasur.com.ar

WARNING: multiple messages have this Message-ID (diff)
From: Ezequiel Garcia <ezequiel@vanguardiasur.com.ar>
To: Krishan Nilanga <krishan@tengriaero.com>
Cc: Lucas Stach <l.stach@pengutronix.de>,
	Anuradha Ranasinghe <anuradha@tengriaero.com>,
	linux-media <linux-media@vger.kernel.org>,
	Lakshitha Dayasena <lakshitha@tengriaero.com>,
	linux-pci@vger.kernel.org, Richard.Zhu@freescale.com
Subject: Re: TW686x Linux Main Line Driver Issue
Date: Tue, 25 Apr 2017 11:15:06 -0300	[thread overview]
Message-ID: <CAAEAJfBEqFYtKLHuNBBbc8+RteM8rhRNs3PFvAnGsVWRpxEGNw@mail.gmail.com> (raw)
In-Reply-To: <CAKXQXwKeA6YCaepmjJJBf+Nc3bOO9aEnGmnHfnb2aDX3f6YXzw@mail.gmail.com>

Hi Krishan,

On 25 April 2017 at 03:46, Krishan Nilanga <krishan@tengriaero.com> wrote:
> Hi All,
>
> gst-launch-1.0 --gst-debug=3D3 v4l2src device=3D/dev/video0 !
> video/x-raw,width=3D640,height=3D480,pixelformat=3DUYVY ! imxeglvivsink
>
> I have tried to run the above gstreamer pipeline and I'm getting
>
> [   97.392807] tw686x 0000:01:00.0: DMA timeout. Resetting DMA for all
> channels
> [   97.392827] tw686x 0000:01:00.0: reset: stopping DMA
>
> for most IRQ calls of tw686x driver.
>
> for some other IRQ calls I'm getting
>
> [   99.592901] tw686x 0000:01:00.0: video0: unexpected p-b buffer!
> [   99.592924] tw686x 0000:01:00.0: reset: stopping DMA
>
> in dmesg.
>
> I hope above details will help to understand the problem.
>

This does not provide much info. It merely says there is some hardware
problem or the signal is being problematic. FWIW, when we get those
messages on our platform it's always correlated to a bad cable
or poor signal.

What is your dma-mode configuration?
--=20
Ezequiel Garc=C3=ADa, VanguardiaSur
www.vanguardiasur.com.ar

  parent reply	other threads:[~2017-04-25 14:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAOxqCCT6MOCLG+HHsuOU0zoq1zxRRJNFn0DYz9tOj-ez7+BNRA@mail.gmail.com>
2017-04-20 14:12 ` TW686x Linux Main Line Driver Issue Ezequiel Garcia
2017-04-20 14:12   ` Ezequiel Garcia
2017-04-24 10:38   ` Lucas Stach
     [not found]     ` <CAKXQXwLuG1A37NTPrE0abPWhMDGd=10Ud+xNa-4+k+8qMhD8tA@mail.gmail.com>
     [not found]       ` <CAKXQXwKeA6YCaepmjJJBf+Nc3bOO9aEnGmnHfnb2aDX3f6YXzw@mail.gmail.com>
2017-04-25 14:15         ` Ezequiel Garcia [this message]
2017-04-25 14:15           ` Ezequiel Garcia

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAAEAJfBEqFYtKLHuNBBbc8+RteM8rhRNs3PFvAnGsVWRpxEGNw@mail.gmail.com \
    --to=ezequiel@vanguardiasur.com.ar \
    --cc=Richard.Zhu@freescale.com \
    --cc=anuradha@tengriaero.com \
    --cc=krishan@tengriaero.com \
    --cc=l.stach@pengutronix.de \
    --cc=lakshitha@tengriaero.com \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.