From: David Henningsson <david.henningsson@canonical.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: "Lin, Mengdong" <mengdong.lin@intel.com>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: Re: HD-Audio: How to reduce driver initializaton time if multiple codecs present on the bus?
Date: Fri, 29 Nov 2013 15:31:59 +0800 [thread overview]
Message-ID: <529842EF.8070800@canonical.com> (raw)
In-Reply-To: <s5hmwkng17c.wl%tiwai@suse.de>
2013-11-29 14:40, Takashi Iwai skrev:
> At Fri, 29 Nov 2013 14:30:48 +0800,
> David Henningsson wrote:
>> 2013-11-28 22:57, Lin, Mengdong skrev:
>>> Hi Takashi,
>>>
>>> We're trying to reduce the HD-A driver initialization time when more than one codecs are connected to the bus, but are blocked.
>>> Would you please share some advices on this?
>>>
>>> Usually, there is one HD-A controller connecting to two codecs: one on-board codec and one integrated display codec.
>>> During initialization, the codecs are created and configured in a serial way.
>>>
>>> Creating a codec may cost 6~20ms, and then building controls make cost about 15~30ms.
>> Sorry for interrupting, but I just wonder - I assume you have a maximum
>> of 4 CPUs. Can't the other 3 CPUs be used to load other non-audio
>> hardware in parallel instead? It sounds you're going to run into lock
>> contention instead if you try to modify the same card from two threads
>> simultaneously.
> IIRC, PCI device probes are done sequentially because asynchronous
> probe caused too many troubles. And if it's a module, it's anyway
> more strictly serialized.
Okay. It just seems to me that from a bird's eye view that parallelizing
module loading and pci probing would give us much bigger benefits than
trying to parallellize internally in the snd-hda-intel driver.
Btw, using a deferred azx_probe_continue (like we do if there's a
firmware file), would one get more parallelization with other drivers?
If so we could consider making that the default.
--
David Henningsson, Canonical Ltd.
https://launchpad.net/~diwic
next prev parent reply other threads:[~2013-11-29 7:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-28 14:57 HD-Audio: How to reduce driver initializaton time if multiple codecs present on the bus? Lin, Mengdong
2013-11-28 15:15 ` Takashi Iwai
2013-11-29 6:30 ` David Henningsson
2013-11-29 6:40 ` Takashi Iwai
2013-11-29 7:31 ` David Henningsson [this message]
2013-11-29 7:49 ` Takashi Iwai
2013-11-29 8:05 ` Lin, Mengdong
2013-11-29 8:07 ` Takashi Iwai
2013-12-02 7:23 ` Lin, Mengdong
2013-12-02 8:24 ` Takashi Iwai
2013-12-02 9:48 ` Lin, Mengdong
2013-12-02 9:52 ` Takashi Iwai
2013-12-02 10:18 ` Takashi Iwai
2013-12-02 11:27 ` Lin, Mengdong
2013-12-02 12:18 ` Takashi Iwai
2013-12-02 14: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=529842EF.8070800@canonical.com \
--to=david.henningsson@canonical.com \
--cc=alsa-devel@alsa-project.org \
--cc=mengdong.lin@intel.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 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.