Changes in Makefile

c2d405aa - USB: serial: add MaxLinear/Exar USB to Serial driver

Sun, 22 Nov 2020 17:08:20 +0000

USB: serial: add MaxLinear/Exar USB to Serial driverAdd support for MaxLinear/Exar USB to Serial converters. This driveronly supports XR21V141X series but it can be extended to other seriesfrom Exar as well in future.This driver is inspired from the initial one submitted by Patong Yang:https://lore.kernel.org/r/20180404070634.nhspvmxcjwfgjkcv@advantechmxl-desktopWhile the initial driver was a custom tty USB driver exposing wholenew serial interface ttyXRUSBn, this version is completely based on USBserial core thus exposing the interfaces as ttyUSBn. This will avoidthe overhead of exposing a new USB serial interface which the userspacetools are unaware of.The Exar XR21V141X can be used in either ACM mode using the cdc-acmdriver or in "custom driver" mode in which further features such ashardware and software flow control, GPIO control and in-band line-statusreporting are available.In ACM mode the device always enables RTS/CTS flow control, somethingwhich could prevent transmission in case the CTS input isn't wired upcorrently.A follow-on patch will prevent cdc_acm from binding whenever this driveris enabled.Signed-off-by: Manivannan Sadhasivam Link: https://lore.kernel.org/r/20201122170822.21715-2-mani@kernel.org[ johan: fix some style nits, group related functions, drop unused callbacks, and amend commit message; a few remaining non-trivial issues will be fixed separately ]Signed-off-by: Johan Hovold List of files: /linux-6.15/drivers/usb/serial/Makefile

7604ce70 - USB: serial: keyspan_pda: clean up xircom/entrega support

Tue, 27 Oct 2020 09:25:02 +0000

USB: serial: keyspan_pda: clean up xircom/entrega supportDrop the separate Kconfig symbol for Xircom / Entrega and always includesupport in the keyspan_pda driver.Note that all configs that enabled CONFIG_USB_SERIAL_XIRCOM also enableCONFIG_USB_SERIAL_KEYSPAN_PDA.Acked-by: Sebastian Andrzej Siewior Reviewed-by: Greg Kroah-Hartman Signed-off-by: Johan Hovold List of files: /linux-6.15/drivers/usb/serial/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/serial/Makefile

ea534e0b - USB: serial: add uPD78F0730 USB to Serial Adaptor Driver

Wed, 25 Jan 2017 20:40:40 +0000

USB: serial: add uPD78F0730 USB to Serial Adaptor DriverThe adaptor can be found on development boards for 78k, RL78 and V850microcontrollers produced by Renesas Electronics Corporation.This is not a full-featured USB to serial converter, however it allowsbasic communication and simple control which is enough for programming ofon-board flash and debugging through a debug monitor.uPD78F0730 is a USB-enabled microcontroller with USB-to-UART conversionimplemented in firmware.This chip is also present in some debugging adaptors which use it forUSB-to-SPI conversion as well. The present driver doesn't cover SPI,only USB-to-UART conversion is supported.Signed-off-by: Maksim Salau Signed-off-by: Johan Hovold List of files: /linux-6.15/drivers/usb/serial/Makefile

0c9bd600 - USB: serial: add Fintek F81532/534 driver

Mon, 14 Nov 2016 05:37:59 +0000

USB: serial: add Fintek F81532/534 driverThis driver is for Fintek F81532/F81534 USB to Serial Ports IC.F81532 spec:https://drive.google.com/file/d/0B8vRwwYO7aMFOTRRMmhWQVNvajQ/view?usp=sharingF81534 spec:https://drive.google.com/file/d/0B8vRwwYO7aMFV29pQWJqbVBNc00/view?usp=sharingFeatures:1. F81532 is 1-to-2 & F81534 is 1-to-4 serial ports IC2. Support Baudrate from B50 to B115200.Signed-off-by: Ji-Ze Hong (Peter Hong) Signed-off-by: Johan Hovold List of files: /linux-6.15/drivers/usb/serial/Makefile

537b8a86 - Revert "USB: serial: add Moxa UPORT 11x0 driver"

Mon, 29 Feb 2016 17:56:02 +0000

Revert "USB: serial: add Moxa UPORT 11x0 driver"This reverts commit 0b2b093ad405b56a9e6f4f20a25da77ebfa9549c.Turns out the MOXA vendor driver was basically just a copy of theti_usb_3410_5052 driver. We don't want two drivers for the same chipeven if mxu11x0 had gotten some much needed clean up before merge. Solet's remove the mxu11x0 driver, add support for these Moxa devices tothe TI driver, and then clean that driver up instead.Signed-off-by: Johan Hovold Acked-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/usb/serial/Makefile

0b2b093a - USB: serial: add Moxa UPORT 11x0 driver

Mon, 28 Dec 2015 20:21:25 +0000

USB: serial: add Moxa UPORT 11x0 driverAdd a driver which supports :- UPort 1110 : 1 port RS-232 USB to Serial Hub.- UPort 1130 : 1 port RS-422/485 USB to Serial Hub.- UPort 1130I : 1 port RS-422/485 USB to Serial Hub with Isolation.- UPort 1150 : 1 port RS-232/422/485 USB to Serial Hub.- UPort 1150I : 1 port RS-232/422/485 USB to Serial Hub with Isolation.This driver is based on GPL MOXA driver written by Hen Huang and availableon MOXA website. The original driver was based on io_ti serial driver.Signed-off-by: Mathieu OTHACEHE Signed-off-by: Johan Hovold List of files: /linux-6.15/drivers/usb/serial/Makefile

f8c0e057 - USB: serial: remove zte_ev driver

Mon, 15 Sep 2014 16:40:45 +0000

USB: serial: remove zte_ev driverThe zte_ev driver is based on code (once) distributed by ZTE that stillappears to originally have been reverse-engineered and bolted onto thegeneric driver.A closer analysis of the zte_ev setup code reveals that it consists ofstandard CDC requests (SET/GET_LINE_CODING and SET_CONTROL_LINE_STATE)but unfortunately fails to get some of those right. In particular, asreported by Lei Liu, it fails to lower DTR/RTS on close. It also appearsthat the control requests lack the interface argument.Since line control is already handled properly by the option driver, andthe SET/GET_LINE_CODING requests appears to be redundant (amounts to aSET 9600 8N1) let's remove the redundant zte_ev driver.Also move the remaining ZTE PIDs to the generic option modem driver.Reported-by: Lei Liu Signed-off-by: Johan Hovold List of files: /linux-6.15/drivers/usb/serial/Makefile

ee467a1f - USB: serial: add Moxa UPORT 12XX/14XX/16XX driver

Sun, 29 Dec 2013 18:23:17 +0000

USB: serial: add Moxa UPORT 12XX/14XX/16XX driverAdd a driver which supports the following Moxa USB to serial converters:* 2 ports : UPort 1250, UPort 1250I* 4 ports : UPort 1410, UPort 1450, UPort 1450I* 8 ports : UPort 1610-8, UPort 1650-8* 16 ports : UPort 1610-16, UPort 1650-16The UPORT devices don't directly fit the USB serial model. USB serialassumes a bulk in/out endpoint pair per serial port. Thus a dual portUSB serial device is expected to have two bulk in/out pairs. The MoxaUPORT only has one pair for data transfer and places a header on eachtransfer over the endpoint indicating for which port the transferrelates to. There is a second endpoint pair for events, such as modemcontrol lines changing state, setting baud rates etc. Again, amultiplexing header is used on these endpoints.Some ports need to have a kfifo explicitly allocated since theframework does not allocate one if there is no associated endpoints.The framework will however free it on unload of the module.All data transfers are made on port0, yet the locks are taken on PortN.urb->context points to PortN, even though the URB is for port0.Where possible, code from the generic driver is called. Howevermxuport_process_read_urb_data() is mostly a cut/paste ofusb_serial_generic_process_read_urb().The driver will attempt to load firmware from userspace and comparethe available version and the running version. If the availableversion is newer, it will be download into RAM of the device andstarted. This is optional and the driver appears to work O.K. witholder firmware in the devices ROM.This driver is based on the MOXA driver and retains MOXAs copyright.[jhovold@gmail.com: fix get_fw_version error path and some style issues]Signed-off-by: Andrew Lunn Reviewed-by: Johan Hovold Signed-off-by: Johan Hovold Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/usb/serial/Makefile

1f923071 - USB: serial: move the "simple" drivers into usb-serial-simple.c

Mon, 05 Aug 2013 11:27:19 +0000

USB: serial: move the "simple" drivers into usb-serial-simple.cInstead of having to create a new driver for a "simple" usb to serialdevice, mush them all into one file, with a macro, so as to make it easyto add new ones.Cc: "René Bürgel" Acked-by: Wei Shuai Cc: Josh Triplett Acked-by: Frans Klaver Cc: "Wesley W. Terpstra" Cc: Johan Hovold Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/usb/serial/Makefile

a8825734 - USB: serial: add driver for Suunto ANT+ USB device

Fri, 26 Jul 2013 04:52:29 +0000

USB: serial: add driver for Suunto ANT+ USB deviceThis adds a driver for the Suunto ANT+ USB device, exposing it as a usbserial device. This lets the userspace "gant" program to talk to thedevice to communicate over the ANT+ protocol to any devices it finds.Reported-by: Steinar Gunderson Tested-by: Steinar Gunderson Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/usb/serial/Makefile

88f3ec27 - USB: serial: add support Infineon modem USB flashloader driver

Wed, 29 May 2013 15:05:56 +0000

USB: serial: add support Infineon modem USB flashloader driverIf you want to download Infineon modem via USB, this Infineon USBflashloader driver is required.Signed-off-by: Wei Shuai Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/usb/serial/Makefile

1157f69b - usb-serial: add support for USB Wishbone-serial adapters

Thu, 11 Apr 2013 13:08:20 +0000

usb-serial: add support for USB Wishbone-serial adaptersWishbone is an open hardware SoC bus commonly used in FPGAdesigns. Bus access can be serialized using the Etherboneprotocol .This driver is intended to be used with devices which attachtheir internal Wishbone bus to a USB serial interface usingthe Etherbone protocol. A userspace library is required tospeak the protocol made available by this driver as ttyUSBx.Signed-off-by: Wesley W. Terpstra Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/usb/serial/Makefile

59e931c4 - usb: add driver for xsens motion trackers

Fri, 25 Jan 2013 16:05:44 +0000

usb: add driver for xsens motion trackersSigned-off-by: Frans Klaver Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/usb/serial/Makefile

70c048a2 - USB: ezusb: move ezusb.c from drivers/usb/serial to drivers/usb/misc

Wed, 26 Sep 2012 20:20:19 +0000

USB: ezusb: move ezusb.c from drivers/usb/serial to drivers/usb/miscThis patch- moves drivers/usb/serial/ezusb.c to drivers/usb/misc/- renamed CONFIG_USB_EZUSB to CONFIG_USB_EZUSB_FX2 to avoid build errors- adapts Makefiles and Kconfigs switching from bool to tristate for CONFIG_USB_EZUSB_FX2Signed-off-by: René Bürgel Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/usb/serial/Makefile

64f0d8cd - USB: serial: remove vizzini driver

Mon, 24 Sep 2012 19:42:19 +0000

USB: serial: remove vizzini driverIt's out-dated for the tty-layer stuff, and would require a bunch ofwork. That's not really a big deal, the big issue is that there is nocompany contact for the hardware, so questions we have about it (likewhy isn't this just handled by the cdc-acm driver instead?) gounanswered.So drop the driver. If someone comes along to help answer thequestions, we can easily revert this and fix up the code.Cc: Alan Cox Cc: Rob Duncan Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/usb/serial/Makefile

c05fecb1 - USB: serial: add vizzini driver

Tue, 18 Sep 2012 05:53:32 +0000

USB: serial: add vizzini driverHere's a driver for the Vizzini USB to serial device.It looks to be copied from cdc-acm, and probably can be cleaned up a lotmore. Also, there's some odd "try to grab another interface" that isprobably wrong. And, if this really is a cdc-acm device, it probablyshould just be a quirk of the cdc-acm device, but I can't figure thatout, and people have been using this driver for a long time now. Somerge it to let people use their hardware and clean it up over time.Driver written by Rob Duncan but cleaned up and forward ported to thelatest kernel tree by me.Cc: Rob Duncan Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/usb/serial/Makefile

799ee924 - USB: serial: add zte_ev.c driver

Fri, 17 Aug 2012 23:59:51 +0000

USB: serial: add zte_ev.c driverThis adds a driver for the zte_ev set of usb to serial devices. It isbased on a patch floating around the internet that modified the genericusb-serial driver to only work for this type of device.I've left comments in the code that I think show the data commands beingsent to the device, which I'm guessing come from a usb analyzer. Maybethey can help others out as well.Many thanks to nirinA raseliarison for pointing the original patch outto me, and for testing that the driver works properly.Tested-by: nirinA raseliarison Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/usb/serial/Makefile

f7a33e60 - USB: serial: add quatech2 usb to serial driver

Thu, 10 May 2012 19:36:02 +0000

USB: serial: add quatech2 usb to serial driverThis supports the Quatech USB 2 usb to serial adapters.Signed-off-by: Bill Pemberton Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/usb/serial/Makefile

62f2a83d - USB: serial: metro-usb: add to the build

Thu, 08 Mar 2012 21:34:01 +0000

USB: serial: metro-usb: add to the buildThis adds the metro-usb driver to the build system properly.Cc: Aleksey Babahin Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/usb/serial/Makefile