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,
tiwai@suse.de, broonie@kernel.org,
pierre-louis.bossart@linux.intel.com, bard.liao@intel.com
Subject: [PATCH 0/3] ALSA/ASoC/SoundWire: Intel: update maximum number of links
Date: Fri, 16 Aug 2024 10:33:28 +0800 [thread overview]
Message-ID: <20240816023331.6565-1-yung-chuan.liao@linux.intel.com> (raw)
Intel new platforms can have up to 5 SoundWire links.
This series does not apply to SoundWire tree due to recent changes in
machine driver. Can we go via ASoC tree with Vinod's Acked-by tag?
Pierre-Louis Bossart (3):
ALSA/ASoC/SoundWire: Intel: use single definition for
SDW_INTEL_MAX_LINKS
soundwire: intel: increase maximum number of links
soundwire: intel: add probe-time check on link id
drivers/soundwire/intel.h | 7 +++++++
drivers/soundwire/intel_ace2x.c | 20 ++++++++++++++++++++
drivers/soundwire/intel_auxdevice.c | 14 ++++++++++++++
include/linux/soundwire/sdw_intel.h | 8 ++++++++
sound/hda/intel-sdw-acpi.c | 5 ++---
sound/soc/intel/boards/sof_sdw.c | 4 +++-
sound/soc/intel/boards/sof_sdw_common.h | 4 +---
sound/soc/intel/boards/sof_sdw_hdmi.c | 2 ++
8 files changed, 57 insertions(+), 7 deletions(-)
--
2.43.0
next reply other threads:[~2024-08-16 2:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-16 2:33 Bard Liao [this message]
2024-08-16 2:33 ` [PATCH 1/3] ALSA/ASoC/SoundWire: Intel: use single definition for SDW_INTEL_MAX_LINKS Bard Liao
2024-08-16 11:25 ` Mark Brown
2024-08-18 7:50 ` Takashi Iwai
2024-08-16 2:33 ` [PATCH 2/3] soundwire: intel: increase maximum number of links Bard Liao
2024-08-17 17:21 ` Vinod Koul
2024-08-16 2:33 ` [PATCH 3/3] soundwire: intel: add probe-time check on link id Bard Liao
2024-08-17 17:22 ` Vinod Koul
2024-08-20 12:44 ` [PATCH 0/3] ALSA/ASoC/SoundWire: Intel: update maximum number of links 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=20240816023331.6565-1-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.intel.com \
--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