mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: alsa-devel@alsa-project.org, vkoul@kernel.org,
	Bard Liao <yung-chuan.liao@linux.intel.com>
Cc: linux-kernel@vger.kernel.org, rander.wang@linux.intel.com,
	hui.wang@canonical.com, ranjani.sridharan@linux.intel.com,
	mengdong.lin@intel.com, pierre-louis.bossart@linux.intel.com,
	gregkh@linuxfoundation.org, srinivas.kandagatla@linaro.org,
	sanyog.r.kale@intel.com, bard.liao@intel.com, jank@cadence.com,
	tiwai@suse.de, vinod.koul@linaro.org
Subject: Re: [PATCH 0/5] regmap/SoundWire/ASoC: Add SoundWire SDCA support
Date: Thu, 26 Nov 2020 20:05:55 +0000	[thread overview]
Message-ID: <160642115073.9278.10273170290236043053.b4-ty@kernel.org> (raw)
In-Reply-To: <20201103172226.4278-1-yung-chuan.liao@linux.intel.com>

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/5] soundwire: SDCA: add helper macro to access controls
      commit: 07e21d4d96493fd0a8220ab134855253a34a9c84
[2/5] regmap/SoundWire: sdw: add support for SoundWire 1.2 MBQ
      commit: fb5103f9d6ce197b4d0b67b4e60e68470f5293d1
[3/5] ASoC/SoundWire: rt715-sdca: First version of rt715 sdw sdca codec driver
      commit: 6f4a038b99677f4db737841b81b9d45ed4b54966
[4/5] ASoC/SoundWire: rt1316: Add RT1316 SDCA vendor-specific driver
      (no commit info)
[5/5] 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

  parent reply	other threads:[~2020-11-26 20:07 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-03 17:22 Bard Liao
2020-11-03 17:22 ` [PATCH 1/5] soundwire: SDCA: add helper macro to access controls Bard Liao
2020-11-23 18:44   ` Mark Brown
2020-11-24  8:33   ` Vinod Koul
2020-11-03 17:22 ` [PATCH 2/5] regmap/SoundWire: sdw: add support for SoundWire 1.2 MBQ Bard Liao
2020-11-24  8:36   ` Vinod Koul
2020-11-03 17:22 ` [PATCH 3/5] ASoC/SoundWire: rt715-sdca: First version of rt715 sdw sdca codec driver Bard Liao
2020-11-03 17:22 ` [PATCH 4/5] ASoC/SoundWire: rt1316: Add RT1316 SDCA vendor-specific driver Bard Liao
2020-11-03 17:22 ` [PATCH 5/5] ASoC/SoundWire: rt711-sdca: Add RT711 " Bard Liao
2020-11-30 18:17   ` Mark Brown
2020-11-30 18:36     ` Pierre-Louis Bossart
2020-11-26 20:05 ` Mark Brown [this message]
2020-11-30 18:16 ` [PATCH 0/5] regmap/SoundWire/ASoC: Add SoundWire SDCA support Mark Brown

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=160642115073.9278.10273170290236043053.b4-ty@kernel.org \
    --to=broonie@kernel.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=bard.liao@intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hui.wang@canonical.com \
    --cc=jank@cadence.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mengdong.lin@intel.com \
    --cc=pierre-louis.bossart@linux.intel.com \
    --cc=rander.wang@linux.intel.com \
    --cc=ranjani.sridharan@linux.intel.com \
    --cc=sanyog.r.kale@intel.com \
    --cc=srinivas.kandagatla@linaro.org \
    --cc=tiwai@suse.de \
    --cc=vinod.koul@linaro.org \
    --cc=vkoul@kernel.org \
    --cc=yung-chuan.liao@linux.intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®