From: Vinod Koul <vinod.koul@intel.com>
To: Chemsi Mehdi <chmsmehdi@gmail.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: How does ALSALIB commuciates with low level kernel API
Date: Mon, 20 Jun 2016 23:13:52 +0530 [thread overview]
Message-ID: <20160620174352.GV16910@localhost> (raw)
In-Reply-To: <CAHkWnPYuUgrARoMDHjg-0vSKVfz7x6tfh9cpzoEHzvEs+cvUKA@mail.gmail.com>
On Wed, Jun 15, 2016 at 12:12:24AM +0100, Chemsi Mehdi wrote:
> Dear experts,
>
> I am too new in ALSA, trying to read a little bit and understand.
> I want to underatnd how ALSA userspace API calls kernel space code ?
> for example when I call snd_pcm_open() which code is called in kernel
> sound code ?
easist would be to start gdb on alsa-lib snd_pcm_open() and start tracing
the steps.
> and how the link is made ? via IOCTL/write ?
IOCTL, see sound/core/pcm_native.c on kernel side..
--
~Vinod
prev parent reply other threads:[~2016-06-20 17:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-14 23:12 How does ALSALIB commuciates with low level kernel API Chemsi Mehdi
2016-06-15 7:00 ` Clemens Ladisch
2016-06-20 17:43 ` Vinod Koul [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=20160620174352.GV16910@localhost \
--to=vinod.koul@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=chmsmehdi@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