The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Bard Liao <yung-chuan.liao@linux.intel.com>
To: linux-sound@vger.kernel.org, vkoul@kernel.org
Cc: vinod.koul@linaro.org, linux-kernel@vger.kernel.org,
	pierre-louis.bossart@linux.dev, peter.ujfalusi@linux.intel.com,
	bard.liao@intel.com
Subject: [PATCH 0/5] soundwire: add BRA properties
Date: Tue, 30 Jun 2026 20:48:20 +0800	[thread overview]
Message-ID: <20260630124825.2263243-1-yung-chuan.liao@linux.intel.com> (raw)

This series adds mipi-sdw-bra-mode-max-data-per-frame and
mipi-sdw-bra-mode-block-alignment properties support and fixes the
BRA_NumBytes[8] support in cadence_master driver.

Bard Liao (4):
  soundwire: cadence_master: add BRA_NumBytes[8] support
  soundwire: intel: handle Peripheral bra_block_alignment
  soundwire: get mipi-sdw-bra-mode-max-data-per-frame property
  soundwire: intel_ace2x: handle the max_data_per_frame property

Richard Fitzgerald (1):
  soundwire: Add bra_block_alignment property support

 drivers/soundwire/cadence_master.c | 35 +++++++++++++++++++++++++-----
 drivers/soundwire/cadence_master.h |  1 +
 drivers/soundwire/intel_ace2x.c    | 20 +++++++++++++++--
 drivers/soundwire/mipi_disco.c     |  6 +++++
 include/linux/soundwire/sdw.h      | 14 ++++++++++++
 5 files changed, 68 insertions(+), 8 deletions(-)

-- 
2.43.0


             reply	other threads:[~2026-06-30 12:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-30 12:48 Bard Liao [this message]
2026-06-30 12:48 ` [PATCH 1/5] soundwire: cadence_master: add BRA_NumBytes[8] support Bard Liao
2026-06-30 12:48 ` [PATCH 2/5] soundwire: Add bra_block_alignment property support Bard Liao
2026-06-30 12:48 ` [PATCH 3/5] soundwire: intel: handle Peripheral bra_block_alignment Bard Liao
2026-06-30 12:48 ` [PATCH 4/5] soundwire: get mipi-sdw-bra-mode-max-data-per-frame property Bard Liao
2026-06-30 12:48 ` [PATCH 5/5] soundwire: intel_ace2x: handle the max_data_per_frame property Bard Liao

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=20260630124825.2263243-1-yung-chuan.liao@linux.intel.com \
    --to=yung-chuan.liao@linux.intel.com \
    --cc=bard.liao@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=peter.ujfalusi@linux.intel.com \
    --cc=pierre-louis.bossart@linux.dev \
    --cc=vinod.koul@linaro.org \
    --cc=vkoul@kernel.org \
    /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