From: Takashi Iwai <tiwai@suse.de>
To: Thadeu Lima de Souza Cascardo <cascardo@holoscopio.com>
Cc: alsa-devel@alsa-project.org, ibm-acpi@hmh.eng.br,
Jaroslav Kysela <perex@perex.cz>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] alsa: use subsys_initcall for sound core instead of module_init
Date: Thu, 14 Jan 2010 17:18:26 +0100 [thread overview]
Message-ID: <s5hd41ck6ct.wl%tiwai@suse.de> (raw)
In-Reply-To: <20100114155342.GA1396@holoscopio.com>
At Thu, 14 Jan 2010 13:53:43 -0200,
Thadeu Lima de Souza Cascardo wrote:
>
> On Wed, Jan 13, 2010 at 07:48:07AM +0100, Takashi Iwai wrote:
> > At Tue, 12 Jan 2010 20:20:39 -0200,
> > Thadeu Lima de Souza Cascardo wrote:
> > >
> > > This is needed for built-in drivers which are built before the sound directory,
> > > like thinkpad_acpi.
> > >
> > > Otherwise, registering a card fails.
> >
> > Oh well, this kind of problem hits again.
> >
> > I don't remember why subsys_init() wasn't taken before... Maybe some
> > dependency between sound and V4L or so. But, it's worth to check again.
> >
>
> Any references to this dependency problem, so I can try to help and investigate
> about it and do some tests?
I also don't remember. That was a long long ago... :)
> > I'll apply this after some testing.
> >
>
> Built-in thinkpad-acpi started working for me after these changes. I can't tell
> you about any subsystem that stopped working, like some V4L driver.
Did you test whether the sound subsystem still works as modules?
Takashi
next prev parent reply other threads:[~2010-01-14 16:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-12 22:20 Thadeu Lima de Souza Cascardo
2010-01-13 6:48 ` Takashi Iwai
2010-01-14 15:53 ` Thadeu Lima de Souza Cascardo
2010-01-14 16:18 ` Takashi Iwai [this message]
2010-01-14 16:22 ` Thadeu Lima de Souza Cascardo
2010-01-14 16:31 ` Takashi Iwai
2010-01-15 14:40 ` 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=s5hd41ck6ct.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=cascardo@holoscopio.com \
--cc=ibm-acpi@hmh.eng.br \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
/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®