[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <161159774049.2212.2964424673309683521.b4-ty@kernel.org>
Date: Mon, 25 Jan 2021 18:02:20 +0000
From: Mark Brown <broonie@...nel.org>
To: Dmitry Osipenko <digetx@...il.com>,
Sameer Pujar <spujar@...dia.com>,
Takashi Iwai <tiwai@...e.com>,
Peter Geis <pgwipeout@...il.com>,
Matt Merhar <mattmerhar@...tonmail.com>,
Jonathan Hunter <jonathanh@...dia.com>,
Nicolas Chauvet <kwizart@...il.com>,
Jaroslav Kysela <perex@...ex.cz>,
Thierry Reding <thierry.reding@...il.com>
Cc: alsa-devel@...a-project.org, linux-kernel@...r.kernel.org,
linux-tegra@...r.kernel.org
Subject: Re: (subset) [PATCH v3 0/6] Clock and reset improvements for Tegra ALSA drivers
On Wed, 20 Jan 2021 03:31:48 +0300, Dmitry Osipenko wrote:
> This series improves the handling of clock and reset controls of
> NVIDA Tegra ALSA drivers. Tegra HDA and AHUB drivers aren't handling
> resets properly, which needs to be fixed in order to unblock other patches
> related to fixes of the reset controller driver since HDA/AHUB are bound
> to fail once reset controller driver will be corrected. In particular ALSA
> drivers are relying on implicit de-assertion of resets which is done by the
> tegra-clk driver. It's not the business of the clk driver to touch resets
> and we need to fix this because it breaks reset/clk programming sequences
> of other Tegra drivers.
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[4/6] ASoC: tegra: ahub: Add missing resets
commit: 24a41a38dd2df065ee942221c2fae5e314770865
[5/6] ASoC: tegra: ahub: Use clk_bulk helpers
commit: 6d8ac9b1dd2f138f4aa39008994600f561eeede8
[6/6] ASoC: tegra: ahub: Reset hardware properly
commit: ed9ce1ed2239909c23d48c723c6549417c476246
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