From: Arnd Bergmann <arnd@arndb.de>
To: Marc Zyngier <marc.zyngier@arm.com>
Cc: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Tony Lindgren <tony@atomide.com>,
Russell King - ARM Linux <linux@arm.linux.org.uk>,
Jason Cooper <jason@lakedaemon.net>, Felipe Balbi <balbi@ti.com>,
Yingjoe Chen <yingjoe.chen@mediatek.com>,
Thomas Gleixner <tglx@linutronix.de>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: Regression with legacy IRQ numbers caused by 9a1091ef0017
Date: Thu, 15 Jan 2015 17:37:50 +0100 [thread overview]
Message-ID: <20923934.GLG5LeSnXd@wuerfel> (raw)
In-Reply-To: <87wq4ogl48.fsf@approximate.cambridge.arm.com>
On Thursday 15 January 2015 14:43:35 Marc Zyngier wrote:
> On Thu, Jan 15 2015 at 2:27:56 pm GMT, Arnd Bergmann <arnd@arndb.de> wrote:
> > On Thursday 15 January 2015 13:42:57 Marc Zyngier wrote:
> >> Of course, this is in no way a proper fix, but I suppose the OMAP DT is
> >> still missing a few bits...
> >
> > I must be missing something here, but all the interrupts are listed
> > correctly in the DT, so what is the omap_hwmod_irq_info actually
> > achieving on omap4 and omap5?
> >
> > Would it work if we just remove the incorrect copy of the resource
> > and use the one that comes from DT?
>
> By the look of it, omap_hwmod_irq_info serves multiple purposes:
> - low level configuration (pads, probably more stuff)
> - interrupt description for some drivers, using resources.
>
> It should be fairly easy to do the latter, but the former looks more
> tricky (it would push the pad configuration down to the drivers, which
> is avoided at the moment).
>
> Probably there is a workable strategy, but my knowledge about OMAP is
> close to *nothing*...
I don't know much about OMAP either so maybe it's better to let someone
comment who understands this better. ;-)
A number of commits have in the past removed omap_hwmod_irq_info entries
here, the last one was 09182ab11b49 ("ARM: OMAP4: hwmod data: Remove
irq entries from mcspi, mmc hwmods").
>From what I can tell, we could drop the omap44xx_dss_dispc_irqs,
omap44xx_dss_dsi1_irqs, omap44xx_dss_dsi2_irqs, and omap44xx_dss_hdmi_irqs
in the samem way, after this data got added to DT as part of
cfe86fcf2d0079f03 ("ARM: omap4.dtsi: add omapdss information").
Unfortunately, the omap-dma driver once again gets in the way, since
there are still users of this that are not converted to use dmaengine,
and unlike the proper driver (drivers/dma/omap-dma.c), the legacy
driver (arch/arm/mach-omap2/dma.c) does not get probed from DT and
instead gets the wrong irq numbers from hwmod now.
Arnd
WARNING: multiple messages have this Message-ID (diff)
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: Regression with legacy IRQ numbers caused by 9a1091ef0017
Date: Thu, 15 Jan 2015 17:37:50 +0100 [thread overview]
Message-ID: <20923934.GLG5LeSnXd@wuerfel> (raw)
In-Reply-To: <87wq4ogl48.fsf@approximate.cambridge.arm.com>
On Thursday 15 January 2015 14:43:35 Marc Zyngier wrote:
> On Thu, Jan 15 2015 at 2:27:56 pm GMT, Arnd Bergmann <arnd@arndb.de> wrote:
> > On Thursday 15 January 2015 13:42:57 Marc Zyngier wrote:
> >> Of course, this is in no way a proper fix, but I suppose the OMAP DT is
> >> still missing a few bits...
> >
> > I must be missing something here, but all the interrupts are listed
> > correctly in the DT, so what is the omap_hwmod_irq_info actually
> > achieving on omap4 and omap5?
> >
> > Would it work if we just remove the incorrect copy of the resource
> > and use the one that comes from DT?
>
> By the look of it, omap_hwmod_irq_info serves multiple purposes:
> - low level configuration (pads, probably more stuff)
> - interrupt description for some drivers, using resources.
>
> It should be fairly easy to do the latter, but the former looks more
> tricky (it would push the pad configuration down to the drivers, which
> is avoided at the moment).
>
> Probably there is a workable strategy, but my knowledge about OMAP is
> close to *nothing*...
I don't know much about OMAP either so maybe it's better to let someone
comment who understands this better. ;-)
A number of commits have in the past removed omap_hwmod_irq_info entries
here, the last one was 09182ab11b49 ("ARM: OMAP4: hwmod data: Remove
irq entries from mcspi, mmc hwmods").
>From what I can tell, we could drop the omap44xx_dss_dispc_irqs,
omap44xx_dss_dsi1_irqs, omap44xx_dss_dsi2_irqs, and omap44xx_dss_hdmi_irqs
in the samem way, after this data got added to DT as part of
cfe86fcf2d0079f03 ("ARM: omap4.dtsi: add omapdss information").
Unfortunately, the omap-dma driver once again gets in the way, since
there are still users of this that are not converted to use dmaengine,
and unlike the proper driver (drivers/dma/omap-dma.c), the legacy
driver (arch/arm/mach-omap2/dma.c) does not get probed from DT and
instead gets the wrong irq numbers from hwmod now.
Arnd
next prev parent reply other threads:[~2015-01-15 16:38 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-14 22:14 Regression with legacy IRQ numbers caused by 9a1091ef0017 Tony Lindgren
2015-01-14 22:14 ` Tony Lindgren
2015-01-15 10:50 ` Russell King - ARM Linux
2015-01-15 10:50 ` Russell King - ARM Linux
2015-01-15 15:28 ` Tony Lindgren
2015-01-15 15:28 ` Tony Lindgren
2015-01-15 17:19 ` Russell King - ARM Linux
2015-01-15 17:19 ` Russell King - ARM Linux
2015-01-16 16:21 ` Tony Lindgren
2015-01-16 16:21 ` Tony Lindgren
2015-01-16 16:30 ` Russell King - ARM Linux
2015-01-16 16:30 ` Russell King - ARM Linux
2015-01-16 16:41 ` Tony Lindgren
2015-01-16 16:41 ` Tony Lindgren
2015-01-16 16:46 ` Felipe Balbi
2015-01-16 16:46 ` Felipe Balbi
2015-01-16 17:22 ` Russell King - ARM Linux
2015-01-16 17:22 ` Russell King - ARM Linux
2015-01-16 17:29 ` Tony Lindgren
2015-01-16 17:29 ` Tony Lindgren
2015-01-16 22:52 ` Tony Lindgren
2015-01-16 22:52 ` Tony Lindgren
2015-01-16 22:57 ` Russell King - ARM Linux
2015-01-16 22:57 ` Russell King - ARM Linux
2015-01-16 22:57 ` Tony Lindgren
2015-01-16 22:57 ` Tony Lindgren
2015-01-15 13:42 ` Marc Zyngier
2015-01-15 13:42 ` Marc Zyngier
2015-01-15 14:27 ` Arnd Bergmann
2015-01-15 14:27 ` Arnd Bergmann
2015-01-15 14:43 ` Marc Zyngier
2015-01-15 14:43 ` Marc Zyngier
2015-01-15 15:37 ` Tony Lindgren
2015-01-15 15:37 ` Tony Lindgren
2015-01-16 16:56 ` Arnd Bergmann
2015-01-16 16:56 ` Arnd Bergmann
2015-01-16 17:23 ` Marc Zyngier
2015-01-16 17:23 ` Marc Zyngier
2015-01-17 0:48 ` Simon Horman
2015-01-17 0:48 ` Simon Horman
2015-01-15 16:37 ` Arnd Bergmann [this message]
2015-01-15 16:37 ` 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=20923934.GLG5LeSnXd@wuerfel \
--to=arnd@arndb.de \
--cc=balbi@ti.com \
--cc=jason@lakedaemon.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=marc.zyngier@arm.com \
--cc=tglx@linutronix.de \
--cc=tony@atomide.com \
--cc=yingjoe.chen@mediatek.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.