[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200615134119.GB3321@kozik-lap>
Date: Mon, 15 Jun 2020 15:41:19 +0200
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Vladimir Oltean <olteanv@...il.com>
Cc: Mark Brown <broonie@...nel.org>,
Marc Kleine-Budde <mkl@...gutronix.de>,
Thomas Gleixner <tglx@...utronix.de>,
Vladimir Oltean <vladimir.oltean@....com>,
linux-spi <linux-spi@...r.kernel.org>,
lkml <linux-kernel@...r.kernel.org>,
Wolfram Sang <wsa@...nel.org>, stable@...r.kernel.org,
Pengutronix Kernel Team <kernel@...gutronix.de>
Subject: Re: [PATCH v2 1/3] spi: spi-fsl-dspi: Fix external abort on
interrupt in exit paths
On Mon, Jun 15, 2020 at 04:12:28PM +0300, Vladimir Oltean wrote:
> On Mon, 15 Jun 2020 at 16:10, Mark Brown <broonie@...nel.org> wrote:
>
> >
> > It's a bit unusual to need to actually free the IRQ over suspend -
> > what's driving that requirement here?
>
> clk_disable_unprepare(dspi->clk); is driving the requirement - same as
> in dspi_remove case, the module will fault when its registers are
> accessed without a clock.
In few cases when I have shared interrupt in different drivers, they
were just disabling it during suspend. Why it has to be freed?
Best regards,
Krzysztof
Powered by blists - more mailing lists