All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Jaroslav Kysela <perex@perex.cz>
Cc: ALSA development <alsa-devel@alsa-project.org>,
	Baolin Wang <baolin.wang@linaro.org>,
	Phil Burk <philburk@google.com>, Zach Riggle <riggle@google.com>,
	Mark Brown <broonie@kernel.org>, Leo Yan <leo.yan@linaro.org>
Subject: Re: [PATCH 0/2 v4] ALSA: pcm: anonymous dup implementation
Date: Tue, 23 Apr 2019 20:08:12 +0200	[thread overview]
Message-ID: <s5hd0lcppbn.wl-tiwai@suse.de> (raw)
In-Reply-To: <f5b429c6-803c-b624-6d39-5001c76e892f@perex.cz>

On Tue, 26 Mar 2019 15:41:11 +0100,
Jaroslav Kysela wrote:
> 
> Dne 26. 03. 19 v 15:27 Phil Burk napsal(a):
> > Hello,
> > 
> > Thanks for keeping this moving forward.
> > 
> > Any suggestions for testing this? We can try to test it here in Android. It may be tricky because your patches may conflict with some proprietary Qualcomm changes in the kernel we are currently using.
> > 
> > Can I get a summary list of the patches required for kernel and tinyalsa?
> 
> The v6 is the last version, the full information is in the cover letter:
> 
> https://mailman.alsa-project.org/pipermail/alsa-devel/2019-February/145127.html
> https://mailman.alsa-project.org/pipermail/alsa-devel/2019-February/145128.html
> https://mailman.alsa-project.org/pipermail/alsa-devel/2019-February/145129.html
> https://mailman.alsa-project.org/pipermail/alsa-devel/2019-February/145130.html

Is there any test result from the practical use cases?

Basically now is the last chance for merging such an intrusive change
for 5.2 kernel.  If we miss it, it'll be postponed at least for 5.3,
i.e. more three months.


thanks,

Takashi


> 
> 						Jaroslav
> 
> > 
> > Thanks,
> > Phil Burk
> > 
> > 
> > On Tue, Mar 26, 2019 at 7:13 AM Takashi Iwai <tiwai@suse.de <mailto:tiwai@suse.de>> wrote:
> > 
> >     On Tue, 26 Mar 2019 15:09:28 +0100,
> >     Mark Brown wrote:
> >     >
> >     > On Mon, Feb 04, 2019 at 10:39:08AM +0100, Jaroslav Kysela wrote:
> >     > > This patchset contains the anonymous dup implementation with permissions
> >     > > checking for the ALSA's PCM interface in kernel to enable the restricted
> >     > > DMA sound buffer sharing for the restricted tasks.
> >     >
> >     > Is there any news on merging this during the current development cycle,
> >     > or anything else needed to move this forwards?
> > 
> >     I've seen no reaction whether the patch really tested, worked or
> >     helped in the real scenario...
> > 
> > 
> >     Takashi
> > 
> 
> 
> -- 
> Jaroslav Kysela <perex@perex.cz>
> Linux Sound Maintainer; ALSA Project; Red Hat, Inc.
> 
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel

  reply	other threads:[~2019-04-23 18:08 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-04  9:39 [PATCH 0/2 v4] ALSA: pcm: anonymous dup implementation Jaroslav Kysela
2019-02-04  9:39 ` [PATCH 1/2] ALSA: pcm: implement the anonymous dup (inode file descriptor) Jaroslav Kysela
2019-02-04  9:39 ` [PATCH 2/2] ALSA: pcm: implement the mmap buffer mode for the anonymous dup Jaroslav Kysela
2019-02-04 10:48   ` Takashi Iwai
2019-02-07 17:41 ` [PATCH 0/2 v4] ALSA: pcm: anonymous dup implementation Phil Burk
2019-02-07 17:53   ` Jaroslav Kysela
2019-02-08 15:57     ` Phil Burk
2019-03-26 14:09 ` Mark Brown
2019-03-26 14:13   ` Takashi Iwai
2019-03-26 14:27     ` Phil Burk
2019-03-26 14:41       ` Jaroslav Kysela
2019-04-23 18:08         ` Takashi Iwai [this message]
2019-04-23 20:11           ` Phil Burk
2019-04-23 20:25             ` Takashi Iwai
2020-06-08 13:45             ` Mark Brown
2020-06-08 17:49               ` Phil Burk
2020-06-10 23:10                 ` Phil Burk
2020-06-12 16: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=s5hd0lcppbn.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=baolin.wang@linaro.org \
    --cc=broonie@kernel.org \
    --cc=leo.yan@linaro.org \
    --cc=perex@perex.cz \
    --cc=philburk@google.com \
    --cc=riggle@google.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.