From: Tomi Valkeinen <tomi.valkeinen@nokia.com>
To: "ext Aguirre, Sergio" <saaguirre@ti.com>
Cc: "Syrjala Ville (Nokia-D/Helsinki)" <ville.syrjala@nokia.com>,
"linux-fbdev@vger.kernel.org" <linux-fbdev@vger.kernel.org>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: RE: [PATCH 4/4] DSS2: clear spurious SYNC_LOST_DIGIT interrupts
Date: Fri, 05 Mar 2010 15:25:13 +0000 [thread overview]
Message-ID: <1267802713.25148.146.camel@tubuntu.research.nokia.com> (raw)
In-Reply-To: <A24693684029E5489D1D202277BE894453CC5CA0@dlee02.ent.ti.com>
On Fri, 2010-03-05 at 16:19 +0100, ext Aguirre, Sergio wrote:
> Hi Ville,
>
> > -----Original Message-----
> > From: linux-omap-owner@vger.kernel.org [mailto:linux-omap-
> > owner@vger.kernel.org] On Behalf Of ville.syrjala@nokia.com
> > Sent: Friday, March 05, 2010 7:26 AM
> > To: Tomi Valkeinen
> > Cc: linux-fbdev@vger.kernel.org; linux-omap@vger.kernel.org; Ville Syrj채l채
> > Subject: [PATCH 4/4] DSS2: clear spurious SYNC_LOST_DIGIT interrupts
> >
> > From: Ville Syrj채l채 <ville.syrjala@nokia.com>
> >
> > When DSS transitions from off mode to on VENC may generate a spurious
> > SYNC_LOST_DIGIT error. Just ack it when restoring the context. Also
> > restore IRQENABLE last to avoid triggering interrupts before the
> > context is fully restored.
>
> (Tomi or anyone can correct me if I'm wrong)
>
> AFAIK, The solution for spurious interrupts is to flush posted bus writes during interrupt handling, which can be achieved by reading the same register just after you have written it.
>
> Tomi, what do you think?
That's a different spurious interrupt =).
In this case the IRQ mechanism from CPU side is working fine, but VENC
is just spamming the error interrupts, for unknown reason.
Tomi
--
To unsubscribe from this list: send the line "unsubscribe linux-fbdev" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-03-05 15:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-05 13:26 [PATCH v3 1/4] DSS2: OMAPFB: Add support for switching memory regions ville.syrjala
2010-03-05 13:26 ` [PATCH 2/4] DSS2: Check if display supports update mode changes ville.syrjala
2010-03-05 13:26 ` [PATCH 3/4] DSS2: Make wait_for_go() succeed for disabled displays ville.syrjala
2010-03-05 13:26 ` [PATCH 4/4] DSS2: clear spurious SYNC_LOST_DIGIT interrupts ville.syrjala
2010-03-05 15:19 ` Aguirre, Sergio
2010-03-05 15:25 ` Tomi Valkeinen [this message]
2010-03-05 15:28 ` Aguirre, Sergio
2010-03-17 13:50 ` [PATCH v3 1/4] DSS2: OMAPFB: Add support for switching memory Tomi Valkeinen
2010-03-17 15:51 ` Ville Syrjälä
2010-03-17 17:34 ` Imre Deak
2010-03-17 20:14 ` Ville Syrjälä
2010-03-18 8:52 ` Imre Deak
2010-03-18 15:26 ` Ville Syrjälä
2010-03-19 7:46 ` Imre Deak
2010-03-19 12:23 ` Ville Syrjälä
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=1267802713.25148.146.camel@tubuntu.research.nokia.com \
--to=tomi.valkeinen@nokia.com \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=saaguirre@ti.com \
--cc=ville.syrjala@nokia.com \
/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;
as well as URLs for NNTP newsgroup(s).