Changes in Makefile

783f6d3d - phy: bcm63xx-usbh: Add BCM63xx USBH driver

Mon, 20 Jul 2020 13:12:09 +0000

phy: bcm63xx-usbh: Add BCM63xx USBH driverAdd BCM63xx USBH PHY driver for BMIPS.Signed-off-by: Álvaro Fernández Rojas Signed-off-by: Simon Arlott Link: https://lore.kernel.org/r/20200720131209.1236590-3-noltari@gmail.comSigned-off-by: Vinod Koul List of files: /linux-6.15/drivers/phy/broadcom/Makefile

4e5b9c9a - phy: usb: Add support for new Synopsys USB controller on the 7216

Fri, 03 Jan 2020 18:18:05 +0000

phy: usb: Add support for new Synopsys USB controller on the 7216The 7216 has the new USB XHCI controller from Synopsys. Whilethis new controller and the PHY are similar to the STB versions,the major differences are:- Many of the registers and fields in the CTRL block have been removed or changed.- A new set of Synopsys control registers, BCHP_USB_XHCI_GBL, were added.- MDIO functionality has been replaced with direct access registers in the BCHP_USB_XHCI_GBL block.- Power up PHY defaults that had to be changed by MDIO in previous chips will now power up with the correct defaults.A new init module was created for this new Synopsys USB controller.A new compatible string was added and the driver will dispatchinto one of two init modules based on it. A "reg-names" field wasadded so the driver can more easily get optional registers.A DT bindings document was also added for this driver.Signed-off-by: Al Cooper Reviewed-by: Florian Fainelli Signed-off-by: Kishon Vijay Abraham I List of files: /linux-6.15/drivers/phy/broadcom/Makefile

4dcddbb3 - phy: sr-usb: Add Stingray USB PHY driver

Tue, 19 Mar 2019 09:15:43 +0000

phy: sr-usb: Add Stingray USB PHY driverUSB PHY driver supports two types of stingray USB PHYs - Type 1 is a combo PHY contains two PHYs, one SS and one HS. - Type 2 is a single HS PHY.These two PHY versons support both Generic xHCI host controller driverand BDC Broadcom device controller driver.Signed-off-by: Srinath Mannam Signed-off-by: Kishon Vijay Abraham I List of files: /linux-6.15/drivers/phy/broadcom/Makefile

92696a89 - phy: bcm-sr-pcie: Add Stingray PCIe PHY driver

Sat, 07 Jul 2018 00:18:33 +0000

phy: bcm-sr-pcie: Add Stingray PCIe PHY driverAdd Stingray PCIe PHY driver for both PAXB and PAXC root complexSigned-off-by: Ray Jui Signed-off-by: Kishon Vijay Abraham I List of files: /linux-6.15/drivers/phy/broadcom/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/phy/broadcom/Makefile

49859e55 - phy: usb: phy-brcm-usb: Add Broadcom STB USB phy driver

Fri, 22 Sep 2017 19:34:01 +0000

phy: usb: phy-brcm-usb: Add Broadcom STB USB phy driverAdd a new USB Phy driver for Broadcom STB SoCs. This driversupports Broadcom STB ARM SoCs. This driver incombination with the Broadcom STB ohci, ehci and xhcidrivers will enable USB1.1, USB2.0 and USB3.0 support.This Phy driver also supports the Broadcom BDC gadgetdriver.Signed-off-by: Al Cooper Signed-off-by: Kishon Vijay Abraham I List of files: /linux-6.15/drivers/phy/broadcom/Makefile

787f2454 - phy: phy-bcm-ns2-usbdrd: Broadcom USB DRD PHY driver for Northstar2

Fri, 09 Jun 2017 11:43:01 +0000

phy: phy-bcm-ns2-usbdrd: Broadcom USB DRD PHY driver for Northstar2This is driver for USB DRD PHY used in Broadcom's Northstar2SoC. The phy can be configured to be in Device mode or Hostmode based on the type of cable connected to the port. Thedriver registers to extcon framework to get appropriateconnect events for Host/Device cables connect/disconnectstates based on VBUS and ID interrupts.Signed-off-by: Raviteja Garimella Signed-off-by: Kishon Vijay Abraham I List of files: /linux-6.15/drivers/phy/broadcom/Makefile

0b56e9a7 - phy: Group vendor specific phy drivers

Thu, 11 May 2017 06:47:42 +0000

phy: Group vendor specific phy driversAdding vendor specific directories in phy to groupphy drivers under their respective vendor umbrella.Also updated the MAINTAINERS file to reflect the correctdirectory structure for phy drivers.Signed-off-by: Vivek Gautam Acked-by: Heiko Stuebner Acked-by: Viresh Kumar Acked-by: Krzysztof Kozlowski Acked-by: Yoshihiro Shimoda Reviewed-by: Jaehoon Chung Cc: Kishon Vijay Abraham I Cc: David S. Miller Cc: Geert Uytterhoeven Cc: Yoshihiro Shimoda Cc: Guenter Roeck Cc: Heiko Stuebner Cc: Viresh Kumar Cc: Maxime Ripard Cc: Chen-Yu Tsai Cc: Sylwester Nawrocki Cc: Krzysztof Kozlowski Cc: Jaehoon Chung Cc: Stephen Boyd Cc: Martin Blumenstingl Cc: linux-arm-kernel@lists.infradead.orgCc: linux-arm-msm@vger.kernel.orgCc: linux-kernel@vger.kernel.orgCc: linux-omap@vger.kernel.orgCc: linux-renesas-soc@vger.kernel.orgCc: linux-rockchip@lists.infradead.orgCc: linux-samsung-soc@vger.kernel.orgCc: linux-usb@vger.kernel.orgSigned-off-by: Kishon Vijay Abraham I List of files: /linux-6.15/drivers/phy/broadcom/Makefile