[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20151103094239.GA6143@dhcp-128-100.nay.redhat.com>
Date: Tue, 3 Nov 2015 17:42:39 +0800
From: Dave Young <dyoung@...hat.com>
To: Lu Baolu <baolu.lu@...ux.intel.com>
Cc: Mathias Nyman <mathias.nyman@...el.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Alan Stern <stern@...land.harvard.edu>,
linux-usb@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 00/12] usb: early: add support for early printk through
USB3 debug port
On 10/28/15 at 04:00pm, Lu Baolu wrote:
> This patch series adds support for early printk through USB3 debug port.
> USB3 debug port is described in xHCI specification as an optional extended
> capability.
>
> The first patch adds a file in debugfs, through which users can check
> whether the debug capability is supported by a specific host controller.
>
> Patch 2 to 10 add the driver for xHCI debug capability. It interfaces with
> the register set and provides the required ops (read/write/control) to upper
> layers. Early printk is one consumer of these ops. The hooks for early printk
> are introduced in patch 9. This design is similar to what we have done in
> drivers/usb/early/ehci-dbgp.c.
>
> Patch 11 is a minor change to usb_debug module. This change is required to
> bind usb_debug with the USB3 debug device.
>
> Patch 12 is the design document and user guide.
>
Nice work, I want to try your patches. But I have only one machine with
debug capability, I think I can use it as debug target. Can I use another
machine with usb 3.0 but no debug capability as the debug host?
BTW, I hacked a cable according to usb 3 spec, cut vbus/d+/d-, cross wired
ss pins.
Thanks
Dave
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists