[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <159802798182.25503.9357316995968776171.b4-ty@kernel.org>
Date: Fri, 21 Aug 2020 17:40:02 +0100
From: Mark Brown <broonie@...nel.org>
To: alsa-devel@...a-project.org, Brent Lu <brent.lu@...el.com>
Cc: Daniel Stuart <daniel.stuart14@...il.com>,
Jie Yang <yang.jie@...ux.intel.com>,
Sam McNally <sammc@...omium.org>,
Kuninori Morimoto <kuninori.morimoto.gx@...esas.com>,
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
Takashi Iwai <tiwai@...e.com>,
Kai Vehmanen <kai.vehmanen@...ux.intel.com>,
Pierre-Louis Bossart <pierre-louis.bossart@...ux.intel.com>,
Yu-Hsuan Hsu <yuhsuan@...omium.org>,
linux-kernel@...r.kernel.org,
Damian van Soelen <dj.vsoelen@...il.com>,
Guennadi Liakhovetski <guennadi.liakhovetski@...ux.intel.com>,
Liam Girdwood <liam.r.girdwood@...ux.intel.com>,
Cezary Rojewski <cezary.rojewski@...el.com>,
Ranjani Sridharan <ranjani.sridharan@...ux.intel.com>
Subject: Re: [PATCH v3 0/2] Add period size constraint for Atom Chromebook
On Fri, 31 Jul 2020 20:26:03 +0800, Brent Lu wrote:
> Two different constraints are implemented: one is in platform's CPU
> DAI to enforce the period to be multiple of 1ms to align with firmware
> design. The other is in Atom Chromebook's machine driver to use 240 as
> period size which is selected by google.
>
>
> Changes since v1:
> -Add comma at the end of media_period_size array declaration.
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/1] ASoC: intel: atom: Add period size constraint
commit: 5e7820e369248f880767c4c4079b414529bc2125
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
Powered by blists - more mailing lists