From: Mark Brown <broonie@kernel.org>
To: Jaroslav Kysela <perex@perex.cz>
Cc: Leo Yan <leo.yan@linaro.org>, Takashi Iwai <tiwai@suse.de>,
alsa-devel@alsa-project.org, arnd@arndb.de,
keescook@chromium.org, bgoswami@codeaurora.org, sr@denx.de,
gustavo@embeddedor.com, philburk@google.com, willy@infradead.org,
mchehab+samsung@kernel.org, sboyd@kernel.org, vkoul@kernel.org,
Baolin Wang <baolin.wang@linaro.org>,
daniel.thompson@linaro.org, mathieu.poirier@linaro.org,
srinivas.kandagatla@linaro.org, anna-maria@linutronix.de,
corbet@lwn.net, jmiller@neverware.com,
ckeepax@opensource.wolfsonmicro.com, joe@perches.com,
o-takashi@sakamocchi.jp, colyli@suse.de,
linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH] ALSA: core: Add DMA share buffer support
Date: Thu, 24 Jan 2019 17:33:21 +0000 [thread overview]
Message-ID: <20190124173321.GE5641@sirena.org.uk> (raw)
In-Reply-To: <3962daba-f6ed-d706-c618-b791a1ba6b59@perex.cz>
[-- Attachment #1: Type: text/plain, Size: 1228 bytes --]
On Thu, Jan 24, 2019 at 02:43:02PM +0100, Jaroslav Kysela wrote:
> If I look to the dma_buf_fd() implementation:
> fd = get_unused_fd_flags(flags);
> fd_install(fd, dmabuf->file);
> .. what if we just add one new ioctl to the ALSA's PCM API which will
> return a new anonymous inode descriptor with the restricted access to
> the main PCM device to satisfy the SELinux requirements / security
> policies? It might be more nice and simple solution than to implement
> the full dma-buf interface for the ALSA's PCM devices.
That certainly works for me so long as the security people are happy.
> Question: The dma-buf also implements the fencing, but I am not able to
> determine, if this mechanism is used in android [1]. It may allow
> concurrent mmap and synchronize apps - but the sound server should
> manage the access to the DMA buffer anyway. In my opinion, it makes much
> sense for the video-pipes when the hardware does some accelerations
> (encoding/decoding).
We had the same discuission off list and couldn't think of a need for
that feature in the audio context but left it in as it's already there
with dma-buf so there's no real cost to implementing it and we weren't
sure we weren't missing something.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-01-24 17:33 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-18 4:55 [RFC PATCH] ALSA: core: Add DMA share buffer support Baolin Wang
2019-01-18 9:35 ` Jaroslav Kysela
2019-01-18 19:08 ` Mark Brown
2019-01-18 19:39 ` Takashi Iwai
2019-01-21 12:40 ` Mark Brown
2019-01-21 14:15 ` Jaroslav Kysela
2019-01-22 20:25 ` Mark Brown
2019-01-23 11:58 ` Takashi Iwai
2019-01-23 12:46 ` Leo Yan
2019-01-24 13:43 ` Jaroslav Kysela
2019-01-24 17:33 ` Mark Brown [this message]
2019-01-25 9:25 ` Baolin Wang
2019-01-25 10:10 ` Takashi Iwai
2019-01-25 10:20 ` Takashi Iwai
2019-01-25 11:24 ` Baolin Wang
2019-01-25 13:04 ` Takashi Iwai
2019-01-28 5:48 ` Baolin Wang
2019-01-25 11:11 ` Baolin Wang
2019-01-25 13:03 ` Takashi Iwai
2019-01-28 5:47 ` Baolin Wang
2019-01-25 13:19 ` [alsa-devel] " Takashi Iwai
2019-01-25 18:25 ` Mark Brown
2019-01-28 13:31 ` Jaroslav Kysela
2019-01-28 14:14 ` Takashi Iwai
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=20190124173321.GE5641@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=anna-maria@linutronix.de \
--cc=arnd@arndb.de \
--cc=baolin.wang@linaro.org \
--cc=bgoswami@codeaurora.org \
--cc=ckeepax@opensource.wolfsonmicro.com \
--cc=colyli@suse.de \
--cc=corbet@lwn.net \
--cc=daniel.thompson@linaro.org \
--cc=gustavo@embeddedor.com \
--cc=jmiller@neverware.com \
--cc=joe@perches.com \
--cc=keescook@chromium.org \
--cc=leo.yan@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=mchehab+samsung@kernel.org \
--cc=o-takashi@sakamocchi.jp \
--cc=perex@perex.cz \
--cc=philburk@google.com \
--cc=sboyd@kernel.org \
--cc=sr@denx.de \
--cc=srinivas.kandagatla@linaro.org \
--cc=tiwai@suse.de \
--cc=vkoul@kernel.org \
--cc=willy@infradead.org \
/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