From: Lane Brooks <lane@brooks.nu>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
linux-media@vger.kernel.org
Subject: Translation faults with OMAP ISP
Date: Tue, 16 Nov 2010 16:46:27 -0700 [thread overview]
Message-ID: <4CE317D3.2020504@brooks.nu> (raw)
In-Reply-To: <201011160001.10737.laurent.pinchart@ideasonboard.com>
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?
Thanks,
Lane
next parent reply other threads:[~2010-11-16 23:46 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 ` Lane Brooks [this message]
2010-11-17 23:09 ` Translation faults with OMAP ISP Laurent Pinchart
2010-11-17 23:17 ` Lane Brooks
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=4CE317D3.2020504@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