On Tue, 2018-09-04 at 16:03 +0100, Mark Brown wrote: > On Tue, Sep 04, 2018 at 02:21:20PM +0100, Liam Girdwood wrote: > > On Mon, 2018-09-03 at 17:25 +0100, Mark Brown wrote: > > > Should this be integrated into the Linux trace event mechanism rather > > > than open coded? It would at least be nice to not call this a trace > > > event buffer - when I initially read this I was expecting it to be for > > > the standard Linux stuff which obviously it isn't. > > Your right, I'll rename. The eventual aim is to make it more like Linux > > trace > > but we are constrained somewhat as some DSPs only 96kB or instruction RAM, > > hence > > it's a simple and raw trace infrastructure. > > I was thinking the code could read it like it's doing now and then just > have a trace event to dump it into the core trace infrastructure as it > reads things in. Most of the data is binary atm, so we were decoding in userspace. Any objection to decoding in the kernel as different trace events ? Thanks Liam _______________________________________________ Alsa-devel mailing list Alsa-devel@xxxxxxxxxxxxxxxx http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
