All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Cousson, Benoit" <b-cousson@ti.com>
To: "S, Venkatraman" <svenkatr@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 0/2] OMAP: Update nr_irqs field in machine descriptors
Date: Thu, 25 Aug 2011 13:49:33 +0200	[thread overview]
Message-ID: <4E5636CD.4080302@ti.com> (raw)
In-Reply-To: <1314215215-18683-1-git-send-email-svenkatr@ti.com>

Hi Venkat,

On 8/24/2011 9:46 PM, S, Venkatraman wrote:
> As part of an effort to get single ARM kernel binary [1],
> multiple  definitions of NR_IRQS under various platforms
> have to be reconciled and abstracted away from common code.
>
> This patch series takes the small step of populating the
> machine descriptors with the pre-existing nr_irqs field.
> Eventually, the common irq handler code will only look at this
> field and not the compile time constant.

Not related to this patch, but still on that topic. The current NR_IRQS 
depends as well on board stuff, like for example : the Phoenix 
IRQs:TWL6030_IRQ_BASE, TWL6040_CODEC_IRQ_BASE.
Is there a plan to get rid of this static defines?

Thanks,
Benoit

WARNING: multiple messages have this Message-ID (diff)
From: b-cousson@ti.com (Cousson, Benoit)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] OMAP: Update nr_irqs field in machine descriptors
Date: Thu, 25 Aug 2011 13:49:33 +0200	[thread overview]
Message-ID: <4E5636CD.4080302@ti.com> (raw)
In-Reply-To: <1314215215-18683-1-git-send-email-svenkatr@ti.com>

Hi Venkat,

On 8/24/2011 9:46 PM, S, Venkatraman wrote:
> As part of an effort to get single ARM kernel binary [1],
> multiple  definitions of NR_IRQS under various platforms
> have to be reconciled and abstracted away from common code.
>
> This patch series takes the small step of populating the
> machine descriptors with the pre-existing nr_irqs field.
> Eventually, the common irq handler code will only look at this
> field and not the compile time constant.

Not related to this patch, but still on that topic. The current NR_IRQS 
depends as well on board stuff, like for example : the Phoenix 
IRQs:TWL6030_IRQ_BASE, TWL6040_CODEC_IRQ_BASE.
Is there a plan to get rid of this static defines?

Thanks,
Benoit

  parent reply	other threads:[~2011-08-25 11:49 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-24 19:46 [PATCH 0/2] OMAP: Update nr_irqs field in machine descriptors Venkatraman S
2011-08-24 19:46 ` Venkatraman S
2011-08-24 19:46 ` [PATCH 1/2] omap2+: Populate " Venkatraman S
2011-08-24 19:46   ` Venkatraman S
2011-08-24 19:46 ` [PATCH 2/2] omap1: " Venkatraman S
2011-08-24 19:46   ` Venkatraman S
2011-08-25 11:49 ` Cousson, Benoit [this message]
2011-08-25 11:49   ` [PATCH 0/2] OMAP: Update " Cousson, Benoit
2011-08-25 14:55   ` S, Venkatraman
2011-08-25 14:55     ` S, Venkatraman
2011-10-06 19:50     ` Tony Lindgren
2011-10-06 19:50       ` Tony Lindgren
2011-10-07 20:15       ` Nicolas Pitre
2011-10-07 20:15         ` Nicolas Pitre
2011-10-07 20:51         ` Tony Lindgren
2011-10-07 20:51           ` Tony Lindgren
2011-10-07 22:18           ` Nicolas Pitre
2011-10-07 22:18             ` Nicolas Pitre

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=4E5636CD.4080302@ti.com \
    --to=b-cousson@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=svenkatr@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.