Message ID | 20230912113245.320159-1-hdegoede@redhat.com (mailing list archive) |
---|---|
Headers | show |
Series | ASoC: rt5640: Fix various IRQ handling issues | expand |
On Tue, 12 Sep 2023 13:32:39 +0200, Hans de Goede wrote: > The recent(ish) rt5640 changes to add HDA header jack-detect support > and the related suspend/resume handling fixes have introduced several > issues with IRQ handling on boards not using the HDA header jack-detect > support. > > This series fixes these issues, see the individual commit messages > for details. > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next Thanks! [1/6] ASoC: rt5640: Revert "Fix sleep in atomic context" commit: fa6a0c0c1dd53b3949ca56bf7213648dfd6a62ee [2/6] ASoC: rt5640: Fix sleep in atomic context commit: df7d595f6bd9dc96cc275cc4b0f313fcfa423c58 [3/6] ASoC: rt5640: Do not disable/enable IRQ twice on suspend/resume commit: 786120ebb649b166021f0212250e8627e53d068a [4/6] ASoC: rt5640: Enable the IRQ on resume after configuring jack-detect commit: b5e85e535551bf82242aa5896e14a136ed3c156d [5/6] ASoC: rt5640: Fix IRQ not being free-ed for HDA jack detect mode commit: 8c8bf3df6b7c0ed1c4dd373b23eb0ce13a63f452 [6/6] ASoC: rt5640: Only cancel jack-detect work on suspend if active commit: 8fc7cc507d61fc655172836c74fb7fcc8b7a978b 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