From: Aleksandrs Vinarskis <alex.vinarskis@gmail.com>
To: tiwai@suse.de
Cc: alex.vinarskis@gmail.com, alsa-devel@alsa-project.org,
david.rhodes@cirrus.com, james.schulman@cirrus.com,
josbeir@gmail.com, linux-kernel@vger.kernel.org,
patches@opensource.cirrus.com, perex@perex.cz,
sbinding@opensource.cirrus.com, stuarth@opensource.cirrus.com,
tiwai@suse.com
Subject: [PATCH v2 0/2] ALSA: hda: cs35l41: Support Dell XPS 9530 (2023)
Date: Wed, 20 Dec 2023 08:38:07 +0100 [thread overview]
Message-ID: <20231220073809.22027-1-alex.vinarskis@gmail.com> (raw)
In-Reply-To: <87ttokpyws.wl-tiwai@suse.de>
Following changes by Cirrus, attaching rebased (and greatly simplified)
patch to support Dell XPS 9530 (2023) laptop.
Safety-guard against capped SPI speed is added via separate patch. It is
not conditioned to particular subsystem, as all devices normally should
pass this check. Following suggestion by Stuart Henderson, error out
threshold is lowered to 1/2 of requested rate.
Aleksandrs Vinarskis (2):
ALSA: hda: cs35l41: Safety-guard against capped SPI speed
ALSA: hda: cs35l41: Support Dell XPS 9530 (2023)
sound/pci/hda/cs35l41_hda_property.c | 17 +++++++++++++++--
1 file changed, 15 insertions(+), 2 deletions(-)
--
2.40.1
next prev parent reply other threads:[~2023-12-20 7:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-12 19:52 [PATCH 1/1] ALSA: hda: cs35l41: Dell Fiorano add missing _DSD properties Aleksandrs Vinarskis
2023-12-14 11:02 ` Takashi Iwai
2023-12-14 15:39 ` Stuart Henderson
2023-12-14 15:49 ` Takashi Iwai
2023-12-14 19:36 ` Aleksandrs Vinarskis
2023-12-18 11:51 ` Andy Shevchenko
2023-12-20 7:38 ` Aleksandrs Vinarskis [this message]
2023-12-20 7:38 ` [PATCH v2 1/2] ALSA: hda: cs35l41: Safety-guard against capped SPI speed Aleksandrs Vinarskis
2023-12-20 13:43 ` Stefan Binding
2023-12-21 11:24 ` Aleksandrs Vinarskis
2023-12-21 15:09 ` Stefan Binding
2023-12-20 7:38 ` [PATCH v2 2/2] ALSA: hda: cs35l41: Support Dell XPS 9530 (2023) Aleksandrs Vinarskis
2023-12-20 13:47 ` Stefan Binding
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=20231220073809.22027-1-alex.vinarskis@gmail.com \
--to=alex.vinarskis@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=david.rhodes@cirrus.com \
--cc=james.schulman@cirrus.com \
--cc=josbeir@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@opensource.cirrus.com \
--cc=perex@perex.cz \
--cc=sbinding@opensource.cirrus.com \
--cc=stuarth@opensource.cirrus.com \
--cc=tiwai@suse.com \
--cc=tiwai@suse.de \
/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
all inboxes | Powered by JetHome®