[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <160676019500.54241.11589384467836552465.b4-ty@kernel.org>
Date: Mon, 30 Nov 2020 18:16:35 +0000
From: Mark Brown <broonie@...nel.org>
To: vkoul@...nel.org, Bard Liao <yung-chuan.liao@...ux.intel.com>,
alsa-devel@...a-project.org
Cc: gregkh@...uxfoundation.org, tiwai@...e.de, jank@...ence.com,
vinod.koul@...aro.org, srinivas.kandagatla@...aro.org,
bard.liao@...el.com, pierre-louis.bossart@...ux.intel.com,
linux-kernel@...r.kernel.org, ranjani.sridharan@...ux.intel.com,
rander.wang@...ux.intel.com, hui.wang@...onical.com,
mengdong.lin@...el.com, sanyog.r.kale@...el.com
Subject: Re: [PATCH 0/5] regmap/SoundWire/ASoC: Add SoundWire SDCA support
On Wed, 4 Nov 2020 01:22:21 +0800, Bard Liao wrote:
> The MIPI SoundWire Device Class standard will define audio functionality
> beyond the scope of the existing SoundWire 1.2 standard, which is limited
> to the bus and interface.
>
> The description is inspired by the USB Audio Class, with "functions",
> "entities", "control selectors", "audio clusters". The main difference
> with the USB Audio class is that the devices are typically on a motherboard
> and descriptors stored in platform firmware instead of being retrieved
> from the device.
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.git for-next
Thanks!
[1/3] ASoC/SoundWire: rt715-sdca: First version of rt715 sdw sdca codec driver
commit: 6f4a038b99677f4db737841b81b9d45ed4b54966
[2/3] ASoC/SoundWire: rt1316: Add RT1316 SDCA vendor-specific driver
(no commit info)
[3/3] ASoC/SoundWire: rt711-sdca: Add RT711 SDCA vendor-specific driver
(no commit info)
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