Hi,

Lu Baolu <baolu...@linux.intel.com> writes:
>> +DEFINE_EVENT(xhci_log_trb, xhci_handle_event,
>> +    TP_PROTO(struct xhci_ring *ring, struct xhci_generic_trb *trb),
>> +    TP_ARGS(ring, trb)
>> +);
>> +
>> +DEFINE_EVENT(xhci_log_trb, xhci_handle_command,
>> +    TP_PROTO(struct xhci_ring *ring, struct xhci_generic_trb *trb),
>> +    TP_ARGS(ring, trb)
>> +);
>> +
>> +DEFINE_EVENT(xhci_log_trb, xhci_handle_transfer,
>> +    TP_PROTO(struct xhci_ring *ring, struct xhci_generic_trb *trb),
>> +    TP_ARGS(ring, trb)
>> +);
>> +
>> +DEFINE_EVENT(xhci_log_trb, xhci_queue_trb,
>> +    TP_PROTO(struct xhci_ring *ring, struct xhci_generic_trb *trb),
>> +    TP_ARGS(ring, trb)
>>  );
>
> How about add xhci_dequeue_trb for those dequeued from event ring?

Sure, and where would the tracer be? When do we "dequeue" TRBs?

> It should be helpful, if we can track the link trb as well.

right

-- 
balbi
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to