From: Simon Trimmer <simont@opensource.cirrus.com>
To: <tiwai@suse.com>
Cc: <linux-sound@vger.kernel.org>, <alsa-devel@alsa-project.org>,
<linux-kernel@vger.kernel.org>, <patches@opensource.cirrus.com>
Subject: RE: [PATCH] ALSA: hda: cs35l56: Perform firmware download in the background
Date: Tue, 18 Jun 2024 13:59:56 +0100 [thread overview]
Message-ID: <000b01dac17f$6b84e5d0$428eb170$@opensource.cirrus.com> (raw)
In-Reply-To: <20240618125325.61173-1-simont@opensource.cirrus.com>
On Tue, Jun 18, 2024 at 1:53 PM Simon Trimmer
> Subject: [PATCH] ALSA: hda: cs35l56: Perform firmware download in the background
>
> It is possible that during system boot when there multiple devices
> attempting simultaneous initialization on a slow control bus the
> download of firmware and tuning data may take a user perceivable amount
> of time (a slow I2C bus with 4 amps this work could take over 2
> seconds).
>
> Adopt a pattern used in the ASoC driver and perform this activity in a
> background thread so that interactive performance is not impaired. The
> system_long_wq is a parallel workqueue and driver instances will perform
> their firmware downloads in parallel to make best use of available bus
> bandwidth.
>
> Signed-off-by: Simon Trimmer <simont@opensource.cirrus.com>
Sorry Takashi this should have had v2 in the Subject - when fixing up v1 we
found all the things that triggered the series of hda_component changes
so it fell off my mental queue as something I'd published before.
I'll do a re-send with that corrected for Lore.
-Simon
next prev parent reply other threads:[~2024-06-18 13:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-18 12:53 [PATCH] ALSA: hda: cs35l56: Perform firmware download in the background Simon Trimmer
2024-06-18 12:59 ` Simon Trimmer [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-05-01 11:17 Simon Trimmer
2024-05-02 7:34 ` Takashi Iwai
2024-05-02 9:21 ` Richard Fitzgerald
2024-05-02 9:52 ` Takashi Iwai
2024-05-02 10:17 ` Simon Trimmer
2024-05-02 10:25 ` 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='000b01dac17f$6b84e5d0$428eb170$@opensource.cirrus.com' \
--to=simont@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=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