<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/drivers/usb/dwc3/debug.c, branch v4.2</title>
<subtitle>Mirror of https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/
</subtitle>
<id>https://git.shady.money/linux/atom?h=v4.2</id>
<link rel='self' href='https://git.shady.money/linux/atom?h=v4.2'/>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/'/>
<updated>2014-09-05T14:55:51Z</updated>
<entry>
<title>usb: dwc3: add tracepoints to aid debugging</title>
<updated>2014-09-05T14:55:51Z</updated>
<author>
<name>Felipe Balbi</name>
<email>balbi@ti.com</email>
</author>
<published>2014-04-30T22:45:10Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=2c4cbe6e5a9c71408b496e00a78ea9284e98af16'/>
<id>urn:sha1:2c4cbe6e5a9c71408b496e00a78ea9284e98af16</id>
<content type='text'>
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 task of debugging dwc3.

Reviewed-by: Paul Zimmerman &lt;paulz@synopsys.com&gt;
Signed-off-by: Felipe Balbi &lt;balbi@ti.com&gt;
</content>
</entry>
</feed>
