linux-kernel - Re: [PATCH 0/1] sound: add quirk for Huawei D15

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] [thread-next>] [day] [month] [year] [list]

Message-Id: <164519450743.1836505.3912962145996830275.b4-ty@kernel.org>
Date:   Fri, 18 Feb 2022 14:28:27 +0000
From:   Mark Brown <broonie@...nel.org>
To:     Mauro Carvalho Chehab <mchehab@...nel.org>,
        Pierre-Louis Bossart <pierre-louis.bossart@...ux.intel.com>
Cc:     alsa-devel@...a-project.org, Jaroslav Kysela <perex@...ex.cz>,
        linux-kernel@...r.kernel.org,
        Bard Liao <yung-chuan.liao@...ux.intel.com>,
        Huajun Li <huajun.li@...el.com>, tiwai@...e.de,
        Takashi Iwai <tiwai@...e.com>,
        Kai Vehmanen <kai.vehmanen@...ux.intel.com>
Subject: Re: [PATCH 0/1] sound: add quirk for Huawei D15

On Fri, 24 Dec 2021 14:09:48 +0100, Mauro Carvalho Chehab wrote:
> Based on my tests, Huawei D15 (Intel) uses SSP0 on es8336.
> 
> Add a quirk for it.
> 
> Please notice that, currently, only the internal speaker is working.
> The topology for the internal microphone and for the headphones
> is wrong. Enabling/disabling the other two quirks (GPIO and/or DMIC)
> doesn't cause any audible results, nor change the devices listed
> on pavucontrol (tested with pipewire-pulse).
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: Intel: sof_es8336: add quirk for Huawei D15 2021
      commit: ce6a70bfce21bb4edb7c0f29ecfb0522fa34ab71

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