> On Apr 6, 2016, at 16:53 , Peter Hurley <[email protected]> wrote: > > If this is a latency problem, ftrace is probably your best bet, but > function_graph and the other tracers can induce even more latency.
Nothing so esoteric. I'm just trying to get the damn thing to work at all. It's worked in previous kernels, but not in the latest. Seeing what code gets executed will help a lot. But I'm currently stuck with the default diagnostics available (e.g. "Unable to set hw params for playback: Invalid argument" NOT HELPFUL). In the past, when I spent so much time with printk, I was trying to understand how all the modules worked together to actually configure and drive the CODEC. I found that to be virtually impossible to do in any comprehensive way, not already understanding it. Can't use printk() if you don't know where to put it. -- Rick Mann [email protected] -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
