From: Mark Brown <broonie@sirena.org.uk>
To: Anuj Aggarwal <anuj.aggarwal@gmail.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: ALSA SoC Architecture Document
Date: Tue, 17 Feb 2009 14:13:08 +0000 [thread overview]
Message-ID: <20090217141307.GC25029@sirena.org.uk> (raw)
In-Reply-To: <2ee9e08d0902170520v23a3bb7ao271ba1e9553d8c8a@mail.gmail.com>
On Tue, Feb 17, 2009 at 06:50:32PM +0530, Anuj Aggarwal wrote:
[Please don't top post.]
> As I have mentioned earlier, I am specifically looking for some
> architecture/block diagrams and data/control paths which will enable
> users to grasp quickly what is lying underneath, instead of the user
> going and reading the kernel documentation.
What exactly are you trying to give an overview of - who is the user and
what do they want to know?
If you're trying to explain what the controls exposed to user space map
to then that's going to be specific to a given board (and codec). If
you just want a brief overview of how things are structured in kernel
without any detail then if there's nothing in any of the presentations
then something along the lines of the quick ASCII art below *might*
help?
/----\
|ALSA|
\----/
||
/---------\
|ASoC core|
\---------/
||
=====================
|| || ||
/-------\ /--------\ /-----\
|Machine| |Platform| |Codec|
\-------/ \--------/ \-----/
prev parent reply other threads:[~2009-02-17 14:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-17 12:11 ALSA SoC Architecture Document Anuj Aggarwal
2009-02-17 13:07 ` Mark Brown
2009-02-17 13:20 ` Anuj Aggarwal
2009-02-17 14:13 ` 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=20090217141307.GC25029@sirena.org.uk \
--to=broonie@sirena.org.uk \
--cc=alsa-devel@alsa-project.org \
--cc=anuj.aggarwal@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 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.