Linux Sound subsystem development
 help / color / mirror / Atom feed
From: Bard Liao <yung-chuan.liao@linux.intel.com>
To: linux-sound@vger.kernel.org, broonie@kernel.org, tiwai@suse.de,
	vkoul@kernel.org
Cc: vinod.koul@linaro.org, linux-kernel@vger.kernel.org,
	pierre-louis.bossart@linux.dev, bard.liao@intel.com
Subject: [PATCH v4 08/16] soundwire: bus: add bpt_stream pointer
Date: Thu, 27 Feb 2025 22:06:07 +0800	[thread overview]
Message-ID: <20250227140615.8147-9-yung-chuan.liao@linux.intel.com> (raw)
In-Reply-To: <20250227140615.8147-1-yung-chuan.liao@linux.intel.com>

From: Pierre-Louis Bossart <pierre-louis.bossart@linux.dev>

Add a convenience pointer to the 'sdw_bus' structure. BPT is a
dedicated stream which will typically not be handled by DAIs or
dailinks. Since there's only one BPT stream per link, storing the
pointer at the link level seems rather natural.

Signed-off-by: Pierre-Louis Bossart <pierre-louis.bossart@linux.dev>
Signed-off-by: Bard Liao <yung-chuan.liao@linux.intel.com>
Reviewed-by: Péter Ujfalusi <peter.ujfalusi@linux.intel.com>
Reviewed-by: Liam Girdwood <liam.r.girdwood@intel.com>
Reviewed-by: Ranjani Sridharan <ranjani.sridharan@linux.intel.com>
---
 include/linux/soundwire/sdw.h | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/include/linux/soundwire/sdw.h b/include/linux/soundwire/sdw.h
index 69f3e700796d..2362f621d94c 100644
--- a/include/linux/soundwire/sdw.h
+++ b/include/linux/soundwire/sdw.h
@@ -979,6 +979,7 @@ struct sdw_stream_runtime {
  * @stream_refcount: number of streams currently using this bus
  * @btp_stream_refcount: number of BTP streams currently using this bus (should
  * be zero or one, multiple streams per link is not supported).
+ * @bpt_stream: pointer stored to handle BTP streams.
  * @ops: Master callback ops
  * @port_ops: Master port callback ops
  * @prop: Master properties
@@ -1017,6 +1018,7 @@ struct sdw_bus {
 	struct sdw_bus_params params;
 	int stream_refcount;
 	int bpt_stream_refcount;
+	struct sdw_stream_runtime *bpt_stream;
 	const struct sdw_master_ops *ops;
 	const struct sdw_master_port_ops *port_ops;
 	struct sdw_master_prop prop;
-- 
2.43.0


  parent reply	other threads:[~2025-02-27 14:07 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-27 14:05 [PATCH v4 00/16] SoundWire/ASoC: add SDW BPT/BRA support Bard Liao
2025-02-27 14:06 ` [PATCH v4 01/16] Documentation: driver: add SoundWire BRA description Bard Liao
2025-02-28  2:00   ` Bagas Sanjaya
2025-02-27 14:06 ` [PATCH v4 02/16] soundwire: cadence: add BTP support for DP0 Bard Liao
2025-02-27 14:06 ` [PATCH v4 03/16] soundwire: extend sdw_stream_type to BPT Bard Liao
2025-02-27 14:06 ` [PATCH v4 04/16] soundwire: stream: extend sdw_alloc_stream() to take 'type' parameter Bard Liao
2025-02-27 14:06 ` [PATCH v4 05/16] soundwire: stream: special-case the bus compute_params() routine Bard Liao
2025-02-27 14:06 ` [PATCH v4 06/16] soundwire: stream: reuse existing code for BPT stream Bard Liao
2025-02-27 14:06 ` [PATCH v4 07/16] soundwire: bus: add send_async/wait APIs for BPT protocol Bard Liao
2025-02-27 14:06 ` Bard Liao [this message]
2025-02-27 14:06 ` [PATCH v4 09/16] soundwire: cadence: add BTP/BRA helpers to format data Bard Liao
2025-02-27 14:06 ` [PATCH v4 10/16] soundwire: intel_auxdevice: add indirection for BPT send_async/wait Bard Liao
2025-02-27 14:06 ` [PATCH v4 11/16] ASoC: SOF: Intel: hda-sdw-bpt: add helpers for SoundWire BPT DMA Bard Liao
2025-02-27 14:06 ` [PATCH v4 12/16] soundwire: intel: add BPT context definition Bard Liao
2025-02-27 14:06 ` [PATCH v4 13/16] soundwire: intel_ace2x: add BPT send_async/wait callbacks Bard Liao
2025-02-27 14:06 ` [PATCH v4 14/16] ASoC: SOF: Intel: hda-sdw-bpt: add CHAIN_DMA support Bard Liao
2025-02-27 14:06 ` [PATCH v4 15/16] soundwire: debugfs: add interface for BPT/BRA transfers Bard Liao
2025-02-27 14:06 ` [PATCH v4 16/16] ASoC: rt711-sdca: add DP0 support Bard Liao
2025-03-03  1:50 ` [PATCH v4 00/16] SoundWire/ASoC: add SDW BPT/BRA support Shuming [范書銘]
2025-03-10  7:06 ` Vinod Koul

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=20250227140615.8147-9-yung-chuan.liao@linux.intel.com \
    --to=yung-chuan.liao@linux.intel.com \
    --cc=bard.liao@intel.com \
    --cc=broonie@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=pierre-louis.bossart@linux.dev \
    --cc=tiwai@suse.de \
    --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