![](https://secure.gravatar.com/avatar/aa4dbd3b332942504b4b2157c4381476.jpg?s=120&d=mm&r=g)
Hello Takashi,
Sorry for the late reply. I got pulled off on some other projects.
We will try to test this in-house but we will need Qualcomm's help. I will also try to get some of our SOC partners to help with testing.
If we miss it, it'll be postponed at least for 5.3, i.e. more three months.
I think it will be difficult to complete the testing before that 5.2 deadline. We should probably shoot for 5.3. If someone needs it sooner that they will have the patches.
Thanks again for all this work.
I assume the four emails below have all the latest patches needed for rev 6.
Thanks, Phil Burk
On Tue, Apr 23, 2019 at 11:08 AM Takashi Iwai tiwai@suse.de wrote:
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.h...
https://mailman.alsa-project.org/pipermail/alsa-devel/2019-February/145128.h...
https://mailman.alsa-project.org/pipermail/alsa-devel/2019-February/145129.h...
https://mailman.alsa-project.org/pipermail/alsa-devel/2019-February/145130.h...
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.