linux-kernel - Re: (subset) [PATCH v2 0/6] Expand SoundWire MBQ register map support

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <173875946575.32457.11587009893936906812.b4-ty@kernel.org>
Date: Wed, 05 Feb 2025 12:44:25 +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 v2 0/6] Expand SoundWire MBQ register map
 support

On Tue, 07 Jan 2025 15:44:02 +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/sound.git for-next

Thanks!

[5/6] ASoC: rt722-sdca: Add some missing readable registers
      commit: f9a5c4b6afc79073491acdab7f1e943ee3a19fbb
[6/6] ASoC: rt722-sdca: Make use of new expanded MBQ regmap
      commit: 299ce4beaf714abe76e3ad106f2e745748f693e9

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