From: archit taneja <archit@ti.com>
To: "Valkeinen, Tomi" <tomi.valkeinen@ti.com>
Cc: "Turquette, Mike" <mturquette@ti.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"Cousson, Benoit" <b-cousson@ti.com>
Subject: Re: [PATCH] OMAP: DSS2: Have separate irq handlers for DISPC and DSI
Date: Fri, 18 Feb 2011 15:55:58 +0530 [thread overview]
Message-ID: <4D5E4936.7040807@ti.com> (raw)
In-Reply-To: <1298022650.24062.20.camel@deskari>
On Friday 18 February 2011 03:20 PM, Valkeinen, Tomi wrote:
> On Fri, 2011-02-18 at 03:45 -0600, Turquette, Mike wrote:
>
> <snip>
>
>> PRM_IRQSTATUS_* registers will have status bits set even when the
>> corresponding PRM_IRQENABLE_* bits are not set. The common assumption
>> was that status bits would not be set if interrupts weren't enabled
>> and this caused us some issues in prcm_interrupt_handler some time
>> back. I don't know how DSS_IRQSTATUS works under the hood, but be
>> careful of such assumptions :-)
And, there is no DSS_IRQENABLE at all in our case :)
>
> That's how DISPC_IRQ* and DSI_IRQ* also works. But that's not what this
> discussion was about =). DISPC and DSI have a shared interrupt line, and
> there's a DSS_IRQSTATUS register with two bits, telling if the interrupt
> was for DISPC or DSI.
>
> Tomi
>
>
next prev parent reply other threads:[~2011-02-18 10:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-17 14:25 [PATCH] OMAP: DSS2: Have separate irq handlers for DISPC and DSI Archit Taneja
2011-02-18 9:10 ` Valkeinen, Tomi
2011-02-18 9:34 ` archit taneja
2011-02-18 9:45 ` Turquette, Mike
2011-02-18 9:50 ` Tomi Valkeinen
2011-02-18 10:25 ` archit taneja [this message]
2011-02-18 10:00 ` Tomi Valkeinen
2011-02-18 11:05 ` archit taneja
2011-02-18 11:11 ` Tomi Valkeinen
-- strict thread matches above, loose matches on Subject: below --
2011-02-21 6:00 Archit Taneja
2011-02-21 6:03 ` archit taneja
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=4D5E4936.7040807@ti.com \
--to=archit@ti.com \
--cc=b-cousson@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=mturquette@ti.com \
--cc=tomi.valkeinen@ti.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