From: archit taneja <archit@ti.com>
To: "Cousson, Benoit" <b-cousson@ti.com>
Cc: "Semwal, Sumit" <sumit.semwal@ti.com>,
"Balbi, Felipe" <balbi@ti.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"Valkeinen, Tomi" <tomi.valkeinen@ti.com>
Subject: Re: OMAP: DSS2: Common IRQ handler for all OMAPs
Date: Tue, 15 Feb 2011 18:13:30 +0530 [thread overview]
Message-ID: <4D5A74F2.1060100@ti.com> (raw)
In-Reply-To: <4D5A5A5C.4070909@ti.com>
Hi,
<snip>
>>>>
>>>> Is it okay to have the same irq entry for 2 different hwmods?
>>>> This requirement comes from OMAP3 where dispc and dsi have a common irq
>>>> line, where as on OMAP4 dispc and dsi have separate irq lines.
>>>
>>> Well, no. I explained that in one of my comment about hwmod modification.
>>> The hwmod data are reflecting the exact HW capabilities.
>>> So, if there is a change in the HW, the hwmod will be different.
>>> It is up to the driver to adapt to this change.
>> I guess what Archit wanted to say is, for hw IPs DISPC and DSI, on
>> OMAP3, have a common IRQ line, so could both their hwmod databases
>> have the same IRQ added for them? This would us call, for a common IRQ
>> line shared w/ DISPC and DSI, like
>> mentioned in Tomi's sample code above.
>
> OK, thanks for the clarification, actually I missed a little bit the
> point :-(
>
> So in fact the 2 modules share that same IRQ today, and you just want to
> populate both hwmod with the same input.
> If this is a real OR between the two IRQ lines, meaning the dispc cannot
> mask the dsi IRQ or the opposite, then having the same IRQ number in the
> two different hwmods is a correct representation of the HW.
There is a real OR between the 2 irq lines in OMAP3, as there is no
DSS_IRQENABLE, but there is a DSS_IRQSTATUS.
You can mask one of DISPC or DSI by zeroing all the bits in
DISPC_IRQENABLE or DSI_IRQENABLE respectively. But there is no higher
level register to mask them.
<snip>
Regards,
Archit
next prev parent reply other threads:[~2011-02-15 12:42 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-02 8:56 [PATCH] OMAP: DSS2: Common IRQ handler for all OMAPs Archit Taneja
2011-02-14 14:21 ` Tomi Valkeinen
2011-02-14 14:30 ` Felipe Balbi
2011-02-15 4:28 ` archit taneja
2011-02-15 7:27 ` Tomi Valkeinen
2011-02-15 8:30 ` archit taneja
2011-02-15 8:37 ` Tomi Valkeinen
2011-02-15 8:47 ` archit taneja
2011-02-15 9:25 ` archit taneja
2011-02-15 10:23 ` Cousson, Benoit
2011-02-15 10:28 ` Semwal, Sumit
2011-02-15 10:50 ` Cousson, Benoit
2011-02-15 12:43 ` archit taneja [this message]
2011-02-15 12:56 ` Cousson, Benoit
2011-02-15 10:57 ` Felipe Balbi
2011-02-15 11:25 ` Tomi Valkeinen
2011-02-15 11:42 ` Felipe Balbi
2011-02-15 8:05 ` Felipe Balbi
2011-02-15 8:20 ` archit taneja
2011-02-15 8:23 ` Felipe Balbi
2011-02-15 7:45 ` Tomi Valkeinen
2011-02-15 8: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=4D5A74F2.1060100@ti.com \
--to=archit@ti.com \
--cc=b-cousson@ti.com \
--cc=balbi@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=sumit.semwal@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