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/core/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/core/Makefile

07dbff0d - usb: core: add a wrapper for the USB PHYs on the HCD

Sat, 03 Mar 2018 21:43:04 +0000

usb: core: add a wrapper for the USB PHYs on the HCDMany SoC platforms have separate devices for the USB PHY which areregistered through the generic PHY framework. These PHYs have to beenabled to make the USB controller actually work. They also have to bedisabled again on shutdown/suspend.Currently (at least) the following HCI platform drivers are using customcode to obtain all PHYs via devicetree for the roothub/controller anddisable/enable them when required:- ehci-platform.c has ehci_platform_power_{on,off}- xhci-mtk.c has xhci_mtk_phy_{init,exit,power_on,power_off}- ohci-platform.c has ohci_platform_power_{on,off}With this new wrapper the USB PHYs can be specified directly in theUSB controller's devicetree node (just like on the drivers listedabove). This allows SoCs like the Amlogic Meson GXL family to operatecorrectly once this is wired up correctly. These SoCs use a dwc3controller and require all USB PHYs to be initialized (if one of the USBPHYs it not initialized then none of USB port works at all).Signed-off-by: Martin Blumenstingl Tested-by: Yixun Lan Cc: Chunfeng Yun Tested-by: Neil Armstrong Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/usb/core/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/core/Makefile

2c93e790 - usb: add CONFIG_USB_PCI for system have both PCI HW and non-PCI based USB HW

Sat, 25 Feb 2017 11:20:55 +0000

usb: add CONFIG_USB_PCI for system have both PCI HW and non-PCI based USB HWa lot of embeded system SOC (e.g. freescale T2080) have bothPCI and USB modules. But USB module is controlled by registers directly,it have no relationship with PCI module.when say N here it will not build PCI related code in USB driver.Signed-off-by: yuan linyu Acked-by: Felipe Balbi Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/usb/core/Makefile

0f247626 - usb: core: Introduce a USB port LED trigger

Fri, 16 Sep 2016 14:13:48 +0000

usb: core: Introduce a USB port LED triggerThis commit adds a new trigger responsible for turning on LED when USBdevice gets connected to the selected USB port. This can can useful forvarious home routers that have USB port(s) and a proper LED telling usera device is connected.The trigger gets its documentation file but basically it just requiresenabling it and selecting USB ports (e.g. echo 1 > ports/usb1-1).There was a long discussion on design of this driver. Its current stateis a result of picking them most adjustable solution as others couldn'thandle all cases.1) It wasn't possible for the driver to register separated trigger for each USB port. Some physical USB ports are handled by more than one controller and so by more than one USB port. E.g. USB 2.0 physical port may be handled by OHCI's port and EHCI's port. It's also not possible to assign more than 1 trigger to a single LED and implementing such feature would be tricky due to syncing triggers and sysfs conflicts with old triggers.2) Another idea was to register trigger per USB hub. This wouldn't allow handling devices with multiple USB LEDs and controllers (hubs) controlling more than 1 physical port. It's common for hubs to have few ports and each may have its own LED.This final trigger is highly flexible. It allows selecting any USB portsfor any LED. It was also modified (comparing to the initial version) toallow choosing ports rather than having user /guess/ proper names. Itwas successfully tested on SmartRG SR400ac which has 3 USB LEDs,2 physical ports and 3 controllers.It was noted USB subsystem already has usb-gadget and usb-host triggersbut they are pretty trivial ones. They indicate activity only and can'thave ports specified.In future it may be good idea to consider adding activity support tousbport as well. This should allow switching to this more generic driverand maybe marking old ones as obsolete.This can be implemented with another sysfs file for setting mode. Thedefault mode wouldn't change so there won't be ABI breakage and so suchfeature can be safely implemented later.There was also an idea of supporting other devices (PCI, SDIO, etc.) butas this driver already contains some USB specific code (and will getmore) these should be probably separated drivers (triggers).Signed-off-by: Rafał Miłecki Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/usb/core/Makefile

0573f2c5 - usb: core: of.c: fix defined but not declare warning

Wed, 15 Jun 2016 03:25:43 +0000

usb: core: of.c: fix defined but not declare warningThe helper usb_of_get_child_node is defined at of.c, but missing itsdeclare as a global function. Fix it by adding related header fileas well as compile it on conditional of CONFIG_OF.Cc: Greg Kroah-Hartman Cc: Arnd Bergmann Cc: Alan Stern Cc: linux-usb@vger.kernel.orgCc: linux-kernel@vger.kernel.orgCc: Ben Dooks Cc: linux-kernel@lists.codethink.co.ukSigned-off-by: Peter Chen Reported-by: Ben Dooks Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/usb/core/Makefile

69bec725 - USB: core: let USB device know device node

Fri, 19 Feb 2016 09:26:15 +0000

USB: core: let USB device know device nodeAlthough most of USB devices are hot-plug's, there are still some devicesare hard wired on the board, eg, for HSIC and SSIC interface USB devices.If these kinds of USB devices are multiple functions, and they can supplyother interfaces like i2c, gpios for other devices, we may need todescribe these at device tree.In this commit, it uses "reg" in dts as physical port number to matchthe phyiscal port number decided by USB core, if they are the same,then the device node is for the device we are creating for USB core.Signed-off-by: Peter Chen Acked-by: Philipp Zabel Acked-by: Alan Stern Acked-by: Rob Herring Acked-by: Arnd Bergmann Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/usb/core/Makefile

3482528e - USB: core: remove CONFIG_USB_DEBUG usage

Thu, 19 Dec 2013 23:42:20 +0000

USB: core: remove CONFIG_USB_DEBUG usageCONFIG_USB_DEBUG is going away, so remove the few places in the USB corethat relied on them.This means that we always now do the "debug" checks for every urbsubmitted, which is a good idea, as who knows how many driver bugs wehave been ignoring when people forget to enable this option. Also, withthe overall speed of USB, doing these extra checks should not cause anyadditional overhead.Also, no longer announce all devices being added to the system ifCONFIG_USB_DEBUG is enabled, as it's not going to be around much longer.Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/usb/core/Makefile

6e30d7cb - usb: Add driver/usb/core/(port.c,hub.h) files

Fri, 11 Jan 2013 12:10:38 +0000

usb: Add driver/usb/core/(port.c,hub.h) filesThis patch is to create driver/usb/core/(port.c,hub.h) files and move usbport related code into port.c.Signed-off-by: Lan Tianyu Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/usb/core/Makefile

da0af6e7 - usb: Bind devices to ACPI devices when possible

Fri, 11 May 2012 08:08:27 +0000

usb: Bind devices to ACPI devices when possibleBuilt-in USB devices will typically have a representation in the systemACPI tables. Add support for binding the two together so the USB code canmake use of the associated methods.Signed-off-by: Matthew Garrett Signed-off-by: Lan Tianyu Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/usb/core/Makefile

fb28d58b - USB: remove CONFIG_USB_DEVICEFS

Thu, 26 Apr 2012 00:15:29 +0000

USB: remove CONFIG_USB_DEVICEFSThis option has been deprecated for many years now, and no userspacetools use it anymore, so it should be safe to finally remove it.Reported-by: Kay Sievers Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/usb/core/Makefile

0a2b8a0d - usb: makefile cleanup

Thu, 07 Oct 2010 02:03:26 +0000

usb: makefile cleanupFor all modules, change -objs to -y; removeif-statements and replace with lists using the kbuild idiom; moveflags to the top of the file; and fix alignment while trying tomaintain the original scheme in each file.None of the dependencies are modified.Signed-off-by: matt mooney Acked-by: Sam Ravnborg Acked-by: Felipe Balbi Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/usb/core/Makefile

25013315 - usb: change to new flag variable

Fri, 24 Sep 2010 19:17:33 +0000

usb: change to new flag variableReplace EXTRA_CFLAGS with ccflags-y.Signed-off-by: matt mooney Acked-by: WANG Cong Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/usb/core/Makefile

97d7b7a4 - USB: add the usbfs devices file to debugfs

Fri, 24 Apr 2009 22:16:04 +0000

USB: add the usbfs devices file to debugfsPeople are very used to the devices file in usbfs. Now that we havemoved usbfs to be an "embedded" option only, the developers miss thefile, they had grown quite attached to it over all of these years. Thispatch brings it back and puts it in the usb debugfs directory, so thatthe developers don't feel sad anymore.Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/usb/core/Makefile

7ceec1f1 - USB: add a blacklist for devices that can't handle some things we throw at them.

Fri, 26 Jan 2007 13:26:21 +0000

USB: add a blacklist for devices that can't handle some things we throw at them.This adds a blacklist to the USB core to handle some autosuspend andstring issues that devices have.Originally written by Oliver, but hacked up a lot by Greg.Signed-off-by: Oliver Neukum Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/usb/core/Makefile

36e56a34 - usbcore: move code among source files

Sun, 02 Jul 2006 02:08:06 +0000

usbcore: move code among source filesThis revised patch (as713b) moves a few routines among source files inusbcore. Some driver-related code in usb.c (claiming interfaces andmatching IDs) is moved to driver.c, where it belongs. Also theusb_generic stuff in driver.c is moved to a new source file: generic.c.(That's the reason for revising the patch.) Although not very big now,it will get bigger in a later patch.None of the code has been changed; it has only been re-arranged.Signed-off-by: Alan Stern Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/usb/core/Makefile

84412f62 - [PATCH] USB: move the endpoint specific sysfs code to it's own file

Wed, 14 Jun 2006 19:14:34 +0000

[PATCH] USB: move the endpoint specific sysfs code to it's own fileThis makes it easier to modify in the future without touching anything else.Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/usb/core/Makefile

ddae41be - [PATCH] USB: reorg some functions out of the main usb.c file

Wed, 16 Nov 2005 21:41:28 +0000

[PATCH] USB: reorg some functions out of the main usb.c fileThis will make the dynamic-id stuff easier to do, as it will beself-contained.No logic was changed at all.Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/usb/core/Makefile

654f3118 - [PATCH] USB: move CONFIG_USB_DEBUG checks into the Makefile

Thu, 17 Nov 2005 17:48:09 +0000

[PATCH] USB: move CONFIG_USB_DEBUG checks into the MakefileThis lets us remove a lot of code in the drivers that were all checkingthe same thing. It also found some bugs in a few of the drivers, whichhas been fixed up.Signed-off-by: Greg Kroah-Hartman Signed-off-by: Linus Torvalds List of files: /linux-6.15/drivers/usb/core/Makefile