From: Mark Brown <firstname.lastname@example.org> To: Kyle Russell <email@example.com> Cc: firstname.lastname@example.org, email@example.com, Haojian Zhuang <firstname.lastname@example.org>, Liam Girdwood <email@example.com>, firstname.lastname@example.org, Daniel Mack <email@example.com>, Takashi Iwai <firstname.lastname@example.org>, Robert Jarzmik <email@example.com>, firstname.lastname@example.org Subject: Re: [PATCH] ASoC: mmp-sspa: set phase two word length register Date: Fri, 20 Nov 2020 21:29:22 +0000 [thread overview] Message-ID: <email@example.com> (raw) In-Reply-To: <firstname.lastname@example.org> On Wed, 18 Nov 2020 22:41:06 -0500, Kyle Russell wrote: > If hw params enables dual phase transmission, then the word length for > the second phase should be set to match the sample format instead of > remaining at the reset default. This matches the configuration already > being done for the first phase. > > This driver already sets the phase two sample size, so this should complete > the phase two configuration. Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next Thanks! [1/1] ASoC: mmp-sspa: set phase two word length register commit: 82d1aeb8a40740cf4208ce864cbcaa5e8bbabf4e 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
prev parent reply other threads:[~2020-11-20 21:30 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-11-19 3:41 Kyle Russell 2020-11-20 21:29 ` Mark Brown [this message]
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: [PATCH] ASoC: mmp-sspa: set phase two word length register' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).