From: Lane Brooks <lane@brooks.nu>
To: David Cohen <david.cohen@nokia.com>
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>
Subject: Re: Translation faults with OMAP ISP
Date: Fri, 19 Nov 2010 07:08:38 -0700 [thread overview]
Message-ID: <4CE684E6.6010403@brooks.nu> (raw)
In-Reply-To: <20101119132927.GD13490@esdhcp04381.research.nokia.com>
On 11/19/2010 06:29 AM, David Cohen wrote:
> On Thu, Nov 18, 2010 at 12:17:21AM +0100, ext Lane Brooks wrote:
>> 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?
> I'm not sure if it's your case, but OMAP3 ISP driver does not support
> pipeline with multiples outputs yet. We have to return error from the
> driver in this case. If you configured CCDC to write to memory and then
> to write to preview/resizer afterwards without deactivating the link to
> write to memory, you may face a similar problem you described.
>
> Can you please try a patch I've sent to you (CC'ing linux-media) with subject:
> "[omap3isp][PATCH] omap3isp: does not allow pipeline with multiple video
> outputs yet"?
>
> Regards,
>
> David
David,
I am not trying to use multiple outputs simultaneously. I get the
translation error with the following sequence:
- Open resizer output and setup media links.
- Stream some images.
- Close resizer.
- Reset all media links.
- Open CCDC and setup media links.
- Try to stream some images but get translation faults.
Is your patch going to help with this problem?
Lane
next prev parent reply other threads:[~2010-11-19 14:09 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
2010-11-19 13:29 ` David Cohen
2010-11-19 14:08 ` Lane Brooks [this message]
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=4CE684E6.6010403@brooks.nu \
--to=lane@brooks.nu \
--cc=david.cohen@nokia.com \
--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