<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="/rss.xsl.xml"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
    <title>Changes in sysfs-bus-usb</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>12fc84e8 - usb: Export BOS descriptor to sysfs</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/Documentation/ABI/testing/sysfs-bus-usb#12fc84e8</link>
        <description>usb: Export BOS descriptor to sysfsMotivation----------The binary device object store (BOS) of a USB device consists of the BOSdescriptor followed by a set of device capability descriptors. One that isof interest to users is the platform descriptor. This contains a 128-bitUUID and arbitrary data, and it allows parties outside of USB-IF to addadditional metadata about a USB device in a standards-compliant manner.Notable examples include the WebUSB and Microsoft OS 2.0 descriptors.The kernel already retrieves and caches the BOS from USB devices if itsbcdUSB is &gt;= 0x0201. Because the BOS is flexible and extensible, we exportthe entire BOS to sysfs so users can retrieve whatever device capabilitiesthey desire, without requiring USB I/O or elevated permissions.Implementation--------------Add bos_descriptors attribute to sysfs. This is a binary file and it worksthe same way as the existing descriptors attribute. The file exists only ifthe BOS is present in the USB device.Also create a binary attribute group, so the driver core can handle thecreation of both the descriptors and bos_descriptors attributes in sysfs.Signed-off-by: Elbert Mai &lt;code@elbertmai.com&gt;Link: https://lore.kernel.org/r/20240305002301.95323-1-code@elbertmai.comSigned-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/Documentation/ABI/testing/sysfs-bus-usb</description>
        <pubDate>Tue, 05 Mar 2024 00:23:01 +0000</pubDate>
        <dc:creator>Elbert Mai &lt;code@elbertmai.com&gt;</dc:creator>
    </item>
<item>
        <title>59de2a56 - usb: typec: Link enumerated USB devices with Type-C partner</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/Documentation/ABI/testing/sysfs-bus-usb#59de2a56</link>
        <description>usb: typec: Link enumerated USB devices with Type-C partnerAdding functions that USB hub code can use to inform theType-C class about connected USB devices.Once taken into use, it will allow the Type-C port driversto power off components that are not needed, for example ifUSB2 device is enumerated, everything that is only relevantfor USB3 (retimers, etc.), can be powered off.This will also create a symlink &quot;typec&quot; for the USB devicespointing to the USB Type-C partner device.Suggested-by: Benson Leung &lt;bleung@chromium.org&gt;Tested-by: Benson Leung &lt;bleung@chromium.org&gt;Signed-off-by: Heikki Krogerus &lt;heikki.krogerus@linux.intel.com&gt;Link: https://lore.kernel.org/r/20231011105825.320062-2-heikki.krogerus@linux.intel.comSigned-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/Documentation/ABI/testing/sysfs-bus-usb</description>
        <pubDate>Wed, 11 Oct 2023 10:58:24 +0000</pubDate>
        <dc:creator>Heikki Krogerus &lt;heikki.krogerus@linux.intel.com&gt;</dc:creator>
    </item>
<item>
        <title>f176638a - USB: Remove Wireless USB and UWB documentation</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/Documentation/ABI/testing/sysfs-bus-usb#f176638a</link>
        <description>USB: Remove Wireless USB and UWB documentationSupport for Wireless USB and Ultra WideBand was removed in 2020 bycommit caa6772db4c1 (&quot;Staging: remove wusbcore and UWB from the kerneltree.&quot;).  But the documentation files were left behind.Let&apos;s get rid of that out-of-date documentation.Signed-off-by: Alan Stern &lt;stern@rowland.harvard.edu&gt;Link: https://lore.kernel.org/r/015d4310-bcd3-4ba4-9a0e-3664f281a9be@rowland.harvard.eduSigned-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/Documentation/ABI/testing/sysfs-bus-usb</description>
        <pubDate>Wed, 09 Aug 2023 00:44:35 +0000</pubDate>
        <dc:creator>Alan Stern &lt;stern@rowland.harvard.edu&gt;</dc:creator>
    </item>
<item>
        <title>83cb2604 - usb: core: add sysfs entry for usb device state</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/Documentation/ABI/testing/sysfs-bus-usb#83cb2604</link>
        <description>usb: core: add sysfs entry for usb device stateExpose usb device state to userland as the information is useful indetecting non-compliant setups and diagnosing enumeration failures.For example:- End-to-end signal integrity issues: the device would fail port reset  repeatedly and thus be stuck in POWERED state.- Charge-only cables (missing D+/D- lines): the device would never enter  POWERED state as the HC would not see any pullup.What&apos;s the status quo?We do have error logs such as &quot;Cannot enable. Maybe the USB cable is bad?&quot;to flag potential setup issues, but there&apos;s no good way to expose them touserspace.Why add a sysfs entry in struct usb_port instead of struct usb_device?The struct usb_device is not device_add() to the system until it&apos;s inADDRESS state hence we would miss the first two states. The structusb_port is a better place to keep the information because its lifecycle is longer than the struct usb_device that is attached to the port.Reported-by: kernel test robot &lt;oliver.sang@intel.com&gt;Closes: https://lore.kernel.org/oe-lkp/202306042228.e532af6e-oliver.sang@intel.comReviewed-by: Alan Stern &lt;stern@rowland.harvard.edu&gt;Signed-off-by: Roy Luo &lt;royluo@google.com&gt;Message-ID: &lt;20230608015913.1679984-1-royluo@google.com&gt;Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/Documentation/ABI/testing/sysfs-bus-usb</description>
        <pubDate>Thu, 08 Jun 2023 01:59:12 +0000</pubDate>
        <dc:creator>Roy Luo &lt;royluo@google.com&gt;</dc:creator>
    </item>
<item>
        <title>f98e0640 - USB: core: Add wireless_status sysfs attribute</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/Documentation/ABI/testing/sysfs-bus-usb#f98e0640</link>
        <description>USB: core: Add wireless_status sysfs attributeAdd a wireless_status sysfs attribute to USB devices to keep track ofwhether a USB device that&apos;s comprised of a receiver dongle and an emitterdevice over a, most of the time proprietary, wireless link has its emitterconnected or disconnected.This will be used by user-space OS components to determine whether thebattery-powered part of the device is wirelessly connected or not,allowing, for example:- upower to hide the battery for devices where the device is turned off  but the receiver plugged in, rather than showing 0%, or other values  that could be confusing to users- Pipewire to hide a headset from the list of possible inputs or outputs  or route audio appropriately if the headset is suddenly turned off, or  turned on- libinput to determine whether a keyboard or mouse is present when its  receiver is plugged in.This is done at the USB interface level as:- the interface on which the wireless status is detected is sometimes  not the same as where it could be consumed (eg. the audio interface  on a headset dongle will still appear even if the headset is turned  off), and we cannot have synchronisation of status across subsystems.- this behaviour is not specific to HID devices, even if the protocols  used to determine whether or not the remote device is connected can  be HID.This is not an attribute that is meant to replace protocol specificAPIs, such as the ones available for WWAN, WLAN/Wi-Fi, or Bluetoothor any other sort of networking, but solely for wireless devices withan ad-hoc &#8220;lose it and your device is e-waste&#8221; receiver dongle.The USB interface will only be exporting the wireless_status sysfsattribute if it gets set through the API exported in the next commit.Signed-off-by: Bastien Nocera &lt;hadess@hadess.net&gt;Acked-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;Acked-by: Alan Stern &lt;stern@rowland.harvard.edu&gt;Link: https://lore.kernel.org/r/20230302105555.51417-4-hadess@hadess.netSigned-off-by: Benjamin Tissoires &lt;benjamin.tissoires@redhat.com&gt;

            List of files:
            /linux-6.15/Documentation/ABI/testing/sysfs-bus-usb</description>
        <pubDate>Thu, 02 Mar 2023 10:55:53 +0000</pubDate>
        <dc:creator>Bastien Nocera &lt;hadess@hadess.net&gt;</dc:creator>
    </item>
<item>
        <title>430d57f5 - usb: core: stop USB enumeration if too many retries</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/Documentation/ABI/testing/sysfs-bus-usb#430d57f5</link>
        <description>usb: core: stop USB enumeration if too many retriesWhen a broken USB accessory connects to a USB host, usbcore mightkeep doing enumeration retries. If the host has a watchdog mechanism,the kernel panic will happen on the host.This patch provides an attribute early_stop to limit the numbers of retriesfor each port of a hub. If a port was marked with early_stop attribute,unsuccessful connection attempts will fail quickly. In addition, if anearly_stop port has failed to initialize, it will ignore all futureconnection events until early_stop attribute is clear.Signed-off-by: Ray Chi &lt;raychi@google.com&gt;Reviewed-by: Alan Stern &lt;stern@rowland.harvard.edu&gt;Link: https://lore.kernel.org/r/20221107072754.3336357-1-raychi@google.comSigned-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/Documentation/ABI/testing/sysfs-bus-usb</description>
        <pubDate>Mon, 07 Nov 2022 07:27:54 +0000</pubDate>
        <dc:creator>Ray Chi &lt;raychi@google.com&gt;</dc:creator>
    </item>
<item>
        <title>f061f43d - usb: hub: port: add sysfs entry to switch port power</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/Documentation/ABI/testing/sysfs-bus-usb#f061f43d</link>
        <description>usb: hub: port: add sysfs entry to switch port powerIn some cases the port of an hub needs to be disabled or switched offand on again. E.g. when the connected device needs to be re-enumerated.Or it needs to be explicitly disabled while the rest of the usb treestays working.For this purpose this patch adds an sysfs switch to enable/disable theport on any hub. In the case the hub is supporting power switching, thepower line will be disabled to the connected device.When the port gets disabled, the associated device gets disconnected andremoved from the logical usb tree. No further device will be enumeratedon that port until the port gets enabled again.Reviewed-by: Alan Stern &lt;stern@rowland.harvard.edu&gt;Signed-off-by: Michael Grzeschik &lt;m.grzeschik@pengutronix.de&gt;Link: https://lore.kernel.org/r/20220607114522.3359148-1-m.grzeschik@pengutronix.deSigned-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/Documentation/ABI/testing/sysfs-bus-usb</description>
        <pubDate>Tue, 07 Jun 2022 11:45:22 +0000</pubDate>
        <dc:creator>Michael Grzeschik &lt;m.grzeschik@pengutronix.de&gt;</dc:creator>
    </item>
<item>
        <title>8c67d06f - usb: Link the ports to the connectors they are attached to</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/Documentation/ABI/testing/sysfs-bus-usb#8c67d06f</link>
        <description>usb: Link the ports to the connectors they are attached toCreating link to the USB Type-C connector for every new portthat is added when possible.Reviewed-by: Andy Shevchenko &lt;andriy.shevchenko@linux.intel.com&gt;Acked-by: Rafael J. Wysocki &lt;rafael.j.wysocki@intel.com&gt;Signed-off-by: Heikki Krogerus &lt;heikki.krogerus@linux.intel.com&gt;Link: https://lore.kernel.org/r/20211223082349.45616-1-heikki.krogerus@linux.intel.comSigned-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/Documentation/ABI/testing/sysfs-bus-usb</description>
        <pubDate>Thu, 23 Dec 2021 08:23:49 +0000</pubDate>
        <dc:creator>Heikki Krogerus &lt;heikki.krogerus@linux.intel.com&gt;</dc:creator>
    </item>
<item>
        <title>989eff9c - ABI: sysfs-bus-usb: add missing sysfs fields</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/Documentation/ABI/testing/sysfs-bus-usb#989eff9c</link>
        <description>ABI: sysfs-bus-usb: add missing sysfs fieldsThere are lots of interface, power and endpoint properties that are currentlymissing any documentation.Add a description for them.Signed-off-by: Mauro Carvalho Chehab &lt;mchehab+huawei@kernel.org&gt;Link: https://lore.kernel.org/r/7f6f7b955032836546f78a9041b22c10b6f4bc5b.1632750608.git.mchehab+huawei@kernel.orgSigned-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/Documentation/ABI/testing/sysfs-bus-usb</description>
        <pubDate>Mon, 27 Sep 2021 13:59:47 +0000</pubDate>
        <dc:creator>Mauro Carvalho Chehab &lt;mchehab+huawei@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>e06ab8d5 - ABI: sysfs-bus-usb: use a wildcard for interface name on What</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/Documentation/ABI/testing/sysfs-bus-usb#e06ab8d5</link>
        <description>ABI: sysfs-bus-usb: use a wildcard for interface name on WhatUse &lt;INTERFACE&gt; instead of INTERFACE, in order for the get_abi.plscript to be able to identify this as a wildcard.Signed-off-by: Mauro Carvalho Chehab &lt;mchehab+huawei@kernel.org&gt;Link: https://lore.kernel.org/r/cec7048385b6a4779894e19af681226e60f4d8b9.1632750608.git.mchehab+huawei@kernel.orgSigned-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/Documentation/ABI/testing/sysfs-bus-usb</description>
        <pubDate>Mon, 27 Sep 2021 13:59:46 +0000</pubDate>
        <dc:creator>Mauro Carvalho Chehab &lt;mchehab+huawei@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>3628f573 - ABI: sysfs-bus-usb: better document variable argument</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/Documentation/ABI/testing/sysfs-bus-usb#3628f573</link>
        <description>ABI: sysfs-bus-usb: better document variable argumentOn almost all ABI documents, variable arguments are declaredas &lt;foo_bar&gt;. Change it here too, in order to allow replacingsuch wildcards by regexes on a scriptable way.Acked-by: Heikki Krogerus &lt;heikki.krogerus@linux.intel.com&gt;Acked-by: Rajat Jain &lt;rajatja@google.com&gt;Acked-by: Bjorn Helgaas &lt;bhelgaas@google.com&gt;Signed-off-by: Mauro Carvalho Chehab &lt;mchehab+huawei@kernel.org&gt;Link: https://lore.kernel.org/r/2f7e4e874677dbd82693a6b219decefa18802e8f.1631782432.git.mchehab+huawei@kernel.orgSigned-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/Documentation/ABI/testing/sysfs-bus-usb</description>
        <pubDate>Thu, 16 Sep 2021 08:59:28 +0000</pubDate>
        <dc:creator>Mauro Carvalho Chehab &lt;mchehab+huawei@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>70f400d4 - driver core: Move the &quot;removable&quot; attribute from USB to core</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/Documentation/ABI/testing/sysfs-bus-usb#70f400d4</link>
        <description>driver core: Move the &quot;removable&quot; attribute from USB to coreMove the &quot;removable&quot; attribute from USB to core in order to allow it to besupported by other subsystem / buses. Individual buses that want to supportthis attribute can populate the removable property of the device whileenumerating it with the 3 possible values - - &quot;unknown&quot; - &quot;fixed&quot; - &quot;removable&quot;Leaving the field unchanged (i.e. &quot;not supported&quot;) would mean that theattribute would not show up in sysfs for that device. The UAPI (location,symantics etc) for the attribute remains unchanged.Move the &quot;removable&quot; attribute from USB to the device core so it can beused by other subsystems / buses.By default, devices do not have a &quot;removable&quot; attribute in sysfs.If a subsystem or bus driver wants to support a &quot;removable&quot; attribute, itshould call device_set_removable() before calling device_register() ordevice_add(), e.g.:    device_set_removable(dev, DEVICE_REMOVABLE);    device_register(dev);The possible values and the resulting sysfs attribute contents are:    DEVICE_REMOVABLE_UNKNOWN  -&gt;  &quot;unknown&quot;    DEVICE_REMOVABLE          -&gt;  &quot;removable&quot;    DEVICE_FIXED              -&gt;  &quot;fixed&quot;Convert the USB &quot;removable&quot; attribute to use this new device corefunctionality.  There should be no user-visible change in the location orsemantics of attribute for USB devices.Reviewed-by: Bjorn Helgaas &lt;bhelgaas@google.com&gt;Signed-off-by: Rajat Jain &lt;rajatja@google.com&gt;Link: https://lore.kernel.org/r/20210524171812.18095-1-rajatja@google.comSigned-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/Documentation/ABI/testing/sysfs-bus-usb</description>
        <pubDate>Mon, 24 May 2021 17:18:11 +0000</pubDate>
        <dc:creator>Rajat Jain &lt;rajatja@google.com&gt;</dc:creator>
    </item>
<item>
        <title>5bdb080f - Revert &quot;usb: Link the ports to the connectors they are attached to&quot;</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/Documentation/ABI/testing/sysfs-bus-usb#5bdb080f</link>
        <description>Revert &quot;usb: Link the ports to the connectors they are attached to&quot;This reverts commit 63cd78617350dae99cc5fbd8f643b83ee819fe33 as itcauses a build error:	depmod: ERROR: Cycle detected: usbcore -&gt; typec -&gt; usbcore	depmod: ERROR: Found 2 modules in dependency cycles!Reported-by: Stephen Rothwell &lt;sfr@canb.auug.org.au&gt;Link: https://lore.kernel.org/r/20210412213655.3776e15e@canb.auug.org.auCc: Heikki Krogerus &lt;heikki.krogerus@linux.intel.com&gt;Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/Documentation/ABI/testing/sysfs-bus-usb</description>
        <pubDate>Mon, 12 Apr 2021 12:36:02 +0000</pubDate>
        <dc:creator>Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;</dc:creator>
    </item>
<item>
        <title>63cd7861 - usb: Link the ports to the connectors they are attached to</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/Documentation/ABI/testing/sysfs-bus-usb#63cd7861</link>
        <description>usb: Link the ports to the connectors they are attached toCreating link to the USB Type-C connector for every new portthat is added when possible.Signed-off-by: Heikki Krogerus &lt;heikki.krogerus@linux.intel.com&gt;Link: https://lore.kernel.org/r/20210407065555.88110-3-heikki.krogerus@linux.intel.comSigned-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/Documentation/ABI/testing/sysfs-bus-usb</description>
        <pubDate>Wed, 07 Apr 2021 06:55:53 +0000</pubDate>
        <dc:creator>Heikki Krogerus &lt;heikki.krogerus@linux.intel.com&gt;</dc:creator>
    </item>
<item>
        <title>54a19b4d - docs: ABI: cleanup several ABI documents</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/Documentation/ABI/testing/sysfs-bus-usb#54a19b4d</link>
        <description>docs: ABI: cleanup several ABI documentsThere are some ABI documents that, while they don&apos;t generateany warnings, they have issues when parsed by get_abi.pl scripton its output result.Address them, in order to provide a clean output.Reviewed-by: Tom Rix &lt;trix@redhat.com&gt; # for fpga-managerReviewed-By: Kajol Jain&lt;kjain@linux.ibm.com&gt; # for sysfs-bus-event_source-devices-hv_gpci and sysfs-bus-event_source-devices-hv_24x7Acked-by: Jonathan Cameron &lt;Jonathan.Cameron@huawei.com&gt; #for IIOAcked-by: Oded Gabbay &lt;oded.gabbay@gmail.com&gt; # for HabanalabsAcked-by: Vaibhav Jain &lt;vaibhav@linux.ibm.com&gt; # for sysfs-bus-papr-pmemAcked-by: Cezary Rojewski &lt;cezary.rojewski@intel.com&gt; # for catptAcked-by: Suzuki K Poulose &lt;suzuki.poulose@arm.com&gt;Acked-by: Ilya Dryomov &lt;idryomov@gmail.com&gt; # for rbdAcked-by: Jonathan Corbet &lt;corbet@lwn.net&gt;Signed-off-by: Mauro Carvalho Chehab &lt;mchehab+huawei@kernel.org&gt;Link: https://lore.kernel.org/r/5bc78e5b68ed1e9e39135173857cb2e753be868f.1604042072.git.mchehab+huawei@kernel.orgSigned-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/Documentation/ABI/testing/sysfs-bus-usb</description>
        <pubDate>Fri, 30 Oct 2020 07:40:50 +0000</pubDate>
        <dc:creator>Mauro Carvalho Chehab &lt;mchehab+huawei@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>34433332 - docs: ABI: testing: make the files compatible with ReST output</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/Documentation/ABI/testing/sysfs-bus-usb#34433332</link>
        <description>docs: ABI: testing: make the files compatible with ReST outputSome files over there won&apos;t parse well by Sphinx.Fix them.Acked-by: Jonathan Cameron &lt;Jonathan.Cameron@huawei.com&gt; # for IIOAcked-by: Fabrice Gasnier &lt;fabrice.gasnier@st.com&gt;Acked-by: Jonathan Corbet &lt;corbet@lwn.net&gt;Signed-off-by: Mauro Carvalho Chehab &lt;mchehab+huawei@kernel.org&gt;Link: https://lore.kernel.org/r/58cf3c2d611e0197fb215652719ebd82ca2658db.1604042072.git.mchehab+huawei@kernel.orgSigned-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/Documentation/ABI/testing/sysfs-bus-usb</description>
        <pubDate>Fri, 30 Oct 2020 07:40:39 +0000</pubDate>
        <dc:creator>Mauro Carvalho Chehab &lt;mchehab+huawei@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>68f1ec8e - usb: Change &quot;wired&quot; to &quot;hardwired&quot; for connect_type</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/Documentation/ABI/testing/sysfs-bus-usb#68f1ec8e</link>
        <description>usb: Change &quot;wired&quot; to &quot;hardwired&quot; for connect_typeThe sysfs documentation for /sys/bus/usb/.../portX/connect_type has oneof the possible values listed as &quot;wired&quot; when the actual value should be&quot;hardwired&quot;.Changes the ABI documentation for connect_type to match the strings inport.c.Signed-off-by: Jon Flatley &lt;jflat@chromium.org&gt;Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/Documentation/ABI/testing/sysfs-bus-usb</description>
        <pubDate>Fri, 01 Feb 2019 21:55:07 +0000</pubDate>
        <dc:creator>Jon Flatley &lt;jflat@chromium.org&gt;</dc:creator>
    </item>
<item>
        <title>355c74e5 - usb: export firmware port location in sysfs</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/Documentation/ABI/testing/sysfs-bus-usb#355c74e5</link>
        <description>usb: export firmware port location in sysfsThe platform firmware &quot;location&quot; data is used to find port peerrelationships. But firmware is an unreliable source, and there arereal world examples of errors leading to missing or wrong peerrelationships.  Debugging this is currently hard.Exporting the location attribute makes it easier to spot mismatchesbetween the firmware data and the real world.Signed-off-by: Bj&#248;rn Mork &lt;bjorn@mork.no&gt;Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/Documentation/ABI/testing/sysfs-bus-usb</description>
        <pubDate>Fri, 28 Sep 2018 13:40:31 +0000</pubDate>
        <dc:creator>Bj&#248;rn Mork &lt;bjorn@mork.no&gt;</dc:creator>
    </item>
<item>
        <title>201af55d - usb: core: added uevent for over-current</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/Documentation/ABI/testing/sysfs-bus-usb#201af55d</link>
        <description>usb: core: added uevent for over-currentAfter commit 1cbd53c8cd85 (&quot;usb: core: introduce per-port over-currentcounters&quot;) usb ports expose a sysfs value &apos;over_current_count&apos;to user space. This value on its own is not very useful as it requiresmanual polling.As a solution, fire a udev event from the usb hub device that specifiesthe values &apos;OVER_CURRENT_PORT&apos; and &apos;OVER_CURRENT_COUNT&apos; that indicatethe path of the usb port where the over-current event occurred and thevalue of &apos;over_current_count&apos; in sysfs. Additionally, callsysfs_notify() so the sysfs value supports poll().Signed-off-by: Jon Flatley &lt;jflat@chromium.org&gt;Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/Documentation/ABI/testing/sysfs-bus-usb</description>
        <pubDate>Thu, 20 Sep 2018 17:17:54 +0000</pubDate>
        <dc:creator>Jon Flatley &lt;jflat@chromium.org&gt;</dc:creator>
    </item>
<item>
        <title>aa071a92 - usb: hub: Per-port setting to reduce TRSTRCY to 10 ms</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/Documentation/ABI/testing/sysfs-bus-usb#aa071a92</link>
        <description>usb: hub: Per-port setting to reduce TRSTRCY to 10 msCurrently, the USB hub core waits for 50 ms after enumerating thedevice. This was added to help &quot;some high speed devices&quot; toenumerate (b789696af8 &quot;[PATCH] USB: relax usbcore reset timings&quot;).On some devices, the time-to-active is important, so we providea per-port option to reduce the time to what the USB specificationrequires: 10 ms.Signed-off-by: Nicolas Boichat &lt;drinkcat@chromium.org&gt;Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/Documentation/ABI/testing/sysfs-bus-usb</description>
        <pubDate>Mon, 28 May 2018 06:32:19 +0000</pubDate>
        <dc:creator>Nicolas Boichat &lt;drinkcat@chromium.org&gt;</dc:creator>
    </item>
</channel>
</rss>
