public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@ti.com>
To: Tony Lindgren <tony@atomide.com>
Cc: Tero Kristo <t-kristo@ti.com>,
	linux-omap@vger.kernel.org,
	Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
	"Avinash.H.M" <avinashhm@ti.com>,
	"Cousson, Benoit" <b-cousson@ti.com>
Subject: Re: [PATCHv3 1/6] omap: prcm: switch to a chained IRQ handler mechanism
Date: Fri, 24 Jun 2011 09:00:14 -0700	[thread overview]
Message-ID: <87wrgb1apd.fsf@ti.com> (raw)
In-Reply-To: <20110623081940.GW23145@atomide.com> (Tony Lindgren's message of "Thu, 23 Jun 2011 01:19:40 -0700")

Tony Lindgren <tony@atomide.com> writes:

> * Tero Kristo <t-kristo@ti.com> [110622 09:38]:

[...]

>> +struct omap_prcm_irq  __initdata omap_prcm_3xxx_irqs[] = {
>> +	OMAP_PRCM_IRQ("wkup",                  0,
>> +		      CHIP_IS_OMAP3430 | CHIP_GE_OMAP3630ES1_1),
>> +	OMAP_PRCM_IRQ("evgenon",               2,
>> +		      CHIP_IS_OMAP3430 | CHIP_GE_OMAP3630ES1_1),
>> +	OMAP_PRCM_IRQ("evgenoff",              3,
>> +		      CHIP_IS_OMAP3430 | CHIP_GE_OMAP3630ES1_1),
> ...
>
> Please note consider that this data will be coming from device
> tree and will disappear from here. We won't be merging any new
> data after v3.1 unless it comes from device tree. 

Personally, I don't think this qualifies as device-tree data.  At least
not yet, since the device tree does not currently handle this type of
thing since it's not a real interrupt controller.

Even for the newly proposed (but not merged) irq_domain stuff in the
device tree to work, there needs to be an irq_desc for each of the
"linux IRQs" (to use the term from the irq_domain stuff), so the above
mapping of names needs to exist in order to create the irq_descs so that
irq_domains can even work.

Also, until the rest of our IRQ infrastructure is converted to device
tree (which will also need irq_domains), and until there is a way to
describe the PRCM in the device tree, I don't think it makes sense to
use device tree to describe this small amount of data (which is also
__initdata.)

> So this too will need to be converted because we won't be able to add
> support for new omaps otherwise.

For small amounts of data like this, I think we can.  

As long as we're working on the device tree for the big items, I think
we can make a case that items like this belong in the kernel.  In my
opinion, just because it's data, doesn't mean it always belongs in the
device tree.  Some kinds of data will always be needed to create
infrastructure even for the device tree to work.  I think interrupts are
one of those items.

Kevin

  parent reply	other threads:[~2011-06-24 16:00 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-22 16:42 [PATCHv3 0/6] PRCM chain handler Tero Kristo
2011-06-22 16:42 ` [PATCHv3 1/6] omap: prcm: switch to a chained IRQ handler mechanism Tero Kristo
2011-06-22 23:53   ` Kevin Hilman
2011-06-23  7:24     ` Tero Kristo
2011-06-23  8:19   ` Tony Lindgren
2011-06-23  9:08     ` Tero Kristo
2011-06-23  9:51       ` Tony Lindgren
2011-06-24 16:00     ` Kevin Hilman [this message]
2011-06-24 21:02   ` Kevin Hilman
2011-06-22 16:42 ` [PATCHv3 2/6] PRCM: Add support for PAD wakeup interrupts Tero Kristo
2011-06-23 10:23   ` Govindraj
2011-06-24 21:34     ` Kevin Hilman
2011-06-24 21:21   ` Kevin Hilman
2011-06-22 16:42 ` [PATCHv3 3/6] OMAP: PRCM: Added an api to get id for a PRCM event Tero Kristo
2011-06-24 21:58   ` Kevin Hilman
2011-06-22 16:42 ` [PATCHv3 4/6] OMAP3: PM: Use PRCM chain handler Tero Kristo
2011-06-24 21:57   ` Kevin Hilman
2011-06-22 16:42 ` [PATCHv3 5/6] OMAP3: Serial: Made serial to work properly with " Tero Kristo
2011-06-22 17:09   ` Tero Kristo
2011-06-23 10:30     ` Govindraj
2011-06-23  8:21   ` Tony Lindgren
2011-06-23  9:11     ` Tero Kristo
2011-06-23 10:00       ` Tony Lindgren
2011-06-23 10:35         ` Govindraj
2011-06-23 11:12           ` Tony Lindgren
2011-06-24 15:15         ` Kevin Hilman
2011-06-24 22:00   ` Kevin Hilman
2011-06-22 16:42 ` [PATCHv3 6/6] OMAP3: Serial tty: Added resume_idle calls to critical points Tero Kristo
2011-06-27 15:02 ` [PATCHv3 0/6] PRCM chain handler Tero Kristo

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=87wrgb1apd.fsf@ti.com \
    --to=khilman@ti.com \
    --cc=avinashhm@ti.com \
    --cc=b-cousson@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=t-kristo@ti.com \
    --cc=thomas.petazzoni@free-electrons.com \
    --cc=tony@atomide.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