linux-kernel - Re: [PATCH] ASoC: amd: acp: Power on/off the speaker enable gpio pin based on DAPM callback.

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:   Fri, 24 Dec 2021 16:17:29 +0000
From:   Mark Brown <broonie@...nel.org>
To:     alsa-devel@...a-project.org,
        V sujith kumar Reddy <vsujithkumar.reddy@....com>
Cc:     open list <linux-kernel@...r.kernel.org>,
        Takashi Iwai <tiwai@...e.com>,
        Jaroslav Kysela <perex@...ex.cz>,
        Ajit Kumar Pandey <AjitKumar.Pandey@....com>,
        Sunil-kumar.Dommati@....com, Basavaraj.Hiregoudar@....com,
        Vijendar.Mukunda@....com, ajitkumar.pandey@....com,
        Arnd Bergmann <arnd@...db.de>,
        Liam Girdwood <lgirdwood@...il.com>, Alexander.Deucher@....com,
        Geert Uytterhoeven <geert+renesas@...der.be>
Subject: Re: [PATCH] ASoC: amd: acp: Power on/off the speaker enable gpio pin based on DAPM callback.

On Fri, 24 Dec 2021 20:30:43 +0530, V sujith kumar Reddy wrote:
> Configure the speaker gpio pin based on power sequence of the DAPM
> speaker events.
> Enable speaker after widget power up and Disable before widget  powerdown.
> 
> 

Applied to

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

Thanks!

[1/1] ASoC: amd: acp: Power on/off the speaker enable gpio pin based on DAPM callback.
      commit: 5c5f08f7fc0bee9a1bc3fbdcb7a21cfd0648ab14

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