From: Andreas Larsson <andreas@gaisler.com>
To: Lars Poeschel <larsi@wh2.tu-dresden.de>
Cc: poeschel@lemonage.de, grant.likely@linaro.org,
linus.walleij@linaro.org, linux-gpio@vger.kernel.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
mark.rutland@arm.com, ian.campbell@citrix.com,
galak@codeaurora.org, pawel.moll@arm.com, tomasz.figa@gmail.com,
swarren@wwwdotorg.org,
Javier Martinez Canillas <javier.martinez@collabora.co.uk>,
Enric Balletbo i Serra <eballetbo@gmail.com>,
Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>,
Santosh Shilimkar <santosh.shilimkar@ti.com>,
Kevin Hilman <khilman@linaro.org>, Balaji T K <balajitk@ti.com>,
Tony Lindgren <tony@atomide.com>,
Jon Hunter <jgchunter@gmail.com>
Subject: Re: [PATCH v2] gpio: interrupt consistency check for OF GPIO IRQs
Date: Thu, 22 Aug 2013 15:16:18 +0200 [thread overview]
Message-ID: <52160F22.2080701@gaisler.com> (raw)
In-Reply-To: <1377092334-770-1-git-send-email-larsi@wh2.tu-dresden.de>
On 2013-08-21 15:38, Lars Poeschel wrote:
> +static void of_gpio_scan_irq_lines(const struct device_node *const node,
> + struct device_node *const gcn,
> + struct irq_domain *const irq_domain,
> + const u32 intsize,
> + const struct gpio_chip * const gc,
> + bool request)
> +{
> + struct device_node *child;
> + struct device_node *irq_parent;
> + const __be32 *intspec;
> + u32 intlen;
> + int ret;
> + int i;
> + irq_hw_number_t hwirq;
> + unsigned int type;
> +
> + if (node == NULL)
> + return;
> +
> + for_each_child_of_node(node, child) {
> + of_gpio_scan_irq_lines(child, gcn, irq_domain, intsize, gc,
> + request);
> + /* Check if we have an IRQ parent, else continue */
> + irq_parent = of_irq_find_parent(child);
Hi!
This call to of_irq_find_parent breaks gpiolib-of for SPARC due to the
fact that the function is undefined when !defined(CONFIG_OF_IRQ) &&
defined(CONFIG_OF).
Defining the empty of_irq_find_parent in include/linux/of_irq.h when
!defined(CONFIG_OF_IRQ) instead of the current case when
!defined(CONFIG_OF) would solve the immediate compilation problem.
However, when !defined(CONFIG_OF_IRQ) (i.e. SPARC in this case) the
whole tree walking will never accomplish anything, so it would be good
if of_gpiochip_reserve_irq_lines is just an empty dummy or something
like that when !defined(CONFIG_OF_IRQ).
Cheers,
Andreas Larsson
next prev parent reply other threads:[~2013-08-22 13:40 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-21 13:38 [PATCH v2] gpio: interrupt consistency check for OF GPIO IRQs Lars Poeschel
2013-08-21 21:49 ` Tomasz Figa
2013-08-21 23:10 ` Stephen Warren
2013-08-21 23:27 ` Linus Walleij
2013-08-22 20:53 ` Stephen Warren
2013-08-23 9:51 ` Lars Poeschel
2013-08-23 18:38 ` Linus Walleij
2013-08-23 19:49 ` Stephen Warren
2013-08-29 18:51 ` Linus Walleij
2013-08-21 23:36 ` Linus Walleij
2013-08-22 21:10 ` Stephen Warren
2013-08-23 9:40 ` Lars Poeschel
2013-08-23 19:48 ` Stephen Warren
2013-08-26 10:30 ` Lars Poeschel
2013-08-23 18:45 ` Linus Walleij
2013-08-23 19:52 ` Stephen Warren
2013-08-23 19:55 ` Tomasz Figa
2013-08-23 20:55 ` Stephen Warren
2013-08-26 10:45 ` Lars Poeschel
2013-08-27 20:05 ` Stephen Warren
2013-08-29 19:00 ` Linus Walleij
2013-08-30 20:08 ` Stephen Warren
2013-09-02 9:43 ` Lars Poeschel
2013-09-03 12:28 ` Linus Walleij
2013-08-22 9:01 ` Lars Poeschel
2013-08-22 21:08 ` Stephen Warren
2013-08-22 22:30 ` Tomasz Figa
2013-08-22 13:16 ` Andreas Larsson [this message]
2013-08-26 10:56 ` Lars Poeschel
2013-08-26 11:29 ` Andreas Larsson
2013-08-26 14:04 ` Lars Poeschel
2013-08-27 6:06 ` Andreas Larsson
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=52160F22.2080701@gaisler.com \
--to=andreas@gaisler.com \
--cc=balajitk@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=eballetbo@gmail.com \
--cc=galak@codeaurora.org \
--cc=grant.likely@linaro.org \
--cc=ian.campbell@citrix.com \
--cc=javier.martinez@collabora.co.uk \
--cc=jgchunter@gmail.com \
--cc=khilman@linaro.org \
--cc=larsi@wh2.tu-dresden.de \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=plagnioj@jcrosoft.com \
--cc=poeschel@lemonage.de \
--cc=santosh.shilimkar@ti.com \
--cc=swarren@wwwdotorg.org \
--cc=tomasz.figa@gmail.com \
--cc=tony@atomide.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 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).