From: Arnd Bergmann <arnd@arndb.de>
To: linuxppc-dev@lists.ozlabs.org
Cc: Mark Brown <broonie@kernel.org>,
Lars-Peter Clausen <lars@metafoo.de>,
alsa-devel@alsa-project.org, Jiada Wang <jiada_wang@mentor.com>,
linux-kernel@vger.kernel.org, Timur Tabi <timur@tabi.org>,
lgirdwood@gmail.com, nicoleotsuka@gmail.com, tiwai@suse.de,
Li.Xiubo@freescale.com, Markus Pargmann <mpa@pengutronix.de>
Subject: Re: [alsa-devel] [PATCH] ASoC: fsl_ssi: free irq before irq_dispose_mapping()
Date: Mon, 01 Dec 2014 20:56:23 +0100 [thread overview]
Message-ID: <2547588.Qc4F2IfZke@wuerfel> (raw)
In-Reply-To: <20141201194147.GP7712@sirena.org.uk>
On Monday 01 December 2014 19:41:47 Mark Brown wrote:
> On Mon, Dec 01, 2014 at 08:39:51PM +0100, Lars-Peter Clausen wrote:
> > On 12/01/2014 07:48 PM, Timur Tabi wrote:
>
> > >A quick grep shows the following drivers that call both functions:
>
> > Most of these drivers will probably work fine without irq_of_parse_and_map().
>
> I'd also note that quite a few of these drivers look pretty legacy - a
> very large proportion are for old PowerPC hardware, though by no means
> all.
Right, from the times before we were using platform_device for probing
device tree based devices and they had to map the interrupt themselves.
Some of them like arch/powerpc/sysdev/fsl_pci.c seem fine, this one
is does not expect to ever destroy a device, and it only unmaps the
interrupt if request_irq fails. drivers/ata/pata_mpc52xx.c on the
other hand seems wrong in the same was as drivers/edac/mpc85xx_edac.c
and sound/soc/fsl/fsl_ssi.c.
All other drivers that call irq_of_parse_and_map and pass that into
devm_request_irq just never unmap, and their interrupts are already
mapped by the platform code, so I think it's not even a leak.
Arnd
WARNING: multiple messages have this Message-ID (diff)
From: Arnd Bergmann <arnd@arndb.de>
To: linuxppc-dev@lists.ozlabs.org
Cc: alsa-devel@alsa-project.org, Lars-Peter Clausen <lars@metafoo.de>,
lgirdwood@gmail.com, Jiada Wang <jiada_wang@mentor.com>,
Li.Xiubo@freescale.com, Timur Tabi <timur@tabi.org>,
linux-kernel@vger.kernel.org, nicoleotsuka@gmail.com,
tiwai@suse.de, Mark Brown <broonie@kernel.org>,
Markus Pargmann <mpa@pengutronix.de>
Subject: Re: [alsa-devel] [PATCH] ASoC: fsl_ssi: free irq before irq_dispose_mapping()
Date: Mon, 01 Dec 2014 20:56:23 +0100 [thread overview]
Message-ID: <2547588.Qc4F2IfZke@wuerfel> (raw)
In-Reply-To: <20141201194147.GP7712@sirena.org.uk>
On Monday 01 December 2014 19:41:47 Mark Brown wrote:
> On Mon, Dec 01, 2014 at 08:39:51PM +0100, Lars-Peter Clausen wrote:
> > On 12/01/2014 07:48 PM, Timur Tabi wrote:
>
> > >A quick grep shows the following drivers that call both functions:
>
> > Most of these drivers will probably work fine without irq_of_parse_and_map().
>
> I'd also note that quite a few of these drivers look pretty legacy - a
> very large proportion are for old PowerPC hardware, though by no means
> all.
Right, from the times before we were using platform_device for probing
device tree based devices and they had to map the interrupt themselves.
Some of them like arch/powerpc/sysdev/fsl_pci.c seem fine, this one
is does not expect to ever destroy a device, and it only unmaps the
interrupt if request_irq fails. drivers/ata/pata_mpc52xx.c on the
other hand seems wrong in the same was as drivers/edac/mpc85xx_edac.c
and sound/soc/fsl/fsl_ssi.c.
All other drivers that call irq_of_parse_and_map and pass that into
devm_request_irq just never unmap, and their interrupts are already
mapped by the platform code, so I think it's not even a leak.
Arnd
next prev parent reply other threads:[~2014-12-01 19:56 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-01 2:50 [PATCH] ASoC: fsl_ssi: free irq before irq_dispose_mapping() Jiada Wang
2014-12-01 2:50 ` Jiada Wang
2014-12-01 2:50 ` Jiada Wang
2014-12-01 6:50 ` Markus Pargmann
2014-12-01 6:50 ` Markus Pargmann
2014-12-01 6:50 ` Markus Pargmann
2014-12-01 16:49 ` Lars-Peter Clausen
2014-12-01 16:49 ` [alsa-devel] " Lars-Peter Clausen
2014-12-01 16:49 ` Lars-Peter Clausen
2014-12-01 16:51 ` Timur Tabi
2014-12-01 16:51 ` Timur Tabi
2014-12-01 16:59 ` Lars-Peter Clausen
2014-12-01 16:59 ` [alsa-devel] " Lars-Peter Clausen
2014-12-01 16:59 ` Lars-Peter Clausen
2014-12-01 18:48 ` Timur Tabi
2014-12-01 18:48 ` Timur Tabi
2014-12-01 19:39 ` Lars-Peter Clausen
2014-12-01 19:39 ` Lars-Peter Clausen
2014-12-01 19:41 ` Mark Brown
2014-12-01 19:41 ` Mark Brown
2014-12-01 19:56 ` Arnd Bergmann [this message]
2014-12-01 19:56 ` Arnd Bergmann
2014-12-01 19:59 ` Timur Tabi
2014-12-01 19:59 ` Timur Tabi
2014-12-01 20:01 ` Arnd Bergmann
2014-12-01 20:01 ` Arnd Bergmann
2014-12-01 20:11 ` Timur Tabi
2014-12-01 20:11 ` Timur Tabi
2014-12-01 20:30 ` Lars-Peter Clausen
2014-12-01 20:30 ` Lars-Peter Clausen
2014-12-01 20:40 ` Fabio Estevam
2014-12-01 20:40 ` Fabio Estevam
2014-12-01 20:42 ` Timur Tabi
2014-12-01 20:42 ` Timur Tabi
2014-12-01 21:03 ` Fabio Estevam
2014-12-01 21:03 ` Fabio Estevam
2014-12-01 20:16 ` Mark Brown
2014-12-01 20:16 ` Mark Brown
2014-12-01 19:24 ` Mark Brown
2014-12-01 19:24 ` [alsa-devel] " Mark Brown
2014-12-01 19:24 ` Mark Brown
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=2547588.Qc4F2IfZke@wuerfel \
--to=arnd@arndb.de \
--cc=Li.Xiubo@freescale.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=jiada_wang@mentor.com \
--cc=lars@metafoo.de \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpa@pengutronix.de \
--cc=nicoleotsuka@gmail.com \
--cc=timur@tabi.org \
--cc=tiwai@suse.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 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.