From: Stefan Binding <sbinding@opensource.cirrus.com>
To: Aleksandrs Vinarskis <alex.vinarskis@gmail.com>, <tiwai@suse.de>
Cc: <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>, <stuarth@opensource.cirrus.com>,
<tiwai@suse.com>
Subject: Re: [PATCH v2 1/2] ALSA: hda: cs35l41: Safety-guard against capped SPI speed
Date: Wed, 20 Dec 2023 13:43:55 +0000 [thread overview]
Message-ID: <8170413d-07a8-4e77-b43d-78cd9e4ea76f@opensource.cirrus.com> (raw)
In-Reply-To: <20231220073809.22027-2-alex.vinarskis@gmail.com>
Hi,
On 20/12/2023 07:38, Aleksandrs Vinarskis wrote:
> Some devices with intel-lpss based SPI controllers may have misconfigured
> clock divider due to firmware bug. This would result in capped SPI speeds,
> which leads to longer DSP firmware loading times.
> This safety guards against possible hangs during wake-up by not
> initializing the device if lpss was not patched/fixed UEFI was not
> installed
>
> Signed-off-by: Aleksandrs Vinarskis <alex.vinarskis@gmail.com>
> ---
> sound/pci/hda/cs35l41_hda_property.c | 15 +++++++++++++--
> 1 file changed, 13 insertions(+), 2 deletions(-)
>
> diff --git a/sound/pci/hda/cs35l41_hda_property.c b/sound/pci/hda/cs35l41_hda_property.c
> index c9eb70290973..cb305b093311 100644
> --- a/sound/pci/hda/cs35l41_hda_property.c
> +++ b/sound/pci/hda/cs35l41_hda_property.c
> @@ -210,6 +210,19 @@ static int generic_dsd_config(struct cs35l41_hda *cs35l41, struct device *physde
>
> if (cfg->bus == SPI) {
> cs35l41->index = id;
> + /*
> + * Some devices with intel-lpss based SPI controllers may have misconfigured
> + * clock divider due to firmware bug. This would result in capped SPI speeds,
> + * which leads to longer DSP firmware loading times.
> + * Avoid initializing device if lpss was not patched/fixed UEFI was not installed
> + */
> + spi = to_spi_device(cs35l41->dev);
> + if (spi->max_speed_hz < CS35L41_SPI_MAX_FREQ/2) {
> + dev_err(cs35l41->dev,
> + "SPI's max_speed_hz is capped at %u Hz, will not continue to avoid hanging\n",
> + spi->max_speed_hz);
> + return -EINVAL;
> + }
Not sure I agree with completely disabling the CS35L41 Speaker Driver if
the SPI speed is low (for laptops without _DSD).
With a slow speed the driver does not hang - it just takes a long time
(~80s per amp) to load the firmware.
Instead I would prefer that we instead disable the loading of the
firmware in this case.
Without loading firmware, the volume is much lower, but at least you
still have audio.
I have a patch to do that, which I was planning on pushing up
(hopefully) today.
Thanks,
Stefan
> /*
> * Manually set the Chip Select for the second amp <cs_gpio_index> in the node.
> * This is only supported for systems with 2 amps, since we cannot expand the
> @@ -219,8 +232,6 @@ static int generic_dsd_config(struct cs35l41_hda *cs35l41, struct device *physde
> * first.
> */
> if (cfg->cs_gpio_index >= 0) {
> - spi = to_spi_device(cs35l41->dev);
> -
> if (cfg->num_amps != 2) {
> dev_warn(cs35l41->dev,
> "Cannot update SPI CS, Number of Amps (%d) != 2\n",
next prev parent reply other threads:[~2023-12-20 13:44 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 ` [PATCH v2 0/2] ALSA: hda: cs35l41: Support Dell XPS 9530 (2023) Aleksandrs Vinarskis
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 [this message]
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=8170413d-07a8-4e77-b43d-78cd9e4ea76f@opensource.cirrus.com \
--to=sbinding@opensource.cirrus.com \
--cc=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=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®