Changes in Makefile

34c20048 - usb: dwc3: add Realtek DHC RTD SoC dwc3 glue layer driver

Sat, 26 Aug 2023 03:10:06 +0000

usb: dwc3: add Realtek DHC RTD SoC dwc3 glue layer driverRealtek DHC RTD SoCs integrate dwc3 IP and has some customizations tosupport different generations of SoCs.The RTD1619b subclass SoC only supports USB 2.0 from dwc3. The drivercan set a maximum speed to support this. Add role switching function,that can switch USB roles through other drivers, or switch USB rolesthrough user space through set /sys/class/usb_role/.Signed-off-by: Stanley Chang Acked-by: Thinh Nguyen Link: https://lore.kernel.org/r/20230826031028.1892-1-stanley_chang@realtek.comSigned-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/usb/dwc3/Makefile

976f82e8 - usb: dwc3: dwc3-octeon: Convert to glue driver

Mon, 31 Jul 2023 09:30:45 +0000

usb: dwc3: dwc3-octeon: Convert to glue driverDWC3 as implemented in Cavium SoC is using UCTL bridge unitbetween I/O interconnect and USB controller.Currently there is no bond with dwc3 core code, so if anything goeswrong in UCTL setup dwc3 is left in reset, which leads to bus errorwhile trying to read any device register. Thus any failure in UCTLinitialization ends with kernel panic.To avoid this move Octeon DWC3 glue code from arch/mips and make itproper glue driver which is used instead of dwc3-of-simple.Signed-off-by: Ladislav Michl Acked-by: Thomas Bogendoerfer Acked-by: Thinh Nguyen Link: https://lore.kernel.org/r/ZMd/ReyiY7wS6DvN@lenochSigned-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/usb/dwc3/Makefile

e8784c0a - drivers: usb: dwc3: Add AM62 USB wrapper driver

Thu, 14 Apr 2022 10:32:09 +0000

drivers: usb: dwc3: Add AM62 USB wrapper driverIn AM62 SoC, the Designware Core USB3 IP is progammed to operate in USB2.0only mode. Add driver for AM62 USB DWC3 Wrapper.Signed-off-by: Aswath Govindraju Link: https://lore.kernel.org/r/20220414103211.16202-3-a-govindraju@ti.comSigned-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/usb/dwc3/Makefile

84770f02 - usb: dwc3: Add driver for Xilinx platforms

Wed, 17 Mar 2021 06:52:29 +0000

usb: dwc3: Add driver for Xilinx platformsAdd a new driver for supporting Xilinx platforms. This driver is usedfor some sequence of operations required for Xilinx USB controllers.This driver is also used to choose between PIPE clock coming from SerDesand the Suspend Clock. Before the controller is out of reset, the clockselection should be changed to PIPE clock in order to make the USBcontroller work. There is a register added in Xilinx USB controllerregister space for the same.Signed-off-by: Manish Narani Link: https://lore.kernel.org/r/1615963949-75320-3-git-send-email-manish.narani@xilinx.comSigned-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/usb/dwc3/Makefile

6dd25659 - usb: dwc3: add imx8mp dwc3 glue layer driver

Tue, 29 Dec 2020 11:37:44 +0000

usb: dwc3: add imx8mp dwc3 glue layer driverimx8mp SoC integrate dwc3 3.30b IP and has some customizations tosupport low power, which has a seprated wakeup irq and additionallogic to wakeup usb from low power mode both for host mode anddevice mode.Signed-off-by: Li Jun Link: https://lore.kernel.org/r/1609241866-9508-3-git-send-email-jun.li@nxp.comSigned-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/usb/dwc3/Makefile

c9999337 - usb: dwc3: Add Amlogic G12A DWC3 glue

Tue, 23 Apr 2019 08:51:27 +0000

usb: dwc3: Add Amlogic G12A DWC3 glueAdds support for Amlogic G12A USB Control Glue HW.The Amlogic G12A SoC Family embeds 2 USB Controllers :- a DWC3 IP configured as Host for USB2 and USB3- a DWC2 IP configured as Peripheral USB2 OnlyA glue connects these both controllers to 2 USB2 PHYs, and optionnallyto an USB3+PCIE Combo PHY shared with the PCIE controller.The Glue configures the UTMI 8bit interfaces for the USB2 PHYs, includingrouting of the OTG PHY between the DWC3 and DWC2 controllers, andsetups the on-chip OTG mode selection for this PHY.This drivers supports the on-probe setup of the OTG mode, and manuallyvia a debugfs interface. The IRQ mode change detect is yet to be addedin a future patchset, mainly due to lack of hardware to validate on.Signed-off-by: Neil Armstrong Reviewed-by: Martin Blumenstingl Signed-off-by: Felipe Balbi List of files: /linux-6.15/drivers/usb/dwc3/Makefile

3fe314ca - usb: dwc3: Add a glue driver for Synopsys HAPS platform

Tue, 12 Jun 2018 21:26:43 +0000

usb: dwc3: Add a glue driver for Synopsys HAPS platformThis driver is to be used for Synopsys PCIe-base HAPS platform. Move thethe HAPS support from dwc3-pci to this driver.Signed-off-by: Thinh Nguyen Signed-off-by: Felipe Balbi List of files: /linux-6.15/drivers/usb/dwc3/Makefile

a4333c3a - usb: dwc3: Add Qualcomm DWC3 glue driver

Wed, 09 May 2018 17:39:20 +0000

usb: dwc3: Add Qualcomm DWC3 glue driverDWC3 controller on Qualcomm SOCs has a Qscratch wrapper.Some of its uses are described below resulting in need tohave a separate glue driver instead of using dwc3-of-simple: - It exposes register interface to override vbus-override and lane0-pwr-present signals going to hardware. These must be updated in peripheral mode for DWC3 if vbus lines are not connected to hardware block. Otherwise RX termination in SS mode or DP pull-up is not applied by device controller. - pwr_events_irq_stat support to check if USB2 PHY is in L2 state before glue driver proceeds with suspend. - Support for wakeup interrupts lines that are asserted whenever there is any wakeup event on USB3 or USB2 bus. - Support to replace pip3 clock going to DWC3 with utmi clock for hardware configuration where SSPHY is not used with DWC3.Signed-off-by: Manu Gautam Signed-off-by: Felipe Balbi List of files: /linux-6.15/drivers/usb/dwc3/Makefile

de948a74 - usb: dwc3: Makefile: fix link error on randconfig

Thu, 22 Mar 2018 08:45:20 +0000

usb: dwc3: Makefile: fix link error on randconfigIf building a kernel without FTRACE but with TRACING, dwc3.ko fails tolink due to missing trace events. Fix this by using the correctKconfig symbol on Makefile.Reported-by: Randy Dunlap Signed-off-by: Felipe Balbi List of files: /linux-6.15/drivers/usb/dwc3/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/dwc3/Makefile

9840354f - usb: dwc3: Add dual-role support

Wed, 05 Apr 2017 10:39:31 +0000

usb: dwc3: Add dual-role supportIf dr_mode is "otg" then support dual role mode of operation.Currently this mode is only supported when an extcon handle ispresent in the dwc3 device tree node. This is needed toget the ID status events of the port.We're using a workqueue to manage the dual-role state transitionsas the extcon notifier (dwc3_drd_notifier) is called in an atomiccontext by extcon_sync() and this doesn't go well withusb_del_gadget_udc() causing a lockdep and softirq warning.Signed-off-by: Roger Quadros Signed-off-by: Felipe Balbi List of files: /linux-6.15/drivers/usb/dwc3/Makefile

5eb30ced - usb: dwc3: trace: purge dwc3_trace()

Thu, 03 Nov 2016 12:07:51 +0000

usb: dwc3: trace: purge dwc3_trace()Finally get rid of dwc3_trace() hack. If any othermessage is truly needed, we should add propertracepoints for them instead of hacking around withdwc3_trace() or similar.Signed-off-by: Felipe Balbi List of files: /linux-6.15/drivers/usb/dwc3/Makefile

57b14da5 - usb: dwc3: don't compile dwc3_trace() unless CONFIG_FTRACE=y

Fri, 30 Sep 2016 11:12:34 +0000

usb: dwc3: don't compile dwc3_trace() unless CONFIG_FTRACE=yWe don't need dwc3_trace() unless we're building akernel with CONFIG_FTRACE. This patch reducesdwc3.ko text size a bit while also removing overheadof dwc3_trace() calls. text data bss dec hex filename 50796 581 0 51377 c8b1 drivers/usb/dwc3/dwc3.o 43961 581 0 44542 adfe drivers/usb/dwc3/dwc3.o.patchedSigned-off-by: Felipe Balbi List of files: /linux-6.15/drivers/usb/dwc3/Makefile

b0846627 - usb: dwc3: remove dwc3-qcom in favor of dwc3-of-simple

Thu, 19 Nov 2015 18:15:43 +0000

usb: dwc3: remove dwc3-qcom in favor of dwc3-of-simpleNow that we have a generic dwc3-of-simple.c, we canuse that instead of maintaining dwc3-qcom.c which isextremely similar.Cc: Ivan T. Ivanov Signed-off-by: Felipe Balbi List of files: /linux-6.15/drivers/usb/dwc3/Makefile

16adc674 - usb: dwc3: add generic OF glue layer

Wed, 18 Nov 2015 19:15:20 +0000

usb: dwc3: add generic OF glue layerFor simple platforms which merely enable some clocksand populate its children, we can use this genericglue layer to avoid boilerplate code duplication.For now this supports Qcom and Xilinx, but if wefind a way to add generic handling of regulators andoptional PHYs, we can absorb exynos as well.Tested-by: Subbaraya Sundeep Bhatta Signed-off-by: Felipe Balbi List of files: /linux-6.15/drivers/usb/dwc3/Makefile

9fcfa463 - usb: dwc3: drop CONFIG_USB_DWC3_DEBUG

Tue, 30 Jun 2015 17:51:49 +0000

usb: dwc3: drop CONFIG_USB_DWC3_DEBUGnow that we have no users of dev_dbg() in dwc3,we can safely remove CONFIG_USB_DWC3_DEBUG.If dev_dbg() is ever strictly necessary - and Idon't see why it would, considering we want torely on tracepoints for debug - we will dependon DYNAMIC_PRINTK to enable such messages.Signed-off-by: Felipe Balbi List of files: /linux-6.15/drivers/usb/dwc3/Makefile

88bc9d19 - usb: dwc3: add ULPI interface support

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

usb: dwc3: add ULPI interface supportRegisters DWC3's ULPI interface with the ULPI bus when it'savailable.Signed-off-by: Heikki Krogerus Acked-by: David Cohen Signed-off-by: Felipe Balbi List of files: /linux-6.15/drivers/usb/dwc3/Makefile

73815280 - usb: dwc3: remove reliance on dev_vdbg()

Tue, 27 Jan 2015 19:48:14 +0000

usb: dwc3: remove reliance on dev_vdbg()By moving all dev_vdbg() to tracepoints, wecan finally get rid of dev_vdbg() usage fromdwc3.Signed-off-by: Felipe Balbi List of files: /linux-6.15/drivers/usb/dwc3/Makefile

d9152161 - usb: dwc3: Add Qualcomm DWC3 glue layer driver

Fri, 12 Sep 2014 19:28:07 +0000

usb: dwc3: Add Qualcomm DWC3 glue layer driverDWC3 glue layer is hardware layer around Synopsys DesignWareUSB3 core. Its purpose is to supply Synopsys IP with requiredclocks, voltages and interface it with the rest of the SoC.Signed-off-by: Ivan T. Ivanov Signed-off-by: Andy Gross Signed-off-by: Felipe Balbi List of files: /linux-6.15/drivers/usb/dwc3/Makefile

f83fca07 - usb: dwc3: add ST dwc3 glue layer to manage dwc3 HC

Fri, 05 Sep 2014 15:36:30 +0000

usb: dwc3: add ST dwc3 glue layer to manage dwc3 HCThis patch adds the ST glue logic to manage the DWC3 HCon STiH407 SoC family. It manages the powerdown signal,and configures the internal glue logic and syscfg registers.[ balbi@ti.com : actually switch over to of_platform_depopulate() ]Signed-off-by: Giuseppe Cavallaro Signed-off-by: Peter Griffin Acked-by: Lee Jones Signed-off-by: Felipe Balbi List of files: /linux-6.15/drivers/usb/dwc3/Makefile