Home
last modified time | relevance | path

Searched hist:"355 c74e5" (Results 1 – 2 of 2) sorted by relevance

/openbmc/linux/Documentation/ABI/testing/
H A Dsysfs-bus-usb355c74e5 Fri Sep 28 08:40:31 CDT 2018 Bjørn Mork <bjorn@mork.no> usb: export firmware port location in sysfs

The platform firmware "location" data is used to find port peer
relationships. But firmware is an unreliable source, and there are
real world examples of errors leading to missing or wrong peer
relationships. Debugging this is currently hard.

Exporting the location attribute makes it easier to spot mismatches
between the firmware data and the real world.

Signed-off-by: Bjørn Mork <bjorn@mork.no>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
355c74e5 Fri Sep 28 08:40:31 CDT 2018 Bjørn Mork <bjorn@mork.no> usb: export firmware port location in sysfs

The platform firmware "location" data is used to find port peer
relationships. But firmware is an unreliable source, and there are
real world examples of errors leading to missing or wrong peer
relationships. Debugging this is currently hard.

Exporting the location attribute makes it easier to spot mismatches
between the firmware data and the real world.

Signed-off-by: Bjørn Mork <bjorn@mork.no>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
/openbmc/linux/drivers/usb/core/
H A Dport.c355c74e5 Fri Sep 28 08:40:31 CDT 2018 Bjørn Mork <bjorn@mork.no> usb: export firmware port location in sysfs

The platform firmware "location" data is used to find port peer
relationships. But firmware is an unreliable source, and there are
real world examples of errors leading to missing or wrong peer
relationships. Debugging this is currently hard.

Exporting the location attribute makes it easier to spot mismatches
between the firmware data and the real world.

Signed-off-by: Bjørn Mork <bjorn@mork.no>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
355c74e5 Fri Sep 28 08:40:31 CDT 2018 Bjørn Mork <bjorn@mork.no> usb: export firmware port location in sysfs

The platform firmware "location" data is used to find port peer
relationships. But firmware is an unreliable source, and there are
real world examples of errors leading to missing or wrong peer
relationships. Debugging this is currently hard.

Exporting the location attribute makes it easier to spot mismatches
between the firmware data and the real world.

Signed-off-by: Bjørn Mork <bjorn@mork.no>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>