Thread (15 messages) flat view 15 messages, 5 authors, 2011-02-18
STALE5671d

Revision v5 of 6 in this series.

Revisions (6)
  1. v3 [diff vs current]
  2. v4 [diff vs current]
  3. v5 [diff vs current]
  4. v5 [diff vs current]
  5. v5 [diff vs current]
  6. v5 current

[PATCH v5 3/5] OMAP4: hwmod data: add mailbox data

From: Cousson, Benoit <hidden>
Date: 2011-02-15 22:05:46
Also in: linux-omap

Hi Omar,

On 2/15/2011 10:55 PM, Ramirez Luna, Omar wrote:
Hi Benoit,

On Mon, Feb 14, 2011 at 9:00 AM, Cousson, Benoit[off-list ref]  wrote:
quoted
quoted
+static struct omap_hwmod_irq_info omap44xx_mailbox_irqs[] = {
+       { .name = "mbox", .irq = 26 + OMAP44XX_IRQ_GIC_START, },
The original entry was unnamed since it is an unique entry and thus does not
need to be differentiate on this platform.

        { .irq = 26 + OMAP44XX_IRQ_GIC_START },

Do you really need to have a name here? The strategy being to provide a name
only if more than one entry exist.
It is perfectibility doable, I'm just trying to understand your rational.
It is this way instead of plain platform_get_irq because omap2420 has
two interrupt sources to MPU and mailbox driver uses
platform_get_irq_byname to get the irq number.
This is what I was thinking, except that on OMAP2420 the names are:
+	{ .name = "dsp", .irq = 26, },
+	{ .name = "iva", .irq = 34, },

and on OMAP2430 and OMAP3
+	{ .name = "dsp", .irq = 26, },

so why is it named "mbox" on OMAP4?

If you have to do several platform_get_irq_byname to get this one, I'd 
prefer to get rid of that name for OMAP4. It will make mailbox irq 
consistent with the other hwmods.

Thanks,
Benoit
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help