From: Rob Herring <robherring2@gmail.com>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [RFC 1/2] irq_domain: Create common xlate functions that device drivers can use
Date: Thu, 26 Jan 2012 08:50:01 -0600 [thread overview]
Message-ID: <4F216819.7030106@gmail.com> (raw)
In-Reply-To: <CACxGe6tgGqQSThzVVEzwOdtYkjKHT1uQhZBOkCTwkutyKXDCAg@mail.gmail.com>
On 01/25/2012 11:59 AM, Grant Likely wrote:
> On Tue, Jan 24, 2012 at 10:35 PM, Grant Likely
> <grant.likely@secretlab.ca> wrote:
>> On Tue, Jan 24, 2012 at 6:50 PM, Rob Herring <robherring2@gmail.com> wrote:
>>>
>>>
>>> On 01/24/2012 06:18 PM, Grant Likely wrote:
>>>> Rather than having each interrupt controller driver creating its own barely
>>>> unique .xlate function for irq_domain, create a library of translators which
>>>> any driver can use directly.
>>>>
>>>> diff --git a/include/linux/irqdomain.h b/include/linux/irqdomain.h
>>>> index e7379a3..5e497a0 100644
>>>> --- a/include/linux/irqdomain.h
>>>> +++ b/include/linux/irqdomain.h
>>>> @@ -110,6 +110,9 @@ struct irq_domain {
>>>> void *host_data;
>>>> irq_hw_number_t inval_irq;
>>>>
>>>> + /* Data for common irq xlate functions */
>>>> + unsigned int xlate_type;
>>>> +
>>>
>>> How does this get set? Do we want interrupt controllers messing with the
>>> domain struct directly long term?
>>
>> It defaults to IRQ_TYPE_NONE in the alloc function and drivers can
>> override it. Alternately it could be made part of the
>> irq_domain_add() arguments, but I'm not thrilled with adding a whole
>> bunch of arguments to the function prototype.
>
> Do you like this better (built on top of this patch)?
Yes, I think it's better.
> diff --git a/kernel/irq/irqdomain.c b/kernel/irq/irqdomain.c
> index ef2b1fe..7856c04 100644
> --- a/kernel/irq/irqdomain.c
> +++ b/kernel/irq/irqdomain.c
> @@ -701,12 +701,10 @@ int irq_domain_xlate_onecell(struct irq_domain
> *d, struct device_node *ctrlr,
> const u32 *intspec, unsigned int intsize,
> unsigned long *out_hwirq, unsigned int *out_type)
> {
> - if (WARN(intsize < 1, "Bad intspec for %s: intsize=%i < 1\n",
> - ctrlr->full_name, intsize))
> + if (WARN_ON(intsize < 1))
> return -EINVAL;
> - *out_hwirq = intspec[0];
> - *out_type = d->xlate_type;
> - return 0;
> + return irq_domain_xlate_onetwocell(d, ctrlr, intspec, 1,
> + out_hwirq, out_type);
> }
> EXPORT_SYMBOL_GPL(irq_domain_xlate_onecell);
>
> @@ -721,12 +719,10 @@ int irq_domain_xlate_twocell(struct irq_domain
> *d, struct device_node *ctrlr,
> const u32 *intspec, unsigned int intsize,
> irq_hw_number_t *out_hwirq, unsigned int *out_type)
> {
> - if (WARN(intsize < 2, "Bad intspec for %s: intsize=%i < 2\n",
> - ctrlr->full_name, intsize))
> + if (WARN_ON(intsize < 2))
> return -EINVAL;
> - *out_hwirq = intspec[0];
> - *out_type = intspec[1] & IRQ_TYPE_SENSE_MASK;
> - return 0;
> + return irq_domain_xlate_onetwocell(d, ctrlr, intspec, intsize,
> + out_hwirq, out_type);
> }
> EXPORT_SYMBOL_GPL(irq_domain_xlate_twocell);
>
> @@ -746,8 +742,7 @@ int irq_domain_xlate_onetwocell(struct irq_domain *d,
> const u32 *intspec, unsigned int intsize,
> unsigned long *out_hwirq, unsigned int *out_type)
> {
> - if (WARN(intsize < 1, "Bad intspec for %s: intsize=%i < 1\n",
> - ctrlr->full_name, intsize))
> + if (WARN_ON(intsize < 1))
> return -EINVAL;
> *out_hwirq = intspec[0];
> *out_type = d->xlate_type;
next prev parent reply other threads:[~2012-01-26 14:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-25 0:18 [RFC 1/2] irq_domain: Create common xlate functions that device drivers can use Grant Likely
2012-01-25 0:18 ` [RFC 2/2] irqdomain/powerpc: Replace custom xlate functions with library functions Grant Likely
2012-01-25 1:50 ` [RFC 1/2] irq_domain: Create common xlate functions that device drivers can use Rob Herring
2012-01-25 5:35 ` Grant Likely
2012-01-25 17:59 ` Grant Likely
2012-01-26 14:50 ` Rob Herring [this message]
2012-01-26 18:15 ` Grant Likely
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=4F216819.7030106@gmail.com \
--to=robherring2@gmail.com \
--cc=grant.likely@secretlab.ca \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
/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;
as well as URLs for NNTP newsgroup(s).