public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Lane Brooks <lane@brooks.nu>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: linux-media@vger.kernel.org
Subject: Re: Translation faults with OMAP ISP
Date: Wed, 17 Nov 2010 16:17:21 -0700	[thread overview]
Message-ID: <4CE46281.2010308@brooks.nu> (raw)
In-Reply-To: <201011180009.31053.laurent.pinchart@ideasonboard.com>

On 11/17/2010 04:09 PM, Laurent Pinchart wrote:
> Hi Lane,
>
> On Wednesday 17 November 2010 00:46:27 Lane Brooks wrote:
>> Laurent,
>>
>> I am getting iommu translation errors when I try to use the CCDC output
>> after using the Resizer output.
>>
>> If I use the CCDC output to stream some video, then close it down,
>> switch to the Resizer output and open it up and try to stream, I get the
>> following errors spewing out:
>>
>> omap-iommu omap-iommu.0: omap2_iommu_fault_isr: da:00d0ef00 translation
>> fault
>> omap-iommu omap-iommu.0: iommu_fault_handler: da:00d0ef00 pgd:ce664034
>> *pgd:00000000
>>
>> and the select times out.
>>
>>   From a fresh boot, I can stream just fine from the Resizer and then
>> switch to the CCDC output just fine. It is only when I go from the CCDC
>> to the Resizer that I get this problem. Furthermore, when it gets into
>> this state, then anything dev node I try to use has the translation
>> errors and the only way to recover is to reboot.
>>
>> Any ideas on the problem?
> Ouch. First of all, could you please make sure you run the latest code ? Many
> bugs have been fixed in the last few months

I had a pretty good idea that this would be your response, but I was 
hoping otherwise as merging has become more and more difficult to keep 
up with. Anyway, until I have a chance to merge in everything, I just 
found a work around for our usage needs, and that is to always use the 
resizer output and just change the resizer format between full 
resolution and preview resolution. This has turned out to be much more 
stable than switching between the CCDC and RESIZER dev nodes.

Thanks again for your feedback.

Lane

  reply	other threads:[~2010-11-17 23:17 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4CE16AA2.3000208@brooks.nu>
     [not found] ` <4CE18EE4.7080203@brooks.nu>
     [not found]   ` <201011160001.10737.laurent.pinchart@ideasonboard.com>
2010-11-16 23:46     ` Translation faults with OMAP ISP Lane Brooks
2010-11-17 23:09       ` Laurent Pinchart
2010-11-17 23:17         ` Lane Brooks [this message]
2010-11-19 13:29           ` David Cohen
2010-11-19 14:08             ` Lane Brooks
2010-11-19 14:13               ` Laurent Pinchart
2010-11-19 14:16                 ` Lane Brooks
2010-11-19 15:06                   ` David Cohen
2010-11-19 15:07                     ` Laurent Pinchart
2010-11-19 15:12                       ` David Cohen
2010-11-19 16:07                         ` [omap3isp] Prefered patch base for latest code? (was: "RE: Translation faults with OMAP ISP") Aguirre, Sergio
2010-11-19 16:16                           ` Laurent Pinchart
2010-11-19 16:23                             ` Aguirre, Sergio
2010-11-19 16:32                               ` Laurent Pinchart
2010-11-19 16:37                                 ` Aguirre, Sergio

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=4CE46281.2010308@brooks.nu \
    --to=lane@brooks.nu \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-media@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox