From: David Miller <davem@davemloft.net>
To: avorontsov@ru.mvista.com
Cc: sparclinux@vger.kernel.org, linuxppc-dev@ozlabs.org, paulus@samba.org
Subject: Re: [PATCH 1/3]: sparc: Implement irq_of_parse_and_map() and irq_dispose_mapping().
Date: Thu, 21 Aug 2008 14:59:46 -0700 (PDT) [thread overview]
Message-ID: <20080821.145946.01710005.davem@davemloft.net> (raw)
In-Reply-To: <20080821215611.GA14354@oksana.dev.rtsoft.ru>
From: Anton Vorontsov <avorontsov@ru.mvista.com>
Date: Fri, 22 Aug 2008 01:56:11 +0400
> On Thu, Aug 21, 2008 at 12:10:17AM -0700, David Miller wrote:
> > @@ -96,6 +96,14 @@ static inline void of_node_put(struct device_node *node)
> > {
> > }
> >
> > +/* These routines are here to provide compatibility with how powerpc
> > + * handles IRQ mapping for OF device nodes. We precompute and permanently
> > + * register them in the of_device objects, whereas powerpc computes them
> > + * on request.
> > + */
> > +extern int irq_of_parse_and_map(struct device_node *node, int index);
>
> On powerpc irq_of_parse_and_map() returns unsigned type.
>
> > +#define irq_dispose_mapping(irq) do { } while (0)
>
> I'd rather write it as a static inline function, for type checking,
> plus, I think with this macros gcc may generate warnings about
> defined but unused variables.
Thanks, I'll fix that.
> > +
> > /*
> > * NB: This is here while we transition from using asm/prom.h
> > * to linux/of.h
> > diff --git a/arch/sparc/kernel/of_device.c b/arch/sparc/kernel/of_device.c
> > index cc4c235..56e9a71 100644
> > --- a/arch/sparc/kernel/of_device.c
> > +++ b/arch/sparc/kernel/of_device.c
> > @@ -29,6 +29,17 @@ struct of_device *of_find_device_by_node(struct device_node *dp)
> > }
> > EXPORT_SYMBOL(of_find_device_by_node);
> >
> > +int irq_of_parse_and_map(struct device_node *node, int index)
> > +{
> > + struct of_device *op = of_find_device_by_node(node);
> > +
> > + if (!op || index >= op->num_irqs)
> > + return 0xffffffff;
>
> This is valid virq, unfortunately. There is only one invalid virq: 0.
> With this most drivers will fail to identify 'there is no irq' case.
> Does virq0 has special meaning on sparc?
No, I'll fix this up, thanks.
WARNING: multiple messages have this Message-ID (diff)
From: David Miller <davem@davemloft.net>
To: avorontsov@ru.mvista.com
Cc: sparclinux@vger.kernel.org, linuxppc-dev@ozlabs.org, paulus@samba.org
Subject: Re: [PATCH 1/3]: sparc: Implement irq_of_parse_and_map() and
Date: Thu, 21 Aug 2008 21:59:46 +0000 [thread overview]
Message-ID: <20080821.145946.01710005.davem@davemloft.net> (raw)
In-Reply-To: <20080821215611.GA14354@oksana.dev.rtsoft.ru>
From: Anton Vorontsov <avorontsov@ru.mvista.com>
Date: Fri, 22 Aug 2008 01:56:11 +0400
> On Thu, Aug 21, 2008 at 12:10:17AM -0700, David Miller wrote:
> > @@ -96,6 +96,14 @@ static inline void of_node_put(struct device_node *node)
> > {
> > }
> >
> > +/* These routines are here to provide compatibility with how powerpc
> > + * handles IRQ mapping for OF device nodes. We precompute and permanently
> > + * register them in the of_device objects, whereas powerpc computes them
> > + * on request.
> > + */
> > +extern int irq_of_parse_and_map(struct device_node *node, int index);
>
> On powerpc irq_of_parse_and_map() returns unsigned type.
>
> > +#define irq_dispose_mapping(irq) do { } while (0)
>
> I'd rather write it as a static inline function, for type checking,
> plus, I think with this macros gcc may generate warnings about
> defined but unused variables.
Thanks, I'll fix that.
> > +
> > /*
> > * NB: This is here while we transition from using asm/prom.h
> > * to linux/of.h
> > diff --git a/arch/sparc/kernel/of_device.c b/arch/sparc/kernel/of_device.c
> > index cc4c235..56e9a71 100644
> > --- a/arch/sparc/kernel/of_device.c
> > +++ b/arch/sparc/kernel/of_device.c
> > @@ -29,6 +29,17 @@ struct of_device *of_find_device_by_node(struct device_node *dp)
> > }
> > EXPORT_SYMBOL(of_find_device_by_node);
> >
> > +int irq_of_parse_and_map(struct device_node *node, int index)
> > +{
> > + struct of_device *op = of_find_device_by_node(node);
> > +
> > + if (!op || index >= op->num_irqs)
> > + return 0xffffffff;
>
> This is valid virq, unfortunately. There is only one invalid virq: 0.
> With this most drivers will fail to identify 'there is no irq' case.
> Does virq0 has special meaning on sparc?
No, I'll fix this up, thanks.
next prev parent reply other threads:[~2008-08-21 21:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-21 7:10 [PATCH 1/3]: sparc: Implement irq_of_parse_and_map() and irq_dispose_mapping() David Miller
2008-08-21 7:10 ` [PATCH 1/3]: sparc: Implement irq_of_parse_and_map() and David Miller
2008-08-21 21:56 ` [PATCH 1/3]: sparc: Implement irq_of_parse_and_map() and irq_dispose_mapping() Anton Vorontsov
2008-08-21 21:56 ` [PATCH 1/3]: sparc: Implement irq_of_parse_and_map() and Anton Vorontsov
2008-08-21 21:59 ` David Miller [this message]
2008-08-21 21:59 ` David Miller
-- strict thread matches above, loose matches on Subject: below --
2008-08-22 4:21 [PATCH 1/3]: sparc: Implement irq_of_parse_and_map() and irq_dispose_mapping() David Miller
2008-08-22 4:21 ` [PATCH 1/3]: sparc: Implement irq_of_parse_and_map() and David Miller
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=20080821.145946.01710005.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=avorontsov@ru.mvista.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.org \
--cc=sparclinux@vger.kernel.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 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.