[Kernel-packages] [Bug 1730832] Re: [Feature] Add xHCI debug device support in the driver

2019-07-24 Thread Brad Figg
** Tags added: cscc

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1730832

Title:
  [Feature] Add xHCI debug device support in the driver

Status in intel:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released

Bug description:
  Description

  xHCI compatible USB host controllers(i.e. super-speed USB3 controllers)
  can be implemented with the Debug Capability(DbC). It presents a debug
  device which is fully compliant with the USB framework and provides the
  equivalent of a very high performance full-duplex serial link. The debug
  capability operation model and registers interface are defined in 7.6.8
  of the xHCI specification, revision 1.1.

  The DbC debug device shares a root port with the xHCI host. By default,
  the debug capability is disabled and the root port is assigned to xHCI.
  When the DbC is enabled, the root port will be assigned to the DbC debug
  device, and the xHCI sees nothing on this port. This implementation uses
  a sysfs node named  under the xHCI device to manage the enabling
  and disabling of the debug capability.

  When the debug capability is enabled, it will present a debug device
  through the debug port. This debug device is fully compliant with the
  USB3 framework, and it can be enumerated by a debug host on the other
  end of the USB link. As soon as the debug device is configured, a TTY
  serial device named /dev/ttyDBC0 will be created.

  One use of this link is running a login service on the debug target.
  Hence it can be remote accessed by a debug host. Another use case can
  probably be found in servers. It provides a peer-to-peer USB link
  between two host-only machines. This provides a reasonable out-of-band
  communication method between two servers.

  Target Kernel: 4.16
  Target Release: 18.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1730832/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1730832] Re: [Feature] Add xHCI debug device support in the driver

2019-02-14 Thread Brad Figg
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verification-needed-bionic' to 'verification-failed-
bionic'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-bionic

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1730832

Title:
  [Feature] Add xHCI debug device support in the driver

Status in intel:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released

Bug description:
  Description

  xHCI compatible USB host controllers(i.e. super-speed USB3 controllers)
  can be implemented with the Debug Capability(DbC). It presents a debug
  device which is fully compliant with the USB framework and provides the
  equivalent of a very high performance full-duplex serial link. The debug
  capability operation model and registers interface are defined in 7.6.8
  of the xHCI specification, revision 1.1.

  The DbC debug device shares a root port with the xHCI host. By default,
  the debug capability is disabled and the root port is assigned to xHCI.
  When the DbC is enabled, the root port will be assigned to the DbC debug
  device, and the xHCI sees nothing on this port. This implementation uses
  a sysfs node named  under the xHCI device to manage the enabling
  and disabling of the debug capability.

  When the debug capability is enabled, it will present a debug device
  through the debug port. This debug device is fully compliant with the
  USB3 framework, and it can be enumerated by a debug host on the other
  end of the USB link. As soon as the debug device is configured, a TTY
  serial device named /dev/ttyDBC0 will be created.

  One use of this link is running a login service on the debug target.
  Hence it can be remote accessed by a debug host. Another use case can
  probably be found in servers. It provides a peer-to-peer USB link
  between two host-only machines. This provides a reasonable out-of-band
  communication method between two servers.

  Target Kernel: 4.16
  Target Release: 18.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1730832/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1730832] Re: [Feature] Add xHCI debug device support in the driver

2019-02-14 Thread Andy Whitcroft
This bug was erroneously marked for verification in bionic; verification
is not required and verification-needed-bionic is being removed.

** Tags removed: verification-needed-bionic

** Tags added: verification-done-bionic

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1730832

Title:
  [Feature] Add xHCI debug device support in the driver

Status in intel:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released

Bug description:
  Description

  xHCI compatible USB host controllers(i.e. super-speed USB3 controllers)
  can be implemented with the Debug Capability(DbC). It presents a debug
  device which is fully compliant with the USB framework and provides the
  equivalent of a very high performance full-duplex serial link. The debug
  capability operation model and registers interface are defined in 7.6.8
  of the xHCI specification, revision 1.1.

  The DbC debug device shares a root port with the xHCI host. By default,
  the debug capability is disabled and the root port is assigned to xHCI.
  When the DbC is enabled, the root port will be assigned to the DbC debug
  device, and the xHCI sees nothing on this port. This implementation uses
  a sysfs node named  under the xHCI device to manage the enabling
  and disabling of the debug capability.

  When the debug capability is enabled, it will present a debug device
  through the debug port. This debug device is fully compliant with the
  USB3 framework, and it can be enumerated by a debug host on the other
  end of the USB link. As soon as the debug device is configured, a TTY
  serial device named /dev/ttyDBC0 will be created.

  One use of this link is running a login service on the debug target.
  Hence it can be remote accessed by a debug host. Another use case can
  probably be found in servers. It provides a peer-to-peer USB link
  between two host-only machines. This provides a reasonable out-of-band
  communication method between two servers.

  Target Kernel: 4.16
  Target Release: 18.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1730832/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1730832] Re: [Feature] Add xHCI debug device support in the driver

2019-02-14 Thread Andy Whitcroft
** Tags removed: verification-needed-bionic
** Tags added: kernel-fixup-verification-needed-bionic

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1730832

Title:
  [Feature] Add xHCI debug device support in the driver

Status in intel:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released

Bug description:
  Description

  xHCI compatible USB host controllers(i.e. super-speed USB3 controllers)
  can be implemented with the Debug Capability(DbC). It presents a debug
  device which is fully compliant with the USB framework and provides the
  equivalent of a very high performance full-duplex serial link. The debug
  capability operation model and registers interface are defined in 7.6.8
  of the xHCI specification, revision 1.1.

  The DbC debug device shares a root port with the xHCI host. By default,
  the debug capability is disabled and the root port is assigned to xHCI.
  When the DbC is enabled, the root port will be assigned to the DbC debug
  device, and the xHCI sees nothing on this port. This implementation uses
  a sysfs node named  under the xHCI device to manage the enabling
  and disabling of the debug capability.

  When the debug capability is enabled, it will present a debug device
  through the debug port. This debug device is fully compliant with the
  USB3 framework, and it can be enumerated by a debug host on the other
  end of the USB link. As soon as the debug device is configured, a TTY
  serial device named /dev/ttyDBC0 will be created.

  One use of this link is running a login service on the debug target.
  Hence it can be remote accessed by a debug host. Another use case can
  probably be found in servers. It provides a peer-to-peer USB link
  between two host-only machines. This provides a reasonable out-of-band
  communication method between two servers.

  Target Kernel: 4.16
  Target Release: 18.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1730832/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1730832] Re: [Feature] Add xHCI debug device support in the driver

2019-02-14 Thread Brad Figg
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
bionic' to 'verification-done-bionic'. If the problem still exists,
change the tag 'verification-needed-bionic' to 'verification-failed-
bionic'.

If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!


** Tags added: verification-needed-bionic

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1730832

Title:
  [Feature] Add xHCI debug device support in the driver

Status in intel:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released

Bug description:
  Description

  xHCI compatible USB host controllers(i.e. super-speed USB3 controllers)
  can be implemented with the Debug Capability(DbC). It presents a debug
  device which is fully compliant with the USB framework and provides the
  equivalent of a very high performance full-duplex serial link. The debug
  capability operation model and registers interface are defined in 7.6.8
  of the xHCI specification, revision 1.1.

  The DbC debug device shares a root port with the xHCI host. By default,
  the debug capability is disabled and the root port is assigned to xHCI.
  When the DbC is enabled, the root port will be assigned to the DbC debug
  device, and the xHCI sees nothing on this port. This implementation uses
  a sysfs node named  under the xHCI device to manage the enabling
  and disabling of the debug capability.

  When the debug capability is enabled, it will present a debug device
  through the debug port. This debug device is fully compliant with the
  USB3 framework, and it can be enumerated by a debug host on the other
  end of the USB link. As soon as the debug device is configured, a TTY
  serial device named /dev/ttyDBC0 will be created.

  One use of this link is running a login service on the debug target.
  Hence it can be remote accessed by a debug host. Another use case can
  probably be found in servers. It provides a peer-to-peer USB link
  between two host-only machines. This provides a reasonable out-of-band
  communication method between two servers.

  Target Kernel: 4.16
  Target Release: 18.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1730832/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1730832] Re: [Feature] Add xHCI debug device support in the driver

2018-04-04 Thread Leann Ogasawara
** Changed in: intel
   Status: Triaged => Fix Released

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1730832

Title:
  [Feature] Add xHCI debug device support in the driver

Status in intel:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Released

Bug description:
  Description

  xHCI compatible USB host controllers(i.e. super-speed USB3 controllers)
  can be implemented with the Debug Capability(DbC). It presents a debug
  device which is fully compliant with the USB framework and provides the
  equivalent of a very high performance full-duplex serial link. The debug
  capability operation model and registers interface are defined in 7.6.8
  of the xHCI specification, revision 1.1.

  The DbC debug device shares a root port with the xHCI host. By default,
  the debug capability is disabled and the root port is assigned to xHCI.
  When the DbC is enabled, the root port will be assigned to the DbC debug
  device, and the xHCI sees nothing on this port. This implementation uses
  a sysfs node named  under the xHCI device to manage the enabling
  and disabling of the debug capability.

  When the debug capability is enabled, it will present a debug device
  through the debug port. This debug device is fully compliant with the
  USB3 framework, and it can be enumerated by a debug host on the other
  end of the USB link. As soon as the debug device is configured, a TTY
  serial device named /dev/ttyDBC0 will be created.

  One use of this link is running a login service on the debug target.
  Hence it can be remote accessed by a debug host. Another use case can
  probably be found in servers. It provides a peer-to-peer USB link
  between two host-only machines. This provides a reasonable out-of-band
  communication method between two servers.

  Target Kernel: 4.16
  Target Release: 18.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1730832/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1730832] Re: [Feature] Add xHCI debug device support in the driver

2018-03-14 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 4.15.0-12.13

---
linux (4.15.0-12.13) bionic; urgency=medium

  * linux: 4.15.0-12.13 -proposed tracker (LP: #1754059)

  * CONFIG_EFI=y on armhf (LP: #1726362)
- [Config] CONFIG_EFI=y on armhf, reconcile secureboot EFI settings

  * ppc64el: Support firmware disable of RFI flush (LP: #1751994)
- powerpc/pseries: Support firmware disable of RFI flush
- powerpc/powernv: Support firmware disable of RFI flush

  * [Feature] CFL/CNL (PCH:CNP-H): New GPIO Commit added (GPIO Driver needed)
(LP: #1751714)
- gpio / ACPI: Drop unnecessary ACPI GPIO to Linux GPIO translation
- pinctrl: intel: Allow custom GPIO base for pad groups
- pinctrl: cannonlake: Align GPIO number space with Windows

  * [Feature] Add xHCI debug device support in the driver (LP: #1730832)
- usb: xhci: Make some static functions global
- usb: xhci: Add DbC support in xHCI driver
- [Config] USB_XHCI_DBGCAP=y for commit mainline dfba2174dc42.

  * [SRU] Lenovo E41 Mic mute hotkey is not responding (LP: #1753347)
- platform/x86: ideapad-laptop: Increase timeout to wait for EC answer

  * headset mic can't be detected on two Dell machines (LP: #1748807)
- ALSA: hda - Fix a wrong FIXUP for alc289 on Dell machines

  * hisi_sas: Add disk LED support (LP: #1752695)
- scsi: hisi_sas: directly attached disk LED feature for v2 hw

  * [Feature] [Graphics]Whiskey Lake (Coffelake-U 4+2) new PCI Device ID adds
(LP: #1742561)
- drm/i915/cfl: Adding more Coffee Lake PCI IDs.

  * [Bug] [USB Function][CFL-CNL PCH]Stall Error and USB Transaction Error in
trace, Disable of device-initiated U1/U2 failed and rebind failed: -517
during suspend/resume with usb storage. (LP: #1730599)
- usb: Don't print a warning if interface driver rebind is deferred at 
resume

  * retpoline: ignore %cs:0xNNN constant indirections (LP: #1752655)
- [Packaging] retpoline -- elide %cs:0x constants on i386
- [Config] retpoline -- clean up i386 retpoline files

  * hisilicon hibmc regression due to ea642c3216cb ("drm/ttm: add io_mem_pfn
callback") (LP: #1738334)
- drm/ttm: add ttm_bo_io_mem_pfn to check io_mem_pfn

  * [Asus UX360UA] battery status in unity-panel is not changing when battery is
being charged (LP: #1661876) // AC adapter status not detected on Asus
ZenBook UX410UAK (LP: #1745032)
- ACPI / battery: Add quirk for Asus UX360UA and UX410UAK

  * ASUS UX305LA - Battery state not detected correctly (LP: #1482390)
- ACPI / battery: Add quirk for Asus GL502VSK and UX305LA

  * [18.04 FEAT] Automatically detect layer2 setting in the qeth device driver
(LP: #1747639)
- s390/diag: add diag26c support for VNIC info
- s390/qeth: support early setup for z/VM NICs

  * Bionic update to v4.15.7 stable release (LP: #1752317)
- netfilter: drop outermost socket lock in getsockopt()
- arm64: mm: don't write garbage into TTBR1_EL1 register
- kconfig.h: Include compiler types to avoid missed struct attributes
- MIPS: boot: Define __ASSEMBLY__ for its.S build
- xtensa: fix high memory/reserved memory collision
- scsi: ibmvfc: fix misdefined reserved field in ibmvfc_fcp_rsp_info
- MIPS: Drop spurious __unused in struct compat_flock
- cfg80211: fix cfg80211_beacon_dup
- i2c: designware: must wait for enable
- i2c: bcm2835: Set up the rising/falling edge delays
- X.509: fix BUG_ON() when hash algorithm is unsupported
- X.509: fix NULL dereference when restricting key with unsupported_sig
- PKCS#7: fix certificate chain verification
- PKCS#7: fix certificate blacklisting
- extcon: int3496: process id-pin first so that we start with the right 
status
- genirq/matrix: Handle CPU offlining proper
- RDMA/uverbs: Protect from races between lookup and destroy of uobjects
- RDMA/uverbs: Protect from command mask overflow
- RDMA/uverbs: Fix bad unlock balance in ib_uverbs_close_xrcd
- RDMA/uverbs: Fix circular locking dependency
- RDMA/uverbs: Sanitize user entered port numbers prior to access it
- iio: adc: stm32: fix stm32h7_adc_enable error handling
- iio: srf08: fix link error "devm_iio_triggered_buffer_setup" undefined
- iio: buffer: check if a buffer has been set up when poll is called
- iio: adis_lib: Initialize trigger before requesting interrupt
- Kbuild: always define endianess in kconfig.h
- x86/apic/vector: Handle vector release on CPU unplug correctly
- x86/oprofile: Fix bogus GCC-8 warning in nmi_setup()
- mm, swap, frontswap: fix THP swap if frontswap enabled
- mm: don't defer struct page initialization for Xen pv guests
- uapi/if_ether.h: move __UAPI_DEF_ETHHDR libc define
- irqchip/gic-v3: Use wmb() instead of smb_wmb() in gic_raise_softirq()
- irqchip/mips-gic: Avoid spuriously handling masked interrupts
- PCI/cxgb4: Extend T3 PCI quirk to T4+ devices
- net: thunderbolt: Tear 

[Kernel-packages] [Bug 1730832] Re: [Feature] Add xHCI debug device support in the driver

2018-03-07 Thread Thadeu Lima de Souza Cascardo
** Changed in: linux (Ubuntu Bionic)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1730832

Title:
  [Feature] Add xHCI debug device support in the driver

Status in intel:
  Triaged
Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  Description

  xHCI compatible USB host controllers(i.e. super-speed USB3 controllers)
  can be implemented with the Debug Capability(DbC). It presents a debug
  device which is fully compliant with the USB framework and provides the
  equivalent of a very high performance full-duplex serial link. The debug
  capability operation model and registers interface are defined in 7.6.8
  of the xHCI specification, revision 1.1.

  The DbC debug device shares a root port with the xHCI host. By default,
  the debug capability is disabled and the root port is assigned to xHCI.
  When the DbC is enabled, the root port will be assigned to the DbC debug
  device, and the xHCI sees nothing on this port. This implementation uses
  a sysfs node named  under the xHCI device to manage the enabling
  and disabling of the debug capability.

  When the debug capability is enabled, it will present a debug device
  through the debug port. This debug device is fully compliant with the
  USB3 framework, and it can be enumerated by a debug host on the other
  end of the USB link. As soon as the debug device is configured, a TTY
  serial device named /dev/ttyDBC0 will be created.

  One use of this link is running a login service on the debug target.
  Hence it can be remote accessed by a debug host. Another use case can
  probably be found in servers. It provides a peer-to-peer USB link
  between two host-only machines. This provides a reasonable out-of-band
  communication method between two servers.

  Target Kernel: 4.16
  Target Release: 18.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1730832/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1730832] Re: [Feature] Add xHCI debug device support in the driver

2018-03-05 Thread Joseph Salisbury
https://lists.ubuntu.com/archives/kernel-team/2018-March/090558.html

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1730832

Title:
  [Feature] Add xHCI debug device support in the driver

Status in intel:
  Triaged
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  Description

  xHCI compatible USB host controllers(i.e. super-speed USB3 controllers)
  can be implemented with the Debug Capability(DbC). It presents a debug
  device which is fully compliant with the USB framework and provides the
  equivalent of a very high performance full-duplex serial link. The debug
  capability operation model and registers interface are defined in 7.6.8
  of the xHCI specification, revision 1.1.

  The DbC debug device shares a root port with the xHCI host. By default,
  the debug capability is disabled and the root port is assigned to xHCI.
  When the DbC is enabled, the root port will be assigned to the DbC debug
  device, and the xHCI sees nothing on this port. This implementation uses
  a sysfs node named  under the xHCI device to manage the enabling
  and disabling of the debug capability.

  When the debug capability is enabled, it will present a debug device
  through the debug port. This debug device is fully compliant with the
  USB3 framework, and it can be enumerated by a debug host on the other
  end of the USB link. As soon as the debug device is configured, a TTY
  serial device named /dev/ttyDBC0 will be created.

  One use of this link is running a login service on the debug target.
  Hence it can be remote accessed by a debug host. Another use case can
  probably be found in servers. It provides a peer-to-peer USB link
  between two host-only machines. This provides a reasonable out-of-band
  communication method between two servers.

  Target Kernel: 4.16
  Target Release: 18.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1730832/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1730832] Re: [Feature] Add xHCI debug device support in the driver

2018-03-02 Thread Joseph Salisbury
** Changed in: linux (Ubuntu Bionic)
   Status: Triaged => In Progress

** Changed in: linux (Ubuntu Bionic)
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Joseph 
Salisbury (jsalisbury)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1730832

Title:
  [Feature] Add xHCI debug device support in the driver

Status in intel:
  Triaged
Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  Description

  xHCI compatible USB host controllers(i.e. super-speed USB3 controllers)
  can be implemented with the Debug Capability(DbC). It presents a debug
  device which is fully compliant with the USB framework and provides the
  equivalent of a very high performance full-duplex serial link. The debug
  capability operation model and registers interface are defined in 7.6.8
  of the xHCI specification, revision 1.1.

  The DbC debug device shares a root port with the xHCI host. By default,
  the debug capability is disabled and the root port is assigned to xHCI.
  When the DbC is enabled, the root port will be assigned to the DbC debug
  device, and the xHCI sees nothing on this port. This implementation uses
  a sysfs node named  under the xHCI device to manage the enabling
  and disabling of the debug capability.

  When the debug capability is enabled, it will present a debug device
  through the debug port. This debug device is fully compliant with the
  USB3 framework, and it can be enumerated by a debug host on the other
  end of the USB link. As soon as the debug device is configured, a TTY
  serial device named /dev/ttyDBC0 will be created.

  One use of this link is running a login service on the debug target.
  Hence it can be remote accessed by a debug host. Another use case can
  probably be found in servers. It provides a peer-to-peer USB link
  between two host-only machines. This provides a reasonable out-of-band
  communication method between two servers.

  Target Kernel: 4.16
  Target Release: 18.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1730832/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1730832] Re: [Feature] Add xHCI debug device support in the driver

2018-03-02 Thread Leann Ogasawara
** Information type changed from Private to Public

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu Bionic)
   Status: New => Triaged

** Changed in: intel
   Status: Incomplete => Triaged

** Changed in: linux (Ubuntu Bionic)
   Importance: Undecided => Medium

** Changed in: intel
   Importance: Undecided => Medium

** Changed in: linux (Ubuntu Bionic)
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1730832

Title:
  [Feature] Add xHCI debug device support in the driver

Status in intel:
  Triaged
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Bionic:
  Triaged

Bug description:
  Description

  xHCI compatible USB host controllers(i.e. super-speed USB3 controllers)
  can be implemented with the Debug Capability(DbC). It presents a debug
  device which is fully compliant with the USB framework and provides the
  equivalent of a very high performance full-duplex serial link. The debug
  capability operation model and registers interface are defined in 7.6.8
  of the xHCI specification, revision 1.1.

  The DbC debug device shares a root port with the xHCI host. By default,
  the debug capability is disabled and the root port is assigned to xHCI.
  When the DbC is enabled, the root port will be assigned to the DbC debug
  device, and the xHCI sees nothing on this port. This implementation uses
  a sysfs node named  under the xHCI device to manage the enabling
  and disabling of the debug capability.

  When the debug capability is enabled, it will present a debug device
  through the debug port. This debug device is fully compliant with the
  USB3 framework, and it can be enumerated by a debug host on the other
  end of the USB link. As soon as the debug device is configured, a TTY
  serial device named /dev/ttyDBC0 will be created.

  One use of this link is running a login service on the debug target.
  Hence it can be remote accessed by a debug host. Another use case can
  probably be found in servers. It provides a peer-to-peer USB link
  between two host-only machines. This provides a reasonable out-of-band
  communication method between two servers.

  Target Kernel: 4.16
  Target Release: 18.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1730832/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp