From: Vinod Koul <vkoul@kernel.org>
To: Bard Liao <yung-chuan.liao@linux.intel.com>
Cc: linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org,
tiwai@suse.de, broonie@kernel.org,
pierre-louis.bossart@linux.intel.com, bard.liao@intel.com
Subject: Re: [PATCH 3/3] soundwire: intel: add probe-time check on link id
Date: Sat, 17 Aug 2024 22:52:13 +0530 [thread overview]
Message-ID: <ZsDcRWviIZPu0/DH@vaman> (raw)
In-Reply-To: <20240816023331.6565-4-yung-chuan.liao@linux.intel.com>
On 16-08-24, 10:33, Bard Liao wrote:
> From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
>
> In older platforms, the number of links was constant and hard-coded to
> 4. Newer platforms can have varying number of links, so we need to add
> a probe-time check to make sure the ACPI-reported information with
> _DSD properties is aligned with hardware capabilities reported in the
> SoundWire LCAP register.
Acked-by: Vinod Koul <vkoul@kernel.org>
--
~Vinod
next prev parent reply other threads:[~2024-08-17 17:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-16 2:33 [PATCH 0/3] ALSA/ASoC/SoundWire: Intel: update maximum number of links Bard Liao
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 [this message]
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=ZsDcRWviIZPu0/DH@vaman \
--to=vkoul@kernel.org \
--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=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