[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <173634312327.36797.11001679317293209356.b4-ty@kernel.org>
Date: Wed, 08 Jan 2025 13:32:03 +0000
From: Mark Brown <broonie@...nel.org>
To: vkoul@...nel.org, oder_chiou@...ltek.com,
Charles Keepax <ckeepax@...nsource.cirrus.com>
Cc: jack.yu@...ltek.com, shumingf@...ltek.com, lgirdwood@...il.com,
peter.ujfalusi@...ux.intel.com, yung-chuan.liao@...ux.intel.com,
sanyog.r.kale@...el.com, pierre-louis.bossart@...ux.dev,
linux-sound@...r.kernel.org, linux-kernel@...r.kernel.org,
patches@...nsource.cirrus.com
Subject: Re: (subset) [PATCH 0/5] Expand SoundWire MBQ register map support
On Tue, 17 Dec 2024 13:59:16 +0000, Charles Keepax wrote:
> The current SDCA MBQ (Multi-Byte Quantities) register map only
> supports 16-bit types, add support for more sizes and then update
> the rt722 driver to use the new support. We also add support for
> the deferring feature of MBQs to allow hardware to indicate it is
> not currently ready to service a read/write.
>
> Afraid I don't have hardware to test the rt722 change so it is
> only build tested, but I thought it good to include a change to
> demonstrate the new features in use.
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.git for-next
Thanks!
[1/5] soundwire: SDCA: Add additional SDCA address macros
commit: 7b16e60b31202254c62a29f5c709ffb42684b6f9
[2/5] ASoC: SDCA: Update list of entity_0 controls
commit: b21468e83b787ab31aa9df8f429d2ca61def0cc9
[3/5] regmap: sdw-mbq: Add support for further MBQ register sizes
commit: fdd9ef3dce98e035d21c17fac587cb6e3c7706fd
[4/5] regmap: sdw-mbq: Add support for SDCA deferred controls
commit: 5bc493bf0c37c157bf2eb364e55a1c6f8bc43a69
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