Changes in Makefile

31e7f6c0 - usb: misc: onboard_hub: rename to onboard_dev

Mon, 25 Mar 2024 09:15:12 +0000

usb: misc: onboard_hub: rename to onboard_devThis patch prepares onboad_hub to support non-hub devices by renamingthe driver files and their content, the headers and their references.The comments and descriptions have been slightly modified to keepcoherence and account for the specific cases that only affect onboardhubs (e.g. peer-hub).The "hub" variables in functions where "dev" (and similar names) variablesalready exist have been renamed to onboard_dev for clarity, which adds afew lines in cases where more than 80 characters are used.No new functionality has been added.Acked-by: Matthias Kaehlcke Signed-off-by: Javier Carrasco Link: https://lore.kernel.org/r/20240325-onboard_xvf3500-v8-2-29e3f9222922@wolfvision.netSigned-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/usb/misc/Makefile

acd6199f - usb: Add support for Intel LJCA device

Mon, 09 Oct 2023 06:33:22 +0000

usb: Add support for Intel LJCA deviceImplements the USB part of Intel USB-I2C/GPIO/SPI adapter devicenamed "La Jolla Cove Adapter" (LJCA).The communication between the various LJCA module drivers and thehardware will be muxed/demuxed by this driver. Three modules (I2C, GPIO, and SPI) are supported currently.Each sub-module of LJCA device is identified by type field withinthe LJCA message header.The sub-modules of LJCA can use ljca_transfer() to issue a transferbetween host and hardware. And ljca_register_event_cb is exportedto LJCA sub-module drivers for hardware event subscription.The minimum code in ASL that covers this board isScope (\_SB.PCI0.DWC3.RHUB.HS01) { Device (GPIO) { Name (_ADR, Zero) Name (_STA, 0x0F) } Device (I2C) { Name (_ADR, One) Name (_STA, 0x0F) } Device (SPI) { Name (_ADR, 0x02) Name (_STA, 0x0F) } }Signed-off-by: Wentong Wu Reviewed-by: Sakari Ailus Reviewed-by: Andi Shyti Tested-by: Hans de Goede Reviewed-by: Oliver Neukum Link: https://lore.kernel.org/r/1696833205-16716-2-git-send-email-wentong.wu@intel.comSigned-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/usb/misc/Makefile

8be17483 - usb: ftdi-elan: Delete driver

Tue, 21 Mar 2023 15:09:19 +0000

usb: ftdi-elan: Delete driverThis driver didn't see real maintainance since several years. It hasseveral trivial issues (check $(scripts/checkpatch.pl -fdrivers/usb/misc/ftdi-elan.c)) and some harder ones (difficult locking,explict kref handling, ...). Also today it's hard to find hardware tomake actually use of such a card and I suspect the driver is completelyunused.So remove it.Signed-off-by: Uwe Kleine-König Link: https://lore.kernel.org/r/20230321150919.351947-1-u.kleine-koenig@pengutronix.deSigned-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/usb/misc/Makefile

8bc06364 - usb: misc: Add onboard_usb_hub driver

Thu, 30 Jun 2022 19:35:29 +0000

usb: misc: Add onboard_usb_hub driverThe main issue this driver addresses is that a USB hub needs to bepowered before it can be discovered. For discrete onboard hubs (anexample for such a hub is the Realtek RTS5411) this is often solvedby supplying the hub with an 'always-on' regulator, which is kindof a hack. Some onboard hubs may require further initializationsteps, like changing the state of a GPIO or enabling a clock, whichrequires even more hacks. This driver creates a platform devicerepresenting the hub which performs the necessary initialization.Currently it only supports switching on a single regulator, supportfor multiple regulators or other actions can be added as needed.Different initialization sequences can be supported based on thecompatible string.Besides performing the initialization the driver can be configuredto power the hub off during system suspend. This can help to extendbattery life on battery powered devices which have no requirementsto keep the hub powered during suspend. The driver can also beconfigured to leave the hub powered when a wakeup capable USB deviceis connected when suspending, and power it off otherwise.Technically the driver consists of two drivers, the platform driverdescribed above and a very thin USB driver that subclasses thegeneric driver. The purpose of this driver is to provide the platformdriver with the USB devices corresponding to the hub(s) (a hubcontroller may provide multiple 'logical' hubs, e.g. one to supportUSB 2.0 and another for USB 3.x).Co-developed-by: Ravi Chandra Sadineni Reviewed-by: Douglas Anderson Signed-off-by: Ravi Chandra Sadineni Signed-off-by: Matthias Kaehlcke Link: https://lore.kernel.org/r/20220630123445.v24.3.I7c9a1f1d6ced41dd8310e8a03da666a32364e790@changeidSigned-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/usb/misc/Makefile

67a7570a - Revert "usb: misc: Add onboard_usb_hub driver"

Tue, 03 May 2022 14:44:11 +0000

Revert "usb: misc: Add onboard_usb_hub driver"This reverts commit 0298b4b95cb373c21e6323c905589f8dac42c5b4.The series still has built errors as reported in linux-next, so revertit for now.Reported-by: Stephen Rothwell Link: https://lore.kernel.org/r/20220502210728.0b36f3cd@canb.auug.org.auCc: Alan Stern Cc: Douglas Anderson Cc: Matthias Kaehlcke Cc: Ravi Chandra Sadineni Cc: Stephen Boyd Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/usb/misc/Makefile

0298b4b9 - usb: misc: Add onboard_usb_hub driver

Thu, 17 Feb 2022 18:42:53 +0000

usb: misc: Add onboard_usb_hub driverThe main issue this driver addresses is that a USB hub needs to bepowered before it can be discovered. For discrete onboard hubs (anexample for such a hub is the Realtek RTS5411) this is often solvedby supplying the hub with an 'always-on' regulator, which is kindof a hack. Some onboard hubs may require further initializationsteps, like changing the state of a GPIO or enabling a clock, whichrequires even more hacks. This driver creates a platform devicerepresenting the hub which performs the necessary initialization.Currently it only supports switching on a single regulator, supportfor multiple regulators or other actions can be added as needed.Different initialization sequences can be supported based on thecompatible string.Besides performing the initialization the driver can be configuredto power the hub off during system suspend. This can help to extendbattery life on battery powered devices which have no requirementsto keep the hub powered during suspend. The driver can also beconfigured to leave the hub powered when a wakeup capable USB deviceis connected when suspending, and power it off otherwise.Technically the driver consists of two drivers, the platform driverdescribed above and a very thin USB driver that subclasses thegeneric driver. The purpose of this driver is to provide the platformdriver with the USB devices corresponding to the hub(s) (a hubcontroller may provide multiple 'logical' hubs, e.g. one to supportUSB 2.0 and another for USB 3.x).Note: the current series only supports hubs connected directly toa root hub, support for other configurations could be added ifneeded.Co-developed-by: Ravi Chandra Sadineni Reviewed-by: Douglas Anderson Acked-by: Alan Stern Signed-off-by: Ravi Chandra Sadineni Signed-off-by: Matthias Kaehlcke Link: https://lore.kernel.org/r/20220217104219.v21.2.I7c9a1f1d6ced41dd8310e8a03da666a32364e790@changeidSigned-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/usb/misc/Makefile

9a1bf58c - usb: misc: eud: Add driver support for Embedded USB Debugger(EUD)

Tue, 08 Feb 2022 17:54:26 +0000

usb: misc: eud: Add driver support for Embedded USB Debugger(EUD)Add support for control peripheral of EUD (Embedded USB Debugger) tolisten to events such as USB attach/detach, pet EUD to indicate softwareis functional.Reusing the platform device kobj, sysfs entry 'enable' iscreated to enable or disable EUD.To enable the eud the following needs to be doneecho 1 > /sys/bus/platform/.../enableTo disable eud, following is the commandecho 0 > /sys/bus/platform/.../enableSigned-off-by: Souradeep Chowdhury Link: https://lore.kernel.org/r/0ac5c2b2c8e4ce4f4f342a08b48cfc61aeaf7ee8.1644339918.git.quic_schowdhu@quicinc.comSigned-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/usb/misc/Makefile

04d72afa - Revert "USB: misc: Add onboard_usb_hub driver"

Fri, 18 Jun 2021 06:39:24 +0000

Revert "USB: misc: Add onboard_usb_hub driver"This reverts commit b4e326165e21d6a11483f6a4de2174b933413554 as thepatch series is causing build issues in linux-next at the moment.Cc: Matthias Kaehlcke Link: https://lore.kernel.org/r/YMuRcrE8xlWnFSWW@google.comSigned-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/usb/misc/Makefile

b4e32616 - USB: misc: Add onboard_usb_hub driver

Wed, 09 Jun 2021 22:02:46 +0000

USB: misc: Add onboard_usb_hub driverThe main issue this driver addresses is that a USB hub needs to bepowered before it can be discovered. For discrete onboard hubs (anexample for such a hub is the Realtek RTS5411) this is often solvedby supplying the hub with an 'always-on' regulator, which is kindof a hack. Some onboard hubs may require further initializationsteps, like changing the state of a GPIO or enabling a clock, whichrequires even more hacks. This driver creates a platform devicerepresenting the hub which performs the necessary initialization.Currently it only supports switching on a single regulator, supportfor multiple regulators or other actions can be added as needed.Different initialization sequences can be supported based on thecompatible string.Besides performing the initialization the driver can be configuredto power the hub off during system suspend. This can help to extendbattery life on battery powered devices which have no requirementsto keep the hub powered during suspend. The driver can also beconfigured to leave the hub powered when a wakeup capable USB deviceis connected when suspending, and power it off otherwise.Technically the driver consists of two drivers, the platform driverdescribed above and a very thin USB driver that subclasses thegeneric driver. The purpose of this driver is to provide the platformdriver with the USB devices corresponding to the hub(s) (a hubcontroller may provide multiple 'logical' hubs, e.g. one to supportUSB 2.0 and another for USB 3.x).Note: the current series only supports hubs connected directly toa root hub (through xhci-plat), support for other configurationscould be added if needed.Co-developed-by: Ravi Chandra Sadineni Acked-by: Alan Stern Signed-off-by: Ravi Chandra Sadineni Signed-off-by: Matthias Kaehlcke Link: https://lore.kernel.org/r/20210609150159.v12.2.I7c9a1f1d6ced41dd8310e8a03da666a32364e790@changeidSigned-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/usb/misc/Makefile

517c4c44 - usb: Add driver to allow any GPIO to be used for 7211 USB signals

Mon, 12 Oct 2020 20:00:07 +0000

usb: Add driver to allow any GPIO to be used for 7211 USB signalsThe Broadcom 7211 has new functionality that allows some USB lowspeed side band signals, that go from the XHCI host controller topins on the chip, to be remapped to use any GPIO pin instead of thelimited set selectable by hardware. This can be done without changingthe standard driver for the host controller. There is currentlysupport for three USB signals, PWRON, VBUS_PRESENT and PWRFLT. Thisdriver will allow the remapping of any of these three signals basedon settings in the Device Tree node for the driver. The driver waswritten so that it could handle additional signals added in thefuture by just adding the correct properties to the DT node.Below is an example of a DT node that would remap all threesignals:usb_pinmap: usb-pinmap@22000d0 { compatible = "brcm,usb-pinmap"; reg = <0x22000d0 0x4>; in-gpios = <&gpio 18 0>, <&gpio 19 0>; brcm,in-functions = "VBUS", "PWRFLT"; brcm,in-masks = <0x8000 0x40000 0x10000 0x80000>; out-gpios = <&gpio 20 0>; brcm,out-functions = "PWRON"; brcm,out-masks = <0x20000 0x800000 0x400000 0x200000>; interrupts = <0x0 0xb2 0x4>;};Signed-off-by: Al Cooper Link: https://lore.kernel.org/r/20201012200007.8862-3-alcooperx@gmail.comSigned-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/usb/misc/Makefile

249fa821 - USB: Add driver to control USB fast charge for iOS devices

Wed, 16 Oct 2019 09:39:33 +0000

USB: Add driver to control USB fast charge for iOS devicesiOS devices will not draw more than 500mA unless instructed to do so.Setting the charge type power supply property to "fast" tells the deviceto start drawing more power, using the same procedure that official"MFi" chargers would.Signed-off-by: Bastien Nocera Acked-by: Alan Stern Link: https://lore.kernel.org/r/20191016093933.693-7-hadess@hadess.netSigned-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/usb/misc/Makefile

015664d1 - USB: rio500: Remove Rio 500 kernel driver

Mon, 23 Sep 2019 16:18:43 +0000

USB: rio500: Remove Rio 500 kernel driverThe Rio500 kernel driver has not been used by Rio500 owners since 2001not long after the rio500 project added support for a user-space USB stackthrough the very first versions of usbdevfs and then libusb.Support for the kernel driver was removed from the upstream utilitiesin 2008:https://gitlab.freedesktop.org/hadess/rio500/commit/943f624ab721eb8281c287650fcc9e2026f6f5dbCc: Cesar Miquel Signed-off-by: Bastien Nocera Cc: stable Link: https://lore.kernel.org/r/6251c17584d220472ce882a3d9c199c401a51a71.camel@hadess.netSigned-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/usb/misc/Makefile

b2441318 - License cleanup: add SPDX GPL-2.0 license identifier to files with no license

Wed, 01 Nov 2017 14:07:57 +0000

License cleanup: add SPDX GPL-2.0 license identifier to files with no licenseMany source files in the tree are missing licensing information, whichmakes it harder for compliance tools to determine the correct license.By default all files without license information are under the defaultlicense of the kernel, which is GPL version 2.Update the files which contain no license information with the 'GPL-2.0'SPDX license identifier. The SPDX identifier is a legally bindingshorthand, which can be used instead of the full boiler plate text.This patch is based on work done by Thomas Gleixner and Kate Stewart andPhilippe Ombredanne.How this work was done:Patches were generated and checked against linux-4.14-rc6 for a subset ofthe use cases: - file had no licensing information it it. - file was a */uapi/* one with no licensing information in it, - file was a */uapi/* one with existing licensing information,Further patches will be generated in subsequent months to fix up caseswhere non-standard license headers were used, and references to licensehad to be inferred by heuristics based on keywords.The analysis to determine which SPDX License Identifier to be applied toa file was done in a spreadsheet of side by side results from of theoutput of two independent scanners (ScanCode & Windriver) producing SPDXtag:value files created by Philippe Ombredanne. Philippe prepared thebase worksheet, and did an initial spot review of a few 1000 files.The 4.13 kernel was the starting point of the analysis with 60,537 filesassessed. Kate Stewart did a file by file comparison of the scannerresults in the spreadsheet to determine which SPDX license identifier(s)to be applied to the file. She confirmed any determination that was notimmediately clear with lawyers working with the Linux Foundation.Criteria used to select files for SPDX license identifier tagging was: - Files considered eligible had to be source code files. - Make and config files were included as candidates if they contained >5 lines of source - File already had some variant of a license header in it (even if <5 lines).All documentation files were explicitly excluded.The following heuristics were used to determine which SPDX licenseidentifiers to apply. - when both scanners couldn't find any license traces, file was considered to have no license information in it, and the top level COPYING file license applied. For non */uapi/* files that summary was: SPDX license identifier # files ---------------------------------------------------|------- GPL-2.0 11139 and resulted in the first patch in this series. If that file was a */uapi/* path one, it was "GPL-2.0 WITH Linux-syscall-note" otherwise it was "GPL-2.0". Results of that was: SPDX license identifier # files ---------------------------------------------------|------- GPL-2.0 WITH Linux-syscall-note 930 and resulted in the second patch in this series. - if a file had some form of licensing information in it, and was one of the */uapi/* ones, it was denoted with the Linux-syscall-note if any GPL family license was found in the file or had no licensing in it (per prior point). Results summary: SPDX license identifier # files ---------------------------------------------------|------ GPL-2.0 WITH Linux-syscall-note 270 GPL-2.0+ WITH Linux-syscall-note 169 ((GPL-2.0 WITH Linux-syscall-note) OR BSD-2-Clause) 21 ((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause) 17 LGPL-2.1+ WITH Linux-syscall-note 15 GPL-1.0+ WITH Linux-syscall-note 14 ((GPL-2.0+ WITH Linux-syscall-note) OR BSD-3-Clause) 5 LGPL-2.0+ WITH Linux-syscall-note 4 LGPL-2.1 WITH Linux-syscall-note 3 ((GPL-2.0 WITH Linux-syscall-note) OR MIT) 3 ((GPL-2.0 WITH Linux-syscall-note) AND MIT) 1 and that resulted in the third patch in this series. - when the two scanners agreed on the detected license(s), that became the concluded license(s). - when there was disagreement between the two scanners (one detected a license but the other didn't, or they both detected different licenses) a manual inspection of the file occurred. - In most cases a manual inspection of the information in the file resulted in a clear resolution of the license that should apply (and which scanner probably needed to revisit its heuristics). - When it was not immediately clear, the license identifier was confirmed with lawyers working with the Linux Foundation. - If there was any question as to the appropriate license identifier, the file was flagged for further research and to be revisited later in time.In total, over 70 hours of logged manual review was done on thespreadsheet to determine the SPDX license identifiers to apply to thesource files by Kate, Philippe, Thomas and, in some cases, confirmationby lawyers working with the Linux Foundation.Kate also obtained a third independent scan of the 4.13 code base fromFOSSology, and compared selected files where the other two scannersdisagreed against that SPDX file, to see if there was new insights. TheWindriver scanner is based on an older version of FOSSology in part, sothey are related.Thomas did random spot checks in about 500 files from the spreadsheetsfor the uapi headers and agreed with SPDX license identifier in thefiles he inspected. For the non-uapi files Thomas did random spot checksin about 15000 files.In initial set of patches against 4.14-rc6, 3 files were found to havecopy/paste license identifier errors, and have been fixed to reflect thecorrect identifier.Additionally Philippe spent 10 hours this week doing a detailed manualinspection and review of the 12,461 patched files from the initial patchversion early this week with: - a full scancode scan run, collecting the matched texts, detected license ids and scores - reviewing anything where there was a license detected (about 500+ files) to ensure that the applied SPDX license was correct - reviewing anything where there was no detection but the patch license was not GPL-2.0 WITH Linux-syscall-note to ensure that the applied SPDX license was correctThis produced a worksheet with 20 files needing minor correction. Thisworksheet was then exported into 3 different .csv files for thedifferent types of files to be modified.These .csv files were then reviewed by Greg. Thomas wrote a script toparse the csv files and add the proper SPDX tag to the file, in theformat that the file expected. This script was further refined by Gregbased on the output to detect more types of files automatically and todistinguish between header and source .c files (which need differentcomment types.) Finally Greg ran the script using the .csv files togenerate the patches.Reviewed-by: Kate Stewart Reviewed-by: Philippe Ombredanne Reviewed-by: Thomas Gleixner Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/usb/misc/Makefile

8243edf4 - usb: typec: ucsi: Add ACPI driver

Fri, 16 Jun 2017 08:21:25 +0000

usb: typec: ucsi: Add ACPI driverDriver for ACPI UCSI interface method. This driver replacesthe previous UCSI driver drivers/usb/misc/ucsi.c.Signed-off-by: Heikki Krogerus Reviewed-by: Guenter Roeck Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/usb/misc/Makefile

3ec72a2a - usb: misc: add USB251xB/xBi Hi-Speed Hub Controller Driver

Fri, 10 Feb 2017 08:19:27 +0000

usb: misc: add USB251xB/xBi Hi-Speed Hub Controller DriverThis patch adds a driver for configuration of the Microchip USB251xB/xBiUSB 2.0 hub controller series with USB 2.0 upstream connectivity, SMBusconfiguration interface and two to four USB 2.0 downstream ports.Furthermore add myself as a maintainer for this driver.The datasheet can be found at the manufacturers website, see [1]. Alldevice-tree exposed configuration features have been tested on a i.MX6platform with a USB2512B hub.[1] http://ww1.microchip.com/downloads/en/DeviceDoc/00001692C.pdfSigned-off-by: Richard Leitner Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/usb/misc/Makefile

740a6a17 - usb: misc: Add driver for usb4604

Sun, 26 Jun 2016 05:24:54 +0000

usb: misc: Add driver for usb4604This is a minimal driver to support bringing a usb4604 devicefrom microchip out of reset and into hub mode. The usb4604 deviceis related to the usb3503 device, but it didn't seem close enoughto warrant putting both into the same file. This patch borrowssome of the usb3503 structure and trims it down to just handlethe optional reset gpio and adds the i2c command to put thedevice into hub mode.Datasheet: http://ww1.microchip.com/downloads/en/DeviceDoc/00001716A.pdfCc: Signed-off-by: Stephen Boyd Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/usb/misc/Makefile

a335aaf3 - usb: misc: remove outdated USB LED driver

Fri, 17 Jun 2016 06:11:59 +0000

usb: misc: remove outdated USB LED driverThe USB LED driver exposes a undocumented sysfs interface and doesn'tuse the standard kernel LED subsystem. It supports three devices:Delcom Visual Signal IndicatorThe driver supports generation 1 of the device only which wasmanufactured until 2008. Remove support for this device completely.Riso Kagaku RGB LED + Dream Cheeky Webmail NotifierThese devices are HID compliant and are supported by a new USB LEDdriver under drivers/hid utilizing the kernel LED subsystem.So let's remove the old USB LED driver.Signed-off-by: Heiner Kallweit Acked-by: Greg Kroah-Hartman Acked-by: Benjamin Tissoires Signed-off-by: Jiri Kosina List of files: /linux-6.15/drivers/usb/misc/Makefile

0c1849a8 - usb: Add driver for UCSI

Thu, 21 Apr 2016 12:43:40 +0000

usb: Add driver for UCSIUSB Type-C Connector System Software Interface (UCSI) isspecification that defines the registers and data structuresthat can be used to control USB Type-C ports on a system.UCSI is used on several Intel Broxton SoC based platforms.Things that UCSI can be used to control include at least USBData Role swapping, Power Role swapping and controlling ofAlternate Modes on top of providing general details aboutthe port and the partners that are attached to it.The initial purpose of the UCSI driver is to make sure USBis in host mode on desktop and server systems that are USBdual role capable, and provide UCSI interface.The goal is to integrate the driver later to an USB Type-Cframework for Linux kernel, and at the same time add supportfor more extensive USB Type-C port control that UCSI offers,for example data role swapping, power role swapping,Alternate Mode control etc.The UCSI specification is public can be obtained from here:http://www.intel.com/content/www/us/en/io/universal-serial-bus/usb-type-c-ucsi-spec.htmlSigned-off-by: Heikki Krogerus Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/usb/misc/Makefile

66e3e591 - usb: Add driver for Altus Metrum ChaosKey device (v2)

Fri, 20 Mar 2015 03:36:49 +0000

usb: Add driver for Altus Metrum ChaosKey device (v2)This is a hardware random number generator. The driver provides both a/dev/chaoskeyX entry and hooks the entropy source up to the kernelhwrng interface. More information about the device can be found athttp://chaoskey.orgThe USB ID for ChaosKey was allocated from the OpenMoko USB vendorspace and is visible as 'USBtrng' here:http://wiki.openmoko.org/wiki/USB_Product_IDsv2: Respond to review from Oliver Neukum * Delete extensive debug infrastructure and replace it with calls to dev_dbg. * Allocate I/O buffer separately from device structure to obey requirements for non-coherant architectures. * Initialize mutexes before registering device to ensure that open cannot be invoked before the device is ready to proceed. * Return number of bytes read instead of -EINTR when partial read operation is aborted due to a signal. * Make sure device mutex is unlocked in read error paths. * Add MAINTAINERS entry for the driverSigned-off-by: Keith Packard Cc: Oliver Neukum Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/usb/misc/Makefile

ce21bfe6 - USB: Add LVS Test device driver

Mon, 14 Jul 2014 13:57:49 +0000

USB: Add LVS Test device driverOTG3 and EH Compliance Plan 1.0 talks about Super Speed OTG Verificationsystem (SS-OVS) which consists of an excersizer and analyzer.USB Compliance Suite from Lecroy or Ellisys can act as such SS-OVS forLink Layer Validation (LVS).Some modifications are needed for an embedded Linux USB host to pass allthese tests. Most of these tests require just Link to be in U0. They donot work with default Linux USB stack since, default stack does portreset and then starts sending setup packet, which is not expected byLink Layer Validation (LVS) device of Lecroy Compliance Suit. Then,There are many Link Layer Tests which need host to generate specifictraffic.This patch supports specific traffic generation cases. As of now all thehost Lecroy Link Layer-USBIF tests (except TD7.26) passeswith this patch for single run using Lecroy USB Compliance SuiteVersion 1.98 Build 239 and Lecroy USB Protocol Analyzer version 4.80Build 1603. Therefore patch seems to be a good candidate for inclusion.Further modification can be done on top of it.lvstest driver will not bind to any device by default. It can bindmanually to a super speed USB host controller root hub. Therefore, regularhub driver must be unbound before this driver is bound. For example, if2-0:1.0 is the xhci root hub, then execute following to unbind hub driver. echo 2-0:1.0 > /sys/bus/usb/drivers/hub/unbindThen write Linux Foundation's vendor ID which is used by root hubs andSS root hub's device ID into new_id file. Writing IDs into new_id filewill also bind the lvs driver with any available SS root hub interfaces. echo "1D6B 3" > /sys/bus/usb/drivers/lvs/new_idNow connect LVS device with root hub port.Test case specific traffic can be generated as follows whenever needed:1. To issue "Get Device descriptor" command for TD.7.06: echo > /sys/bus/usb/devices/2-0\:1.0/get_dev_desc2. To set U1 timeout to 127 for TD.7.18 echo 127 > /sys/bus/usb/devices/2-0\:1.0/u1_timeout3. To set U2 timeout to 0 for TD.7.18 echo 0 > /sys/bus/usb/devices/2-0\:1.0/u2_timeout4. To issue "Hot Reset" for TD.7.29 echo > /sys/bus/usb/devices/2-0\:1.0/hot_reset5. To issue "U3 Entry" for TD.7.35 echo > /sys/bus/usb/devices/2-0\:1.0/u3_entry6. To issue "U3 Exit" for TD.7.36 echo > /sys/bus/usb/devices/2-0\:1.0/u3_exitSigned-off-by: Pratyush Anand Acked-by: Alan Stern Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/usb/misc/Makefile