From: Lars-Peter Clausen <lars@metafoo.de>
To: Bhaskara rao Budiredla <bhaskarbudiredla@gmail.com>,
alsa-devel@alsa-project.org
Cc: tiwai@suse.de
Subject: Re: Memory and Cycles overhead in <snd_soc_init>
Date: Tue, 10 Feb 2015 17:50:51 +0100 [thread overview]
Message-ID: <54DA36EB.7010007@metafoo.de> (raw)
In-Reply-To: <CAJWVF-wkq5xdH0WqOj+rWk4UEO4aZCcuv5JthvtDkEh8spDiaA@mail.gmail.com>
On 02/10/2015 12:58 PM, Bhaskara rao Budiredla wrote:
> Hi - May I know the purpose of the call to snd_soc_init( ) from kernel_init
> thread? snd_soc_init( ) is trying to register a dummy platform device
> "snd-soc-dummy" containing (dummy_codec/dummy_platform) and a sound card
> device. Neither of those devices are added to platform bus before they are
> making a call to platform_driver_register( ). Due to that platform_match(
> ) will fail and they will not be added to platform bus . Thus,
> snd_soc_init( ) is not doing any useful task during kernel boot time.
>
> Could someone help me if my understanding is correct? If I am correct,
> shall we remove the call to snd_soc_init( ) in kernel_init thread to save
> boot time and memory? Otherwise please suggest me where those dummy devices
> and sound card gets added to platform bus and the purpose of creating them?
All of the devices and driver registered in snd_soc_init() are used.
- Lars
next prev parent reply other threads:[~2015-02-10 16:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-10 11:58 Memory and Cycles overhead in <snd_soc_init> Bhaskara rao Budiredla
2015-02-10 16:50 ` Lars-Peter Clausen [this message]
2015-02-11 9:40 ` Bhaskara rao Budiredla
2015-02-11 12:47 ` Lars-Peter Clausen
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=54DA36EB.7010007@metafoo.de \
--to=lars@metafoo.de \
--cc=alsa-devel@alsa-project.org \
--cc=bhaskarbudiredla@gmail.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.