Hi,
On Mon, Sep 08, 2014 at 09:30:27AM +0530, Pratyush Anand wrote:
On Fri, Sep 05, 2014 at 10:56:26PM +0800, Felipe Balbi wrote:
When we're debugging hard-to-reproduce and time-sensitive
use cases, printk() poses too much overhead. That's when
the kernel's tracing infrastructure comes
On Mon, Sep 08, 2014 at 09:35:33PM +0800, Felipe Balbi wrote:
Hi,
On Mon, Sep 08, 2014 at 09:30:27AM +0530, Pratyush Anand wrote:
On Fri, Sep 05, 2014 at 10:56:26PM +0800, Felipe Balbi wrote:
When we're debugging hard-to-reproduce and time-sensitive
use cases, printk() poses too much
On Fri, Sep 05, 2014 at 10:56:26PM +0800, Felipe Balbi wrote:
When we're debugging hard-to-reproduce and time-sensitive
use cases, printk() poses too much overhead. That's when
the kernel's tracing infrastructure comes into play.
This patch implements a few initial tracepoints for the
dwc3
When we're debugging hard-to-reproduce and time-sensitive
use cases, printk() poses too much overhead. That's when
the kernel's tracing infrastructure comes into play.
This patch implements a few initial tracepoints for the
dwc3 driver. More traces can be added as necessary in order
to ease the
