linux-kernel - Re: [PATCH] ASoC: SOF: amd: Fix for handling spurious interrupts from DSP

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Thu, 02 Feb 2023 17:36:46 +0000
From:   Mark Brown <broonie@...nel.org>
To:     alsa-devel@...a-project.org,
        V sujith kumar Reddy <Vsujithkumar.Reddy@....com>
Cc:     Vijendar.Mukunda@....com, Basavaraj.Hiregoudar@....com,
        Sunil-kumar.Dommati@....com, venkataprasad.potturu@....com,
        ssabakar@....com,
        Pierre-Louis Bossart <pierre-louis.bossart@...ux.intel.com>,
        Liam Girdwood <lgirdwood@...il.com>,
        Peter Ujfalusi <peter.ujfalusi@...ux.intel.com>,
        Bard Liao <yung-chuan.liao@...ux.intel.com>,
        Ranjani Sridharan <ranjani.sridharan@...ux.intel.com>,
        Kai Vehmanen <kai.vehmanen@...ux.intel.com>,
        Daniel Baluta <daniel.baluta@....com>,
        Jaroslav Kysela <perex@...ex.cz>,
        Takashi Iwai <tiwai@...e.com>,
        Ajit Kumar Pandey <AjitKumar.Pandey@....com>,
        Jiapeng Chong <jiapeng.chong@...ux.alibaba.com>,
        Ajye Huang <ajye_huang@...pal.corp-partner.google.com>,
        "moderated list:SOUND - SOUND OPEN FIRMWARE (SOF) DRIVERS" 
        <sound-open-firmware@...a-project.org>,
        open list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] ASoC: SOF: amd: Fix for handling spurious interrupts
 from DSP

On Fri, 03 Feb 2023 18:02:52 +0530, V sujith kumar Reddy wrote:
> As interrupts are Level-triggered,unless and until we deassert the register
> the interrupts are generated which causes spurious interrupts unhandled.
> 
> Now we deasserted the interrupt at top half which solved the below
> "nobody cared" warning.
> 
> warning reported in dmesg:
> 	irq 80: nobody cared (try booting with the "irqpoll" option)
> 	CPU: 5 PID: 2735 Comm: irq/80-AudioDSP
> 		Not tainted 5.15.86-15817-g4c19f3e06d49 #1 1bd3fd932cf58caacc95b0504d6ea1e3eab22289
> 	Hardware name: Google Skyrim/Skyrim, BIOS Google_Skyrim.15303.0.0 01/03/2023
> 	Call Trace:
> 	<IRQ>
> 	dump_stack_lvl+0x69/0x97
> 	 __report_bad_irq+0x3a/0xae
> 	note_interrupt+0x1a9/0x1e3
> 	handle_irq_event_percpu+0x4b/0x6e
> 	handle_irq_event+0x36/0x5b
> 	handle_fasteoi_irq+0xae/0x171
> 	 __common_interrupt+0x48/0xc4
> 	</IRQ>
> 
> [...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next

Thanks!

[1/1] ASoC: SOF: amd: Fix for handling spurious interrupts from DSP
      commit: 2e7c6652f9b86c01cbd4e988057a746a3a461969

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.

Thanks,
Mark