From: Felipe Balbi <felipe.balbi@linux.intel.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Linux USB <linux-usb@vger.kernel.org>
Subject: usb: gadget: functions: add ftrace export over USB
Date: Thu, 21 Mar 2019 13:25:45 +0200 [thread overview]
Message-ID: <87pnqk31vq.fsf@linux.intel.com> (raw)
hi,
Greg KH <gregkh@linuxfoundation.org> writes:
> On Thu, Mar 21, 2019 at 11:50:04AM +0200, Felipe Balbi wrote:
>> > +static struct usb_interface_descriptor ftrace_intf_desc = {
>> > + .bLength = USB_DT_INTERFACE_SIZE,
>> > + .bDescriptorType = USB_DT_INTERFACE,
>> > +
>> > + .bAlternateSetting = 0,
>> > + .bNumEndpoints = 1,
>> > + .bInterfaceClass = USB_CLASS_VENDOR_SPEC,
>> > + .bInterfaceSubClass = USB_SUBCLASS_VENDOR_SPEC,
>>
>> We *may* be able to use the USB_DEBUG_CLASS here with a vendor protocol
>> which we define to be Linux Ftrace. If folks think it would be best,
>> then I can go look at the debug class and check whether it would be
>> feasible.
>
> I didn't think that that class allowed vendor protocols, but if it does,
> sure, that would be nice.
I think it does. That spec is public, actually. Came out as part of usb
3.1. I'll review the spec tomorrow and, hopefully, resend this with
Diagnostic Class for the interface using DvC.Trace subclass and vendor
protocol.
cheers
next reply other threads:[~2019-03-21 11:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-21 11:25 Felipe Balbi [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-03-22 0:59 usb: gadget: functions: add ftrace export over USB kbuild test robot
2019-03-21 10:03 Greg Kroah-Hartman
2019-03-21 9:59 Greg Kroah-Hartman
2019-03-21 9:50 Felipe Balbi
2019-03-21 9:47 Felipe Balbi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87pnqk31vq.fsf@linux.intel.com \
--to=felipe.balbi@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-usb@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).