From: Stefan Binding <sbinding@opensource.cirrus.com>
To: Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>
Cc: <alsa-devel@alsa-project.org>, <linux-sound@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <patches@opensource.cirrus.com>,
"Stefan Binding" <sbinding@opensource.cirrus.com>
Subject: [PATCH v2 0/3] Support Dell models without _DSD
Date: Thu, 21 Dec 2023 13:25:15 +0000 [thread overview]
Message-ID: <20231221132518.3213-1-sbinding@opensource.cirrus.com> (raw)
Add Quirks and driver properties for Dell models.
Driver properties are required since these models do not have _DSD.
Additionally, some laptops, including some of these, have an issue
with their BIOS which causes the SPI speed to be set too slow.
To ensure a decent performance for laptops with this slow speed,
disable firmware loading. Running without firmware results in lower
volume.
Changes since v1:
- Rebased onto for-linus
Stefan Binding (3):
ALSA: hda: cs35l41: Support additional Dell models without _DSD
ALSA: hda: cs35l41: Prevent firmware load if SPI speed too low
ALSA: hda/realtek: Add quirks for Dell models
sound/pci/hda/cs35l41_hda.c | 25 ++++++++--
sound/pci/hda/cs35l41_hda.h | 12 ++++-
sound/pci/hda/cs35l41_hda_i2c.c | 2 +-
sound/pci/hda/cs35l41_hda_property.c | 74 +++++++++++++++-------------
sound/pci/hda/cs35l41_hda_spi.c | 2 +-
sound/pci/hda/patch_realtek.c | 13 +++++
6 files changed, 87 insertions(+), 41 deletions(-)
--
2.34.1
next reply other threads:[~2023-12-21 13:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-21 13:25 Stefan Binding [this message]
2023-12-21 13:25 ` [PATCH v2 1/3] ALSA: hda: cs35l41: Support additional Dell models without _DSD Stefan Binding
2023-12-21 13:25 ` [PATCH v2 2/3] ALSA: hda: cs35l41: Prevent firmware load if SPI speed too low Stefan Binding
2023-12-21 13:25 ` [PATCH v2 3/3] ALSA: hda/realtek: Add quirks for Dell models Stefan Binding
2023-12-29 14:15 ` [PATCH v2 0/3] Support Dell models without _DSD Takashi Iwai
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=20231221132518.3213-1-sbinding@opensource.cirrus.com \
--to=sbinding@opensource.cirrus.com \
--cc=alsa-devel@alsa-project.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=patches@opensource.cirrus.com \
--cc=perex@perex.cz \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.