From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Anksh Agarwal <anksh.agarwal@gmail.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: Query about code organization for kernel driver.
Date: Mon, 24 May 2010 23:19:01 +0100 [thread overview]
Message-ID: <20100524221900.GA13604@sirena.org.uk> (raw)
In-Reply-To: <AANLkTin91dBbESP2i_LyZKoL0KdBWFKzqKPIpuQyIIGY@mail.gmail.com>
On Tue, May 25, 2010 at 01:17:39AM +0530, Anksh Agarwal wrote:
> i am not aware how to split the audio path enable/disable code from the soc
> driver
> and which would be ideal directory to place them, since there is hardly any
> interaction
> between playback and device enable/disable routines? I think the device
> enable/disable code outside sound/ directory wont be a good idea as its
> to be specifically used by alsa playback/record only.
Could you be more specific about what you mean by "enable/disable
rountines" and a "list of devices"? What are you actually trying to
control or enable and disable here? Your description of having a sysfs
file for changing devices at runtime sounds like something that would
normally be done via the ALSA APIs but it's very hard to understand what
exactly you're controlling here.
prev parent reply other threads:[~2010-05-24 22:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-24 19:47 Query about code organization for kernel driver Anksh Agarwal
2010-05-24 22:19 ` Mark Brown [this message]
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=20100524221900.GA13604@sirena.org.uk \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=anksh.agarwal@gmail.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;
as well as URLs for NNTP newsgroup(s).