public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@ti.com>
To: "Pedanekar, Hemant" <hemantp@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	"tony@atomide.com" <tony@atomide.com>
Subject: Re: [PATCH v4 1/4] TI816X: Update common omap platform files
Date: Mon, 24 Jan 2011 12:02:44 -0800	[thread overview]
Message-ID: <87aaiq9ijf.fsf@ti.com> (raw)
In-Reply-To: <2A3DCF3DA181AD40BDE86A3150B27B6B036A8DB4B3@dbde02.ent.ti.com> (Hemant Pedanekar's message of "Sat, 22 Jan 2011 07:40:23 +0530")

"Pedanekar, Hemant" <hemantp@ti.com> writes:

> Hi Kevin,
>
> Hilman, Kevin wrote on Saturday, January 22, 2011 4:01 AM:
>
>> Hi Hemant,
>> 
>> Hemant Pedanekar <hemantp@ti.com> writes:
>> 
>>> This patch updates the common platform files with TI816X support. Also
>>> adds new files for TI816X module base addresses and irq definitions.
>> [...]
>> 
>>> diff --git a/arch/arm/plat-omap/include/plat/irqs-ti816x.h
>> b/arch/arm/plat-omap/include/plat/irqs-ti816x.h
>>> new file mode 100644
>>> index 0000000..3ec5d1b
> [...]
>>> +#define TI816X_IRQ_SECPUBINT	116
>>> +#define TI816X_IRQ_SECSECINT	117
>>> +#define TI816X_IRQ_SECPUBSWINT	118
>>> +#define TI816X_IRQ_SECSECSWINT	119
>>> +#define TI816X_IRQ_SMRFLX0	120
>>> +#define TI816X_IRQ_SMRFLX1	121
>>> +#define TI816X_IRQ_SYS_MMU	122
>>> +#define TI816X_IRQ_MC_MMU	123
>>> +#define TI816X_IRQ_DMM		124
>>> +
>>> +
>>> +#endif
>> 
>> For new platforms, We don't need to have a list of all the
>> IRQ numbers.
>> 
>> Driver code should always be getting IRQ numbers (and base addresses
>> etc.) from struct resource/platform_data, which is populated
>> from omap_hwmod.
>>
>
> Are you suggesting to get rid of this file altogether or the IRQs which 
> may never be used from kernel be removed from this file (and added later
> If needed)?
>   
> Or shall I add this file only in hwmod patch which will be submitted later?

You can get rid of the file altogether.  Even the hwmod data can just
have IRQ numbers and you shouldn't need to add a header file with the
defines.

Kevin 

  reply	other threads:[~2011-01-24 20:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-10 16:37 [PATCH v4 1/4] TI816X: Update common omap platform files Hemant Pedanekar
2011-01-18  0:08 ` Paul Walmsley
2011-01-18  1:07   ` Pedanekar, Hemant
2011-01-21 22:31 ` Kevin Hilman
2011-01-22  2:10   ` Pedanekar, Hemant
2011-01-24 20:02     ` Kevin Hilman [this message]
2011-01-25  1:10       ` Pedanekar, Hemant

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=87aaiq9ijf.fsf@ti.com \
    --to=khilman@ti.com \
    --cc=hemantp@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --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