[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Wed, 28 Mar 2012 18:33:54 -0700
From: David Daney <david.daney@...ium.com>
To: Grant Likely <grant.likely@...retlab.ca>
CC: David Daney <ddaney.cavm@...il.com>,
"linux-mips@...ux-mips.org" <linux-mips@...ux-mips.org>,
"ralf@...ux-mips.org" <ralf@...ux-mips.org>,
"devicetree-discuss@...ts.ozlabs.org"
<devicetree-discuss@...ts.ozlabs.org>,
Rob Herring <rob.herring@...xeda.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v7 2/4] MIPS: Octeon: Setup irq_domains for interrupts.
On 03/28/2012 03:31 PM, Grant Likely wrote:
> On Mon, 26 Mar 2012 12:31:19 -0700, David Daney<ddaney.cavm@...il.com> wrote:
>> From: David Daney<david.daney@...ium.com>
>>
>> Create two domains. One for the GPIO lines, and the other for on-chip
>> sources.
>>
>> Signed-off-by: David Daney<david.daney@...ium.com>
>> ---
> [...]
>> +struct octeon_irq_gpio_domain_data {
>> + unsigned int base_hwirq;
>> +};
>
> Hmmm...
>
>> +static int octeon_irq_gpio_xlat(struct irq_domain *d,
>> + struct device_node *node,
>> + const u32 *intspec,
>> + unsigned int intsize,
>> + unsigned long *out_hwirq,
>> + unsigned int *out_type)
>> +{
> [...]
>> + *out_hwirq = gpiod->base_hwirq + pin;
>
> ...base_hwirq is only used here...
>
> [...]
>> + gpiod = kzalloc(sizeof (*gpiod), GFP_KERNEL);
>> + if (gpiod) {
>> + /* gpio domain host_data is the base hwirq number. */
>> + gpiod->base_hwirq = 16;
>> + irq_domain_add_linear(gpio_node, 16,&octeon_irq_domain_gpio_ops, gpiod);
>
> ... and it is unconditionally set to 16. It looks to me like
> base_hwirq and the associated kzalloc() is unnecessary.
>
There is a little information asymmetry here. You don't know that I
have a patch queued up to add another user of the GPIO irq_domain that
has a different base_hwirq.
I could re-do this to hard code it, and then add it back. But it would
really just be busy work.
David Daney
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists