From: Arnd Bergmann <arnd@arndb.de>
To: linux-arm-kernel@lists.infradead.org
Cc: Mark Brown <broonie@kernel.org>,
linux-samsung-soc@vger.kernel.org, padma.v@samsung.com,
dmitry.torokhov@gmail.com,
Maurus Cuelenaere <mcuelenaere@gmail.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Tomasz Figa <tomasz.figa@gmail.com>,
cw00.choi@samsung.com, Kukjin Kim <kgene@kernel.org>,
jic23@kernel.org, a.kesavan@samsung.com,
Charles Keepax <ckeepax@opensource.wolfsonmicro.com>,
ch.naveen@samsung.com
Subject: Re: [PATCH 05/10] ARM: s3c64xx: enable sparse IRQ support
Date: Sun, 22 Mar 2015 03:54:42 +0100 [thread overview]
Message-ID: <201503220354.43125.arnd@arndb.de> (raw)
In-Reply-To: <20150318000234.GU28806@sirena.org.uk>
On Wednesday 18 March 2015, Mark Brown wrote:
> On Sun, Mar 08, 2015 at 10:42:59PM +0100, Arnd Bergmann wrote:
> > diff --git a/arch/arm/mach-s3c64xx/mach-crag6410.c b/arch/arm/mach-s3c64xx/mach-crag6410.c
> > index f395a5617142..cbe353a5450e 100644
> > --- a/arch/arm/mach-s3c64xx/mach-crag6410.c
> > +++ b/arch/arm/mach-s3c64xx/mach-crag6410.c
> > @@ -855,7 +855,7 @@ static void __init crag6410_machine_init(void)
> > MACHINE_START(WLF_CRAGG_6410, "Wolfson Cragganmore 6410")
> > /* Maintainer: Mark Brown <broonie@opensource.wolfsonmicro.com> */
> > .atag_offset = 0x100,
> > - .nr_irqs = S3C64XX_NR_IRQS + 160,
> > + .nr_irqs = S3C64XX_NR_IRQS,
> > .init_irq = s3c6410_init_irq,
> > .map_io = crag6410_map_io,
> > .init_machine = crag6410_machine_init,
>
> > The samsung-gpio driver does not allocate irq descriptors for itself
> > though, otherwise we could make the S3C64XX_NR_IRQS number smaller.
>
> That's not the only thing, I'm still seeing an issue even with the
> change above. The VICs are also complaining about preallocated
> descriptors, but they just assume the descriptors were preallocated and
> carry on happily.
Yes, that is the behavior I expected to see. The VIC driver would be
fine in theory with allocating the descriptors dynamically, but
the secondary irqchip (s3c_irq_eint) would need significant changes.
IIRC, another problem is the way that the first NR_IRQS_LEGACY interrupts
are always preallocated, but would not need to, once we fix the eint.
Arnd
WARNING: multiple messages have this Message-ID (diff)
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 05/10] ARM: s3c64xx: enable sparse IRQ support
Date: Sun, 22 Mar 2015 03:54:42 +0100 [thread overview]
Message-ID: <201503220354.43125.arnd@arndb.de> (raw)
In-Reply-To: <20150318000234.GU28806@sirena.org.uk>
On Wednesday 18 March 2015, Mark Brown wrote:
> On Sun, Mar 08, 2015 at 10:42:59PM +0100, Arnd Bergmann wrote:
> > diff --git a/arch/arm/mach-s3c64xx/mach-crag6410.c b/arch/arm/mach-s3c64xx/mach-crag6410.c
> > index f395a5617142..cbe353a5450e 100644
> > --- a/arch/arm/mach-s3c64xx/mach-crag6410.c
> > +++ b/arch/arm/mach-s3c64xx/mach-crag6410.c
> > @@ -855,7 +855,7 @@ static void __init crag6410_machine_init(void)
> > MACHINE_START(WLF_CRAGG_6410, "Wolfson Cragganmore 6410")
> > /* Maintainer: Mark Brown <broonie@opensource.wolfsonmicro.com> */
> > .atag_offset = 0x100,
> > - .nr_irqs = S3C64XX_NR_IRQS + 160,
> > + .nr_irqs = S3C64XX_NR_IRQS,
> > .init_irq = s3c6410_init_irq,
> > .map_io = crag6410_map_io,
> > .init_machine = crag6410_machine_init,
>
> > The samsung-gpio driver does not allocate irq descriptors for itself
> > though, otherwise we could make the S3C64XX_NR_IRQS number smaller.
>
> That's not the only thing, I'm still seeing an issue even with the
> change above. The VICs are also complaining about preallocated
> descriptors, but they just assume the descriptors were preallocated and
> carry on happily.
Yes, that is the behavior I expected to see. The VIC driver would be
fine in theory with allocating the descriptors dynamically, but
the secondary irqchip (s3c_irq_eint) would need significant changes.
IIRC, another problem is the way that the first NR_IRQS_LEGACY interrupts
are always preallocated, but would not need to, once we fix the eint.
Arnd
next prev parent reply other threads:[~2015-03-22 2:55 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-02 12:35 [PATCH 00/10] ARM: s3c64xx multiplatform, help needed Arnd Bergmann
2015-03-02 12:35 ` Arnd Bergmann
2015-03-02 12:35 ` [PATCH 01/10] Input: s3c2410_ts: fix S3C_ADC dependency Arnd Bergmann
2015-03-02 12:35 ` Arnd Bergmann
2015-03-04 23:05 ` Dmitry Torokhov
2015-03-04 23:05 ` Dmitry Torokhov
2015-03-02 12:35 ` [PATCH 02/10] ASoC: samsung/smartq: use dynamic registration Arnd Bergmann
2015-03-02 12:35 ` Arnd Bergmann
2015-03-03 14:14 ` Mark Brown
2015-03-03 14:14 ` Mark Brown
2015-03-02 12:35 ` [PATCH 03/10] gpio: samsung: move gpio-samsung driver back to platform code Arnd Bergmann
2015-03-02 12:35 ` Arnd Bergmann
2015-03-02 12:35 ` [PATCH 04/10] ARM: s3c64xx: prepare initcalls for multiplatform Arnd Bergmann
2015-03-02 12:35 ` Arnd Bergmann
2015-03-02 12:35 ` [PATCH 05/10] ARM: s3c64xx: enable sparse IRQ support Arnd Bergmann
2015-03-02 12:35 ` Arnd Bergmann
2015-03-06 17:43 ` Charles Keepax
2015-03-06 17:43 ` Charles Keepax
2015-03-08 18:56 ` Mark Brown
2015-03-08 18:56 ` Mark Brown
2015-03-08 21:42 ` Arnd Bergmann
2015-03-08 21:42 ` Arnd Bergmann
2015-03-18 0:02 ` Mark Brown
2015-03-18 0:02 ` Mark Brown
2015-03-21 16:38 ` Charles Keepax
2015-03-21 16:38 ` Charles Keepax
2015-03-21 18:22 ` Mark Brown
2015-03-21 18:22 ` Mark Brown
2015-03-22 2:54 ` Arnd Bergmann [this message]
2015-03-22 2:54 ` Arnd Bergmann
2015-03-02 12:35 ` [PATCH 06/10] iio: exynos-adc: add experimental touchscreen support Arnd Bergmann
2015-03-02 12:35 ` Arnd Bergmann
2015-03-04 23:10 ` Dmitry Torokhov
2015-03-04 23:10 ` Dmitry Torokhov
2015-03-12 17:01 ` Arnd Bergmann
2015-03-12 17:01 ` Arnd Bergmann
2015-03-02 12:36 ` [PATCH 07/10] ARM: s3c64xx: use new adc/touchscreen driver Arnd Bergmann
2015-03-02 12:36 ` Arnd Bergmann
2015-03-02 12:36 ` [PATCH 08/10] ARM: s3c64xx: use common debug-ll implementation Arnd Bergmann
2015-03-02 12:36 ` Arnd Bergmann
2015-03-02 12:36 ` [PATCH 09/10] ARM: s3c64xx: multiplatform support Arnd Bergmann
2015-03-02 12:36 ` Arnd Bergmann
2015-03-02 12:36 ` [PATCH 10/10] ARM: s3c64xx: allow building without board support Arnd Bergmann
2015-03-02 12:36 ` Arnd Bergmann
2015-03-21 17:17 ` Charles Keepax
2015-03-21 17:17 ` Charles Keepax
2015-03-02 16:17 ` [PATCH 00/10] ARM: s3c64xx multiplatform, help needed Mark Brown
2015-03-02 16:17 ` Mark Brown
2015-03-02 18:03 ` Charles Keepax
2015-03-02 18:03 ` Charles Keepax
2015-03-02 16:53 ` Tomasz Figa
2015-03-02 16:53 ` Tomasz Figa
2015-03-02 19:04 ` Kukjin Kim
2015-03-02 19:04 ` Kukjin Kim
2015-03-02 17:37 ` Dmitry Torokhov
2015-03-02 17:37 ` Dmitry Torokhov
2015-03-02 18:14 ` Vasily Khoruzhick
2015-03-02 18:14 ` Vasily Khoruzhick
2015-03-02 20:48 ` Arnd Bergmann
2015-03-02 20:48 ` Arnd Bergmann
-- strict thread matches above, loose matches on Subject: below --
2015-11-25 16:06 [PATCH 00/10] ARM: s3c64xx multiplatform Arnd Bergmann
2015-11-25 16:06 ` [PATCH 05/10] ARM: s3c64xx: enable sparse IRQ support Arnd Bergmann
2015-11-25 16:06 ` Arnd Bergmann
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=201503220354.43125.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=a.kesavan@samsung.com \
--cc=broonie@kernel.org \
--cc=ch.naveen@samsung.com \
--cc=ckeepax@opensource.wolfsonmicro.com \
--cc=cw00.choi@samsung.com \
--cc=dmitry.torokhov@gmail.com \
--cc=jic23@kernel.org \
--cc=kgene@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=mcuelenaere@gmail.com \
--cc=padma.v@samsung.com \
--cc=tomasz.figa@gmail.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 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.