Enable class-D silence and clock detections
Subsystems (3)
PATCH 1/1 Enable class-D silence and clock detections
From: "derek.fang" <[email protected]>
Avoid noise under bypass boost mode.
--- sound/soc/codecs/rt1015.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
sound/soc/codecs/rt1015.c +1 -1
@@ -475,7 +475,7 @@ static int rt1015_bypass_boost_put(struct snd_kcontrol *kcontrol,snd_soc_component_write (component,RT1015_CLSD_INTERNAL9 ,0x0140 );snd_soc_component_write (component, -RT1015_GAT_BOOST ,0x00fe ); +RT1015_GAT_BOOST ,0x0efe );snd_soc_component_write (component,RT1015_PWR_STATE_CTRL ,0x000d );msleep (500 );
Signature · 1 line
2.7.4
Mark Brown
maintainerQuoted 3 lines · On Fri, May 29, 2020 at 07:05:10PM +0800, [email protected] wrote:
From: "derek.fang" <[email protected]>
Avoid noise under bypass boost mode.
Please submit patches using subject lines reflecting the style for the subsystem, this makes it easier for people to identify relevant patches. Look at what existing commits in the area you're changing are doing and make sure your subject lines visually resemble what they're doing. There's no need to resubmit to fix this alone.
A message that is not in the archive (sent off-list or not yet received): [email protected]
Mark Brown
maintainerQuoted 4 lines · Derek [方德義]
Quoted 2 lines
Please submit patches using subject lines reflecting the style for the subsystem, this makes it easier for people to identify relevant patches.
Sorry for the mistake. I will resend the patch.
It's OK, no need for this one - just please bear this in mind in future.
Mark Brown
maintainerQuoted 1 line · On Fri, 29 May 2020 19:05:10 +0800, [email protected] wrote:
Avoid noise under bypass boost mode.
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/1] ASoC: rt1015: Enable class-D silence and clock detections
commit: 2aec8ccc1a814ca41b70710e1960afd034d1e3ab
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