On 17.01.2017 10:03, Felipe Balbi wrote:
Hi,
Lu Baolu writes:
Move the trace down until the address device command completes.
no. I would loose the tracepoint for the command being queued. I want to
see queue -> execute -> complete for everything. And I want to know what
changes along the wa
Hi,
Lu Baolu writes:
>>> Move the trace down until the address device command completes.
>> no. I would loose the tracepoint for the command being queued. I want to
>> see queue -> execute -> complete for everything. And I want to know what
>> changes along the way (slot context, ep context, etc
Hi,
On 01/16/2017 05:08 PM, Felipe Balbi wrote:
> Hi,
>
> Lu Baolu writes:
>> Hi,
>>
>> On 12/29/2016 07:01 PM, Felipe Balbi wrote:
>>> Let's start tracing at least part of an xhci_virt_device lifetime. We
>>> might want to extend this tracepoint class later, but for now it already
>>> exposes qu
Hi,
Lu Baolu writes:
> Hi,
>
> On 12/29/2016 07:01 PM, Felipe Balbi wrote:
>> Let's start tracing at least part of an xhci_virt_device lifetime. We
>> might want to extend this tracepoint class later, but for now it already
>> exposes quite a bit of valuable information.
>>
>> Signed-off-by: Fel
Hi,
On 12/29/2016 07:01 PM, Felipe Balbi wrote:
> Let's start tracing at least part of an xhci_virt_device lifetime. We
> might want to extend this tracepoint class later, but for now it already
> exposes quite a bit of valuable information.
>
> Signed-off-by: Felipe Balbi
> ---
> drivers/usb/ho
Let's start tracing at least part of an xhci_virt_device lifetime. We
might want to extend this tracepoint class later, but for now it already
exposes quite a bit of valuable information.
Signed-off-by: Felipe Balbi
---
drivers/usb/host/xhci-hub.c | 2 ++
drivers/usb/host/xhci-mem.c | 7 ++
