All of lore.kernel.org
 help / color / mirror / Atom feed
From: archit taneja <archit@ti.com>
To: "Taneja, Archit" <archit@ti.com>
Cc: "Valkeinen, Tomi" <tomi.valkeinen@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: Mon, 21 Feb 2011 11:33:00 +0530	[thread overview]
Message-ID: <4D620014.3040207@ti.com> (raw)
In-Reply-To: <1298268030-25936-1-git-send-email-archit@ti.com>

Hi,

On Monday 21 February 2011 11:30 AM, Taneja, Archit wrote:
> Currently, the core DSS platform device requests for an irq line for OMAP2 and
> OMAP3. Make DISPC and DSI platform devices request for a shared IRQ line.
>
> On OMAP3, the logical OR of DSI and DISPC interrupt lines goes to the MPU. There
> is a register DSS_IRQSTATUS which tells if the interrupt came from DISPC or DSI.
>
> On OMAP2, there is no DSI, only DISPC interrupts goto the MPU. There is no
> DSS_IRQSTATUS register.
>
> Hence, it makes more sense to have separate irq handlers corresponding to the
> DSS sub modules instead of having a common handler.
>
> Since on OMAP3 the logical OR of the lines goes to MPU, the irq line is shared
> among the IRQ handlers.
>
> The hwmod irq info has been removed for DSS to DISPC and DSI for OMAP2 and OMAP3
> hwmod databases. The Probes of DISPC and DSI now request for irq handlers.
>
> Signed-off-by: Archit Taneja<archit@ti.com>
> ---
> v3:
> -return IRQ_NONE instead of IRQ_HANDLED when interrupt is not ours
> -don't print module names wehn using DSSERR
> v2: Removed checking with DSS_IRQSTATUS.
>
> v3 tested on 3430sdp with sharp ls panel and 3430sdp with a Taal panel.
>

Minor correction: Subject should have been:

[PATCH v3] OMAP: DSS2: Have separate irq handlers for DISPC and DSI

<snip>

Regards,
Archit

  reply	other threads:[~2011-02-21  6:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-21  6:00 [PATCH] OMAP: DSS2: Have separate irq handlers for DISPC and DSI Archit Taneja
2011-02-21  6:03 ` archit taneja [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-02-17 14:25 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
2011-02-18 10:00     ` Tomi Valkeinen
2011-02-18 11:05       ` archit taneja
2011-02-18 11:11         ` Tomi Valkeinen

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=4D620014.3040207@ti.com \
    --to=archit@ti.com \
    --cc=b-cousson@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.