On Sat, Mar 30, 2019 at 02:32:35AM +0000, Zengtao (B) wrote: > >-----Original Message----- > >From: Greg Kroah-Hartman [mailto:gre...@linuxfoundation.org] > >Sent: Saturday, March 30, 2019 12:04 AM > >To: Zengtao (B) <prime.z...@hisilicon.com> > >Cc: labb...@redhat.com; sumit.sem...@linaro.org; > >de...@driverdev.osuosl.org; Todd Kjos <tk...@android.com>; > >linux-ker...@vger.kernel.org; dri-de...@lists.freedesktop.org; > >linaro-mm-...@lists.linaro.org; Arve Hjønnevåg <a...@android.com>; > >Joel Fernandes <j...@joelfernandes.org>; Martijn Coenen > ><m...@android.com>; Christian Brauner <christ...@brauner.io> > >Subject: Re: [PATCH] staging: android: ion: refactory ion_alloc for kernel > >driver use > > > >On Sat, Mar 30, 2019 at 02:40:16AM +0800, Zeng Tao wrote: > >> There are two reasons for this patch: > >> 1. There are some potential requirements for ion_alloc in kernel > >> space, some media drivers need to allocate media buffers from ion > >> instead of buddy or dma framework, this is more convient and clean > >> very for media drivers. And In that case, ion is the only media buffer > >> provider, it's more easier to maintain. > > > >As this really is just DMA, what is wrong with the existing dma framework > >that makes it hard to use? You have seen all of the changes recently to it, > >right? > > The current dma framework is powerful enough(to me, and more complex ^_^) > , CMA, IOMMU are all integrated, it's good. But buffer sharing, statistics, > debug, > are not so friendly for media drivers(each driver has to do all, but > duplicate jobs).
Then go add statistics and debugging to the dma code so that everyone benefits! thanks, greg k-h _______________________________________________ devel mailing list de...@linuxdriverproject.org http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
