From: Takashi Iwai <tiwai@suse.de>
To: Stefan Binding <sbinding@opensource.cirrus.com>
Cc: Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
<alsa-devel@alsa-project.org>, <linux-kernel@vger.kernel.org>,
<patches@opensource.cirrus.com>
Subject: Re: [PATCH v1] ALSA: hda: cs35l41: Clarify support for CSC3551 without _DSD Properties
Date: Mon, 15 Aug 2022 18:12:52 +0200 [thread overview]
Message-ID: <87fshxzdrv.wl-tiwai@suse.de> (raw)
In-Reply-To: <20220815152844.462229-1-sbinding@opensource.cirrus.com>
On Mon, 15 Aug 2022 17:28:44 +0200,
Stefan Binding wrote:
>
> For devices which use HID CSC3551, correct ACPI _DSD properties are
> required to be able support those systems.
> Add error message to clarify this.
>
> Signed-off-by: Stefan Binding <sbinding@opensource.cirrus.com>
> ---
> sound/pci/hda/cs35l41_hda.c | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/sound/pci/hda/cs35l41_hda.c b/sound/pci/hda/cs35l41_hda.c
> index 129bffb431c2..b9d94f3a5b99 100644
> --- a/sound/pci/hda/cs35l41_hda.c
> +++ b/sound/pci/hda/cs35l41_hda.c
> @@ -1163,6 +1163,11 @@ static int cs35l41_no_acpi_dsd(struct cs35l41_hda *cs35l41, struct device *physd
> hw_cfg->gpio1.func = CS35l41_VSPK_SWITCH;
> hw_cfg->gpio1.valid = true;
> } else {
> + /*
> + * Note: CLSA010(0/1) are special cases which use a slightly different design.
> + * All other HIDs e.g. CSC3551 require valid ACPI _DSD properties to be supported.
> + */
> + dev_err(cs35l41->dev, "Error: ACPI _DSD Properties are missing for HID %s.", hid);
A newline is missing at the end of the string?
Takashi
prev parent reply other threads:[~2022-08-15 16:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-15 15:28 [PATCH v1] ALSA: hda: cs35l41: Clarify support for CSC3551 without _DSD Properties Stefan Binding
2022-08-15 16:12 ` Takashi Iwai [this message]
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=87fshxzdrv.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@opensource.cirrus.com \
--cc=perex@perex.cz \
--cc=sbinding@opensource.cirrus.com \
--cc=tiwai@suse.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