Changes in Makefile

4602f3bf - usb: common: add USB GPIO based connection detection driver

Thu, 29 Aug 2019 09:22:37 +0000

usb: common: add USB GPIO based connection detection driverDue to the requirement of usb-connector.txt binding, the old wayusing extcon to support USB Dual-Role switch is now deprecatedwhen use Type-B connector.This patch introduces a USB GPIO based connection detection driver,used to support Type-B connector which typically uses an input GPIOto detect USB ID pin, and try to replace the function providedby the extcon-usb-gpio driverSigned-off-by: Chunfeng Yun Tested-by: Nagarjuna Kristam Reviewed-by: Linus Walleij Link: https://lore.kernel.org/r/1567070558-29417-11-git-send-email-chunfeng.yun@mediatek.comSigned-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/usb/common/Makefile

91f255a2 - usb: common: Separated decoding functions from dwc3 driver.

Mon, 26 Aug 2019 11:19:27 +0000

usb: common: Separated decoding functions from dwc3 driver.Patch moves some decoding functions from driver/usb/dwc3/debug.h driverto driver/usb/common/debug.c file. These moved functions include: dwc3_decode_get_status dwc3_decode_set_clear_feature dwc3_decode_set_address dwc3_decode_get_set_descriptor dwc3_decode_get_configuration dwc3_decode_set_configuration dwc3_decode_get_intf dwc3_decode_set_intf dwc3_decode_synch_frame dwc3_decode_set_sel dwc3_decode_set_isoch_delay dwc3_decode_ctrlThese functions are used also in inroduced cdns3 driver.All functions prefixes were changed from dwc3 to usb.Also, function's parameters has been extended according to the nameof fields in standard SETUP packet.Additionally, patch adds usb_decode_ctrl function toinclude/linux/usb/ch9.h file.Signed-off-by: Pawel Laszczak Signed-off-by: Felipe Balbi List of files: /linux-6.15/drivers/usb/common/Makefile

c3788cd9 - usb: roles: Add a description for the class to Kconfig

Wed, 12 Dec 2018 17:13:55 +0000

usb: roles: Add a description for the class to KconfigThat makes the USB role switch support option visible andselectable for the user. The class driver is also moved todrivers/usb/roles/ directory.This will fix an issue that we have with the Intel USB roleswitch driver on systems that don't have USB Type-C connectors:Intel USB role switch driver depends on the USB role switchclass as it should, but since there was no way for the userto enable the USB role switch class, there was also no wayto select that driver. USB Type-C drivers select the USBrole switch class which makes the Intel USB role switchdriver available and therefore hides the problem.So in practice Intel USB role switch driver was depending onUSB Type-C drivers.Fixes: f6fb9ec02be1 ("usb: roles: Add Intel xHCI USB role switch driver")Cc: Signed-off-by: Heikki Krogerus Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/usb/common/Makefile

fde0aa6c - usb: common: Small class for USB role switches

Tue, 20 Mar 2018 12:57:04 +0000

usb: common: Small class for USB role switchesUSB role switch is a device that can be used to choose thedata role for USB connector. With dual-role capable USBcontrollers, the controller itself will be the switch, buton some platforms the USB host and device controllers areseparate IPs and there is a mux between them and theconnector. On those platforms the mux driver will need toregister the switch.With USB Type-C connectors, the host-to-device relationshipis negotiated over the Configuration Channel (CC). Thatmeans the USB Type-C drivers need to be in control of therole switch. The class provides a simple API for the USBType-C drivers for the control.For other types of USB connectors (mainly microAB) the classprovides user space control via sysfs attribute file thatcan be used to request role swapping from the switch.Reviewed-by: Hans de Goede Reviewed-by: Andy Shevchenko Signed-off-by: Heikki Krogerus Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/usb/common/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/common/Makefile

289fcff4 - usb: add bus type for USB ULPI

Wed, 13 May 2015 12:26:42 +0000

usb: add bus type for USB ULPIUTMI+ Low Pin Interface (ULPI) is a commonly used PHYinterface for USB 2.0. The ULPI specification describes astandard set of registers which the vendors can extend fortheir specific needs. ULPI PHYs provide often functionssuch as charger detection and ADP sensing and probing.There are two major issues that the bus type is meant totackle:Firstly, ULPI registers are accessed from the controller.The bus provides convenient method for the controllerdrivers to share that access with the actual PHY drivers.Secondly, there are already platforms that assume ULPI PHYsare runtime detected, such as many Intel Baytrail basedplatforms. They do not provide any kind of hardwaredescription for the ULPI PHYs like separate ACPI deviceobject that could be used to enumerate a device from.Signed-off-by: Heikki Krogerus Acked-by: David Cohen Signed-off-by: Felipe Balbi List of files: /linux-6.15/drivers/usb/common/Makefile

0cfbd328 - usb: Add LED triggers for USB activity

Wed, 24 Sep 2014 20:43:21 +0000

usb: Add LED triggers for USB activityWith this patch, USB activity can be signaled by blinking a LED. Thereare two triggers, one for activity on USB host and one for USB gadget.Both triggers should work with all host/device controllers. Tested onlywith musb.Performace: I measured performance overheads on ARM Cortex-A8 (TIAM335x) running on 600 MHz.Duration of usb_led_activity():- with no LED attached to the trigger: 2 ± 1 µs- with one GPIO LED attached to the trigger: 2 ± 1 µs or 8 ± 2 µs (two peaks in histogram)Duration of functions calling usb_led_activity() (with this patchapplied and no LED attached to the trigger):- __usb_hcd_giveback_urb(): 10 - 25 µs- usb_gadget_giveback_request(): 2 - 6 µsSigned-off-by: Michal Sojka Acked-by: Felipe Balbi Tested-by: Felipe Balbi Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/usb/common/Makefile

aa923ef1 - usb: Rename usb-common.c

Wed, 24 Sep 2014 20:43:20 +0000

usb: Rename usb-common.cIn the next commit, we will want the usb-common module to be composed oftwo object files. Since Kbuild cannot "append" another object to anexisting one, we need to rename usb-common.c to somethingelse (common.c) and create usb-common.o by linking the wanted objectstogether. Currently, usb-common.o comprises only common.o.Signed-off-by: Michal Sojka Acked-by: Felipe Balbi Tested-by: Felipe Balbi Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/usb/common/Makefile

1dfa91aa - usb: common: rename phy-fsm-usb.c to usb-otg-fsm.c

Tue, 29 Apr 2014 00:35:59 +0000

usb: common: rename phy-fsm-usb.c to usb-otg-fsm.cSince usb otg fsm implementation is not related to usb phy.We move it from usb/phy/ to usb/common/, and rename it toreflect its real meaning.Cc: Felipe Balbi Signed-off-by: Peter Chen Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/usb/common/Makefile

f4cbd33f - usb: move usb/usb-common.c to usb/common/usb-common.c

Tue, 29 Apr 2014 00:35:58 +0000

usb: move usb/usb-common.c to usb/common/usb-common.cSince we will have more usb-common things, and it will letusb-common.c be larger and larger, we create a folder named usb/commonfor all usb common things.Cc: Felipe Balbi Signed-off-by: Peter Chen Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/usb/common/Makefile