From: Lee Jones <lee.jones@linaro.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
tglx@linutronix.de, kernel@stlinux.com, jason@lakedaemon.net
Subject: Re: [PATCH v2 2/8] irqchip: Supply new driver for STi based devices
Date: Thu, 27 Nov 2014 09:02:55 +0000 [thread overview]
Message-ID: <20141127090255.GD4628@x1> (raw)
In-Reply-To: <2433040.4NqTrOMmEE@wuerfel>
On Tue, 25 Nov 2014, Arnd Bergmann wrote:
> On Tuesday 25 November 2014 16:24:59 Lee Jones wrote:
>
> > diff --git a/drivers/irqchip/Kconfig b/drivers/irqchip/Kconfig
> > index b21f12f..e502f15 100644
> > --- a/drivers/irqchip/Kconfig
> > +++ b/drivers/irqchip/Kconfig
> > @@ -93,6 +93,13 @@ config RENESAS_IRQC
> > bool
> > select IRQ_DOMAIN
> >
> > +config ST_IRQCHIP
> > + bool
> > + select REGMAP
> > + select MFD_SYSCON
> > + help
> > + Enables SysCfg Controlled IRQs on STi based platforms.
> > +
>
> I'm confused by the purpose of this code. It's apparently a driver
> in drivers/irqchip, the Kconfig symbol contains the string IRQCHIP,
> yet it doesn't actually register an irq_chip.
>
> Also, the name is a bit too generic, ST has lots of different irqchips,
> and this apparently isn't even one of them ;-)
Hmm... now you're going to ask me to remember who I had the
conversation with that alluded to this as the best location for this
driver. Unfortunately, I cannot. Can you think of a better place to
put it then?
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2014-11-27 9:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-25 16:24 [PATCH v2 0/8] irqchip: New driver for ST's SysCfg controlled IRQs Lee Jones
2014-11-25 16:24 ` [PATCH v2 1/8] dt: bindings: Supply shared ST IRQ defines Lee Jones
2014-11-25 16:24 ` [PATCH v2 2/8] irqchip: Supply new driver for STi based devices Lee Jones
[not found] ` <1416932705-16880-3-git-send-email-lee.jones-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2014-11-25 20:57 ` Arnd Bergmann
2014-11-27 9:02 ` Lee Jones [this message]
2014-11-27 9:15 ` Arnd Bergmann
2014-11-27 9:29 ` Lee Jones
2014-11-27 9:47 ` Arnd Bergmann
2014-11-27 9:55 ` Lee Jones
2014-11-25 16:25 ` [PATCH v2 3/8] irqchip: irq-st: Add documentation for STi based syscfg IRQs Lee Jones
2014-11-25 16:25 ` [PATCH v2 4/8] ARM: STi: STiH416: Enable Cortex-A9 PMU support Lee Jones
2014-11-25 16:25 ` [PATCH v2 5/8] ARM: STi: STiH416: Enable PMU IRQs Lee Jones
2014-11-25 16:25 ` [PATCH v2 6/8] ARM: STi: STiH407: Enable Cortex-A9 PMU support Lee Jones
2014-11-25 16:25 ` [PATCH v2 7/8] ARM: STi: STiH407: Enable PMU IRQs Lee Jones
2014-11-25 16:25 ` [PATCH v2 8/8] ARM: STI: Ensure requested STi's SysCfg Controlled IRQs are enabled at boot Lee Jones
[not found] ` <1416932705-16880-1-git-send-email-lee.jones-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2014-12-15 12:28 ` [PATCH v2 0/8] irqchip: New driver for ST's SysCfg controlled IRQs Lee Jones
2014-12-15 14:10 ` Jason Cooper
[not found] ` <20141215141050.GD967-u4khhh1J0LxI1Ri9qeTfzeTW4wlIGRCZ@public.gmane.org>
2014-12-15 14:42 ` Lee Jones
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=20141127090255.GD4628@x1 \
--to=lee.jones@linaro.org \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=jason@lakedaemon.net \
--cc=kernel@stlinux.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/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).