[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1761342.TGgYi16yul@wuerfel>
Date: Mon, 11 Jul 2016 17:46:34 +0200
From: Arnd Bergmann <arnd@...db.de>
To: Wan Zongshun <vw@...mu.org>
Cc: linux-arm-kernel@...ts.infradead.org,
Russell King <linux@...linux.org.uk>,
devicetree@...r.kernel.org, linux-clk@...r.kernel.org,
Daniel Lezcano <daniel.lezcano@...aro.org>,
Thomas Gleixner <tglx@...utronix.de>,
linux-kernel@...r.kernel.org, robh@...nel.org,
jason@...edaemon.net, p.zabel@...gutronix.de,
Wan Zongshun <mcuos.com@...il.com>
Subject: Re: [PATCH v2 02/10] irqchip: add irqchip driver for nuc900
On Sunday, July 10, 2016 3:27:22 PM CEST Wan Zongshun wrote:
> +
> +#if !defined(CONFIG_SOC_NUC900)
> #define NR_IRQS (IRQ_ADC+1)
> +#else
> +#define NR_IRQS 62
> +#endif
>
The Kconfig symbols are a bit confusing here: CONFIG_SOC_NUC900
controls the compilation of the soc_device driver, but I guess
what you actually mean here is CONFIG_SOC_NUC970, which is the
support for the actual chip.
Maybe rename the former to something less confusing and change
this to CONFIG_SOC_NUC970?
Ideally, this should just go away once we use SPARSE_IRQ.
Arnd
Powered by blists - more mailing lists