linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Bard Liao <yung-chuan.liao@linux.intel.com>
Cc: alsa-devel@alsa-project.org, vkoul@kernel.org,
	vinod.koul@linaro.org, linux-kernel@vger.kernel.org,
	tiwai@suse.de, gregkh@linuxfoundation.org, jank@cadence.com,
	srinivas.kandagatla@linaro.org, rander.wang@linux.intel.com,
	ranjani.sridharan@linux.intel.com, hui.wang@canonical.com,
	pierre-louis.bossart@linux.intel.com, sanyog.r.kale@intel.com,
	bard.liao@intel.com
Subject: Re: [PATCH v2 2/5] regmap/SoundWire: sdw: add support for SoundWire 1.2 MBQ
Date: Tue, 1 Dec 2020 11:54:42 +0000	[thread overview]
Message-ID: <20201201115442.GA5239@sirena.org.uk> (raw)
In-Reply-To: <20201130144020.19757-3-yung-chuan.liao@linux.intel.com>

[-- Attachment #1: Type: text/plain, Size: 709 bytes --]

On Mon, Nov 30, 2020 at 10:40:17PM +0800, Bard Liao wrote:
> From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
> 
> The SoundWire 1.1 specification only allowed for reads and writes of
> bytes. The SoundWire 1.2 specification adds a new capability to
> transfer "Multi-Byte Quantities" (MBQ) across the bus. The transfers
> still happens one-byte-at-a-time, but the update is atomic.

Please do not submit new versions of already applied patches, please
submit incremental updates to the existing code.  Modifying existing
commits creates problems for other users building on top of those
commits so it's best practice to only change pubished git commits if
absolutely essential.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2020-12-01 11:56 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-30 14:40 [PATCH v2 0/5] regmap/SoundWire/ASoC: Add SoundWire SDCA support Bard Liao
2020-11-30 14:40 ` [PATCH v2 1/5] soundwire: SDCA: add helper macro to access controls Bard Liao
2020-11-30 14:40 ` [PATCH v2 2/5] regmap/SoundWire: sdw: add support for SoundWire 1.2 MBQ Bard Liao
2020-12-01 11:54   ` Mark Brown [this message]
2020-11-30 14:40 ` [PATCH v2 3/5] ASoC/SoundWire: rt715-sdca: First version of rt715 sdw sdca codec driver Bard Liao
2020-12-02 16:07   ` Mark Brown
2020-12-03  2:29     ` Liao, Bard
2020-11-30 14:40 ` [PATCH v2 4/5] ASoC/SoundWire: rt1316: Add RT1316 SDCA vendor-specific driver Bard Liao
2020-11-30 14:40 ` [PATCH v2 5/5] ASoC/SoundWire: rt711-sdca: Add RT711 " Bard Liao
2020-12-01  2:42 ` [PATCH v2 0/5] regmap/SoundWire/ASoC: Add SoundWire SDCA support Liao, Bard
2020-12-01  4:11   ` Vinod Koul
2020-12-01 14:35     ` Pierre-Louis Bossart
2020-12-01 14:53       ` Mark Brown
2020-12-02  7:14         ` Vinod Koul
2020-12-02 16:08           ` Mark Brown
2020-12-02 17:19 ` (subset) " 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=20201201115442.GA5239@sirena.org.uk \
    --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=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;
as well as URLs for NNTP newsgroup(s).