From: Jaroslav Kysela <perex@perex.cz>
To: Phil Burk <philburk@google.com>, Mark Brown <broonie@kernel.org>
Cc: "Takashi Iwai" <tiwai@suse.de>,
"Zach Riggle 🖖" <riggle@google.com>,
"ALSA development" <alsa-devel@alsa-project.org>,
"Baolin Wang" <baolin.wang@linaro.org>,
"Leo Yan" <leo.yan@linaro.org>
Subject: Re: [PATCH 0/2] ALSA: pcm: implement the anonymous dup v3
Date: Fri, 1 Feb 2019 17:28:44 +0100 [thread overview]
Message-ID: <4901c6a6-605e-4f43-ff38-eb492495a3c9@perex.cz> (raw)
In-Reply-To: <CACL=Q7wkh4h4YNrLUS8ihBqkc-t3-B1x2s1n_f9WP_B=oRyGJg@mail.gmail.com>
Dne 1.2.2019 v 16:31 Phil Burk napsal(a):
> Thank you all for sorting this out. It seems like we are moving in a
> really good direction.
>
>> I agree. We can have just two modes for the beginning:
>> a) full one (useful for testing)
>> b) buffer only (allow just sound data mmap)
>
> The full one is would also be used by the HAL for querying the DSP position.
>
>> if we should use different names (like anon_inode:snd-pcm and
> anon_inode:snd-pcm-buffer)
>
> That would be helpful.
>
> I have attached a revised requirements doc. The original doc was more of
> a HowTo for OEMs to create the "anon_inode:dmabuf" FD.. This clarifies
> the requirements and allows for the use of "anon_inode:snd-pcm*". It
> should match what we have arrived at by discussion. Let me know if it
> makes sense.
It looks fine, but the HAL will use probably the standard sound device
open (/dev/snd/), doesn't? So:
fd1 - /dev/snd/pcm (HAL) - standard sound device inode (no restrictions)
fd2 - anon_inode:snd-pcm-buffer (for the EXCLUSIVE access)
With modes, I talked about the anonymous dup ioctl parameter. If there's
another resource manager above HAL, the situation might be:
fd1 - /dev/snd/pcm (resource manager) - standard sound device inode
fd2 - anon_inode:snd-pcm (access to the full pcm sound API using the
anonymous inode)
fd3 - anon_inode:snd-pcm-buffer (for the EXCLUSIVE access)
Perhaps you have different layers in Android.
Thanks,
Jaroslav
--
Jaroslav Kysela <perex@perex.cz>
Linux Sound Maintainer; ALSA Project; Red Hat, Inc.
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2019-02-01 16:28 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-30 12:41 [PATCH 0/2] ALSA: pcm: implement the anonymous dup v3 Jaroslav Kysela
2019-01-30 12:41 ` [PATCH 1/2] ALSA: pcm: implement the anonymous dup (inode file descriptor) Jaroslav Kysela
2019-01-30 12:41 ` [PATCH 2/2] ALSA: pcm: implement the ioctl/mmap filter for the anonymous dup Jaroslav Kysela
2019-01-30 22:32 ` [PATCH 0/2] ALSA: pcm: implement the anonymous dup v3 Mark Brown
2019-01-31 0:45 ` Phil Burk
2019-01-31 8:06 ` Leo Yan
2019-01-31 8:17 ` Takashi Iwai
2019-01-31 8:25 ` Jaroslav Kysela
2019-01-31 8:08 ` Takashi Iwai
2019-01-31 12:26 ` Mark Brown
2019-01-31 13:30 ` Jaroslav Kysela
2019-01-31 15:48 ` Phil Burk
2019-01-31 19:35 ` Phil Burk
2019-01-31 19:54 ` Zach Riggle 🖖
2019-01-31 20:32 ` Takashi Iwai
2019-02-01 9:55 ` Jaroslav Kysela
2019-02-01 13:01 ` Mark Brown
2019-02-01 15:31 ` Phil Burk
2019-02-01 16:28 ` Jaroslav Kysela [this message]
2019-02-01 16:39 ` Phil Burk
2019-02-01 12:59 ` Mark Brown
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=4901c6a6-605e-4f43-ff38-eb492495a3c9@perex.cz \
--to=perex@perex.cz \
--cc=alsa-devel@alsa-project.org \
--cc=baolin.wang@linaro.org \
--cc=broonie@kernel.org \
--cc=leo.yan@linaro.org \
--cc=philburk@google.com \
--cc=riggle@google.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.