Hi,
On 03/21/2017 07:33 PM, Ingo Molnar wrote:
>> Lu Baolu (5):
>> > x86: add simple udelay calibration
>> > usb: early: add driver for xhci debug capability
>> > x86: add support for earlyprintk via USB3 debug port
>> > usb: serial: add dbc debug device support to usb_debug
>> > usb:
Hi,
On 03/21/2017 07:33 PM, Ingo Molnar wrote:
>> Lu Baolu (5):
>> > x86: add simple udelay calibration
>> > usb: early: add driver for xhci debug capability
>> > x86: add support for earlyprintk via USB3 debug port
>> > usb: serial: add dbc debug device support to usb_debug
>> > usb:
* Greg Kroah-Hartman wrote:
> > I've applied them locally to -tip (it appears the USB maintainers are still
> > fine with this being carried in tip:x86/debug for a v4.12 merge, right?),
> > and
> > will push them out and will propagate them to linux-next as well
* Greg Kroah-Hartman wrote:
> > I've applied them locally to -tip (it appears the USB maintainers are still
> > fine with this being carried in tip:x86/debug for a v4.12 merge, right?),
> > and
> > will push them out and will propagate them to linux-next as well if they
> > pass
> >
On Tue, Mar 21, 2017 at 12:33:28PM +0100, Ingo Molnar wrote:
>
> * Lu Baolu wrote:
>
> > xHCI debug capability (DbC) is an optional but standalone
> > functionality provided by an xHCI host controller. With DbC
> > hardware initialized, the system will present a debug
On Tue, Mar 21, 2017 at 12:33:28PM +0100, Ingo Molnar wrote:
>
> * Lu Baolu wrote:
>
> > xHCI debug capability (DbC) is an optional but standalone
> > functionality provided by an xHCI host controller. With DbC
> > hardware initialized, the system will present a debug device
> > through the
* Lu Baolu wrote:
> xHCI debug capability (DbC) is an optional but standalone
> functionality provided by an xHCI host controller. With DbC
> hardware initialized, the system will present a debug device
> through the USB3 debug port (normally the first USB3 port).
>
* Lu Baolu wrote:
> xHCI debug capability (DbC) is an optional but standalone
> functionality provided by an xHCI host controller. With DbC
> hardware initialized, the system will present a debug device
> through the USB3 debug port (normally the first USB3 port).
> The debug device is fully
xHCI debug capability (DbC) is an optional but standalone
functionality provided by an xHCI host controller. With DbC
hardware initialized, the system will present a debug device
through the USB3 debug port (normally the first USB3 port).
The debug device is fully compliant with the USB framework
xHCI debug capability (DbC) is an optional but standalone
functionality provided by an xHCI host controller. With DbC
hardware initialized, the system will present a debug device
through the USB3 debug port (normally the first USB3 port).
The debug device is fully compliant with the USB framework
10 matches
Mail list logo