[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAOMZO5DYLZmz6f0yjrOpaL4B_wicq0ofrYpW6QqzNPEc0j407Q@mail.gmail.com>
Date: Fri, 18 Jun 2021 08:20:38 -0300
From: Fabio Estevam <festevam@...il.com>
To: Shengjiu Wang <shengjiu.wang@....com>
Cc: Timur Tabi <timur@...nel.org>,
Nicolin Chen <nicoleotsuka@...il.com>,
Xiubo Li <Xiubo.Lee@...il.com>,
Mark Brown <broonie@...nel.org>,
Jaroslav Kysela <perex@...ex.cz>,
Takashi Iwai <tiwai@...e.com>,
Linux-ALSA <alsa-devel@...a-project.org>,
linuxppc-dev@...ts.ozlabs.org,
linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] ASoC: fsl_xcvr: disable all interrupts when suspend happens
Hi Shengjiu,
On Fri, Jun 18, 2021 at 7:10 AM Shengjiu Wang <shengjiu.wang@....com> wrote:
>
> There is an unhandled interrupt after suspend, which cause endless
> interrupt when system resume, so system may hang.
>
> Disable all interrupts in runtime suspend callback to avoid above
> issue.
Fixe tag?
> + ret = regmap_update_bits(xcvr->regmap, FSL_XCVR_EXT_IER0,
> + FSL_XCVR_IRQ_EARC_ALL, 0);
> + if (ret < 0)
> + dev_err(dev, "Failed to clear IER0: %d\n", ret);
> +
The operations in _suspend() are usually balanced with the ones in _resume().
Shouldn't you enable the interrupts in resume() then?
I see that the interrupts are currently enabled inside fsl_xcvr_prepare().
Powered by blists - more mailing lists