Changes in Makefile

7c0408d8 - tty: add rpmsg driver

Fri, 15 Oct 2021 09:47:01 +0000

tty: add rpmsg driverThis driver exposes a standard TTY interface on top of the rpmsgframework through a rpmsg service.This driver supports multi-instances, offering a /dev/ttyRPMSGx entryper rpmsg endpoint.Reviewed-by: Mathieu Poirier Signed-off-by: Arnaud Pouliquen Link: https://lore.kernel.org/r/20211015094701.5732-3-arnaud.pouliquen@foss.st.comSigned-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/tty/Makefile

ed5aecd3 - tty: remove broken r3964 line discipline

Wed, 05 May 2021 09:18:54 +0000

tty: remove broken r3964 line disciplineNoone stepped up in the past two years since it was marked as BROKEN bycommit c7084edc3f6d (tty: mark Siemens R3964 line discipline as BROKEN).Remove the line discipline for good.Three remarks:* we remove also the uapi header (as noone is able to use that interface anyway)* we do *not* remove the N_R3964 constant definition from tty.h, so it remains reserved.* in_interrupt() check is now removed from vt's con_put_char. Noone else calls tty_operations::put_char from interrupt context.Signed-off-by: Jiri Slaby Link: https://lore.kernel.org/r/20210505091928.22010-2-jslaby@suse.czSigned-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/tty/Makefile

3b00b6af - tty: rocket, remove the driver

Tue, 02 Mar 2021 06:21:37 +0000

tty: rocket, remove the driverWhile the driver is still marked as maintained in MAINTAINERS, Comtroldoes not really care about this ancient driver. They are stillmanufacturing serial devices, but those are controlled only byout-of-tree drivers.Comtrol didn't answer my pings, so this driver is apparentlyunmaintained. Aside from that, the driver was untouched for years, onlywhole-tree changes happened during the past years. The driver needs muchmore care, so drop it for now. If someone steps up to reintroduce it,they need to clean it up first.Signed-off-by: Jiri Slaby Link: https://lore.kernel.org/r/20210302062214.29627-7-jslaby@suse.czSigned-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/tty/Makefile

67b1544a - tty: isicom, remove this orphan

Tue, 02 Mar 2021 06:21:36 +0000

tty: isicom, remove this orphanThe Isicom driver was orphaned by commit d86b3001a1a6 (MAINTAINERS:orphan isicom) 10 years ago. Noone stepped up to take care of them andto fix all the issues the driver has.So it's time to drop the driver with all its traces.Signed-off-by: Jiri Slaby Link: https://lore.kernel.org/r/20210302062214.29627-6-jslaby@suse.czSigned-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/tty/Makefile

f76edd8f - tty: cyclades, remove this orphan

Tue, 02 Mar 2021 06:21:35 +0000

tty: cyclades, remove this orphanThe Cyclades driver was orphaned by commit d459883e6c54 (MAINTAINERS:remove two dead e-mail) 13 years ago. Noone stepped up to take care ofthem and to fix all the issues the driver has.On the top of that, there is no way to obtain the firmware for Z cardsfrom the vendor as cyclades.com ceased to exist.So it's time to drop the driver with all its traces.Signed-off-by: Jiri Slaby Link: https://lore.kernel.org/r/20210302062214.29627-5-jslaby@suse.czSigned-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/tty/Makefile

8ba59e9d - misc: pti: Remove driver for deprecated platform

Fri, 22 Jan 2021 11:43:58 +0000

misc: pti: Remove driver for deprecated platformIntel Moorestown and Medfield are quite old Intel Atom based32-bit platforms, which were in limited use in some Android phones,tablets and consumer electronics more than eight years ago.There are no bugs or problems ever reported outside from Intelfor breaking any of that platforms for years. It seems no realusers exists who run more or less fresh kernel on it. The commit05f4434bc130 ("ASoC: Intel: remove mfld_machine") also in alignwith this theory.Due to above and to reduce a burden of supporting outdated driverswe remove the support of outdated platforms completely.Cc: Alexander Shishkin Acked-by: Linus Walleij Acked-by: Arnd Bergmann Acked-by: Alexander Shishkin Signed-off-by: Andy Shevchenko Link: https://lore.kernel.org/r/20210122114358.39299-1-andriy.shevchenko@linux.intel.comSigned-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/tty/Makefile

a91bd622 - Revert "init/console: Use ttynull as a fallback when there is no console"

Fri, 08 Jan 2021 11:48:47 +0000

Revert "init/console: Use ttynull as a fallback when there is no console"This reverts commit 757055ae8dedf5333af17b3b5b4b70ba9bc9da4e.The commit caused that ttynull was used as the default consoleon several systems[1][2][3]. As a result, the console wasblank even when a better alternative existed.It happened when there was no console configuredon the command line and ttynull_init() was the first initcallcalling register_console().Or it happened when /dev/ did not exist when console_on_rootfs()was called. It was not able to open /dev/console even thougha console driver was registered. It tried to add ttynull consolebut it obviously did not help. But ttynull became the preferredconsole and was used by /dev/console when it was available later.The commit tried to fix a historical problem that have been therefor ages. The primary motivation was the commit 3cffa06aeef7ece30f6("printk/console: Allow to disable console output by using console="" or console=null"). It provided a clean solution for a workaround that was widely used and worked only by chance.This revert causes that the console="" or console=null command lineoptions will again work only by chance. These options will cause thata particular console will be preferred and the default (tty) oneswill not get enabled. There will be no console registered atall. As a result there won't be stdin, stdout, and stderr forthe init process. But it worked exactly this way even before.The proper solution has to fulfill many conditions: + Register ttynull only when explicitly required or as the ultimate fallback. + ttynull should get associated with /dev/console but it must not become preferred console when used as a fallback. Especially, it must still be possible to replace it by a better console later.Such a change requires clean up of the register_console() code.Otherwise, it would be even harder to follow. Especially, the useof has_preferred_console and CON_CONSDEV flag is tricky. The cleanup is risky. The ordering of consoles is not well defined. Andany changes tend to break existing user settings.Do the revert at the least risky solution for now.[1] https://lore.kernel.org/linux-kselftest/20201221144302.GR4077@smile.fi.intel.com/[2] https://lore.kernel.org/lkml/d2a3b3c0-e548-7dd1-730f-59bc5c04e191@synopsys.com/[3] https://patchwork.ozlabs.org/project/linux-um/patch/20210105120128.10854-1-thomas@m3y3r.de/Reported-by: Andy Shevchenko Reported-by: Vineet Gupta Reported-by: Thomas Meyer Signed-off-by: Petr Mladek Acked-by: Greg Kroah-Hartman Acked-by: Sergey Senozhatsky Signed-off-by: Linus Torvalds List of files: /linux-6.15/drivers/tty/Makefile

757055ae - init/console: Use ttynull as a fallback when there is no console

Wed, 11 Nov 2020 13:54:49 +0000

init/console: Use ttynull as a fallback when there is no consolestdin, stdout, and stderr standard I/O stream are created for the initprocess. They are not available when there is no console registeredfor /dev/console. It might lead to a crash when the init processtries to use them, see the commit 48021f98130880dd742 ("printk: handleblank console arguments passed in.").Normally, ttySX and ttyX consoles are used as a fallback when no consolesare defined via the command line, device tree, or SPCR. But therewill be no console registered when an invalid console name is configuredor when the configured consoles do not exist on the system.Users even try to avoid the console intentionally, for example,by using console="" or console=null. It is used on productionsystems where the serial port or terminal are not visible tousers. Pushing messages to these consoles would just unnecessaryslowdown the system.Make sure that stdin, stdout, stderr, and /dev/console are alwaysavailable by a fallback to the existing ttynull driver. It hasbeen implemented for exactly this purpose but it was used onlywhen explicitly configured.Reviewed-by: Greg Kroah-Hartman Reviewed-by: Guenter Roeck Tested-by: Guenter Roeck Acked-by: Sergey Senozhatsky Signed-off-by: Petr Mladek Link: https://lore.kernel.org/r/20201111135450.11214-2-pmladek@suse.com List of files: /linux-6.15/drivers/tty/Makefile

3d608a59 - tty: Remove redundant synclinkmp driver

Thu, 05 Nov 2020 12:33:57 +0000

tty: Remove redundant synclinkmp driverA note from the vendor: "The hardware used with synclink.c and synclinkmp.c has not been manufactured for 15 years and was low volume. The chances of either driver still being in use is very low. Not even Microgate (me) has the ability to test either anymore (no hardware). I don’t know the policy about driver removal, but I think both could be removed without upsetting anyone."Cc: Michael Ellerman Cc: Benjamin Herrenschmidt Cc: Paul Mackerras Cc: Greg Kroah-Hartman Cc: Jiri Slaby Cc: linuxppc-dev@lists.ozlabs.orgSigned-off-by: Lee Jones Link: https://lore.kernel.org/r/20201105123357.708813-3-lee.jones@linaro.orgSigned-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/tty/Makefile

a1f714b4 - tty: Remove redundant synclink driver

Thu, 05 Nov 2020 12:33:56 +0000

tty: Remove redundant synclink driverA note from the vendor: "The hardware used with synclink.c and synclinkmp.c has not been manufactured for 15 years and was low volume. The chances of either driver still being in use is very low. Not even Microgate (me) has the ability to test either anymore (no hardware). I don’t know the policy about driver removal, but I think both could be removed without upsetting anyone."Cc: Michael Ellerman Cc: Benjamin Herrenschmidt Cc: Paul Mackerras Cc: Greg Kroah-Hartman Cc: Jiri Slaby Cc: linuxppc-dev@lists.ozlabs.orgSigned-off-by: Lee Jones Link: https://lore.kernel.org/r/20201105123357.708813-2-lee.jones@linaro.orgSigned-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/tty/Makefile

3117ff13 - tty: Add NULL TTY driver

Wed, 03 Apr 2019 11:33:27 +0000

tty: Add NULL TTY driverIf no console driver is enabled (or if a non-present driver is selectedwith something like console=null in an attempt to disable the console),opening /dev/console errors out, and init scripts and other userspacecode that relies on the existence of a console will fail. Symlinking/dev/null to /dev/console does not solve the problem since /dev/nulldoes not behave like a real TTY.To just provide a dummy console to userspace when no console driver isavailable or desired, add a ttynull driver which simply discards allwrites. It can be chosen on the command line in the standard way, i.e.with console=ttynull.Signed-off-by: Vincent Whitchurch Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/tty/Makefile

e6bf3cc5 - tty: remove bfin_jtag_comm and hvc_bfin_jtag drivers

Fri, 09 Mar 2018 16:16:06 +0000

tty: remove bfin_jtag_comm and hvc_bfin_jtag driversThe blackfin architecture is getting removed, so these driversare not needed any more.Acked-by: Greg Kroah-Hartman Acked-by: Aaron Wu Signed-off-by: Arnd Bergmann List of files: /linux-6.15/drivers/tty/Makefile

5ba484e7 - tty: Remove metag DA TTY and console driver

Wed, 21 Feb 2018 15:37:54 +0000

tty: Remove metag DA TTY and console driverNow that arch/metag/ has been removed, remove the metag DA TTY andconsole driver. It is of no value without the architecture code.Signed-off-by: James Hogan Acked-by: Greg Kroah-Hartman Cc: Jiri Slaby Cc: linux-metag@vger.kernel.org List of files: /linux-6.15/drivers/tty/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/tty/Makefile

55bd2133 - sparc64: vcc: Enable VCC module in linux

Tue, 15 Aug 2017 21:02:57 +0000

sparc64: vcc: Enable VCC module in linuxEnables the Virtual Console Concentrator (VCC) modulein linux kernelSigned-off-by: Jagannathan Raman Reviewed-by: Liam Merwick Reviewed-by: Shannon Nelson Signed-off-by: David S. Miller List of files: /linux-6.15/drivers/tty/Makefile

8a8dabf2 - tty: handle the case where we cannot restore a line discipline

Fri, 02 Jun 2017 12:49:30 +0000

tty: handle the case where we cannot restore a line disciplineHistorically the N_TTY driver could never fail but this has become broken overtime. Rather than trying to rewrite half the ldisc layer to fix the breakageintroduce a second level of fallback with an N_NULL ldisc which cannot fail,and thus restore the guarantees required by the ldisc layer.We still try and fail to N_TTY first. It's much more useful to find yourselfback in your old ldisc (first attempt) or in N_TTY (second attempt), and whileI'm not aware of any code out there that makes those assumptions it's good todrive(r) defensively.Signed-off-by: Alan Cox Reported-by: Dmitry Vyukov Tested-by: Dmitry Vyukov Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/tty/Makefile

a1235b3e - tty: split job control support into a file of its own

Wed, 12 Apr 2017 22:37:16 +0000

tty: split job control support into a file of its ownThis makes it easier for job control to become optional and/or usableindependently from tty_io.c, as well as providing a nice purposeseparation. No logical changes from this patch.Signed-off-by: Nicolas Pitre Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/tty/Makefile

fff0a2ca - tty: move baudrate handling code to a file of its own

Wed, 12 Apr 2017 22:37:15 +0000

tty: move baudrate handling code to a file of its ownTo allow reuse without the rest of the tty_ioctl code.No logical changes from this patch.Signed-off-by: Nicolas Pitre Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/tty/Makefile

cd6484e1 - serdev: Introduce new bus for serial attached devices

Thu, 02 Feb 2017 19:48:07 +0000

serdev: Introduce new bus for serial attached devicesThe serdev bus is designed for devices such as Bluetooth, WiFi, GPSand NFC connected to UARTs on host processors. Tradionally these havebeen handled with tty line disciplines, rfkill, and userspace glue suchas hciattach. This approach has many drawbacks since it doesn't fitinto the Linux driver model. Handling of sideband signals, power controland firmware loading are the main issues.This creates a serdev bus with controllers (i.e. host serial ports) andattached devices. Typically, these are point to point connections, butsome devices have muxing protocols or a h/w mux is conceivable. Anymuxing is not yet supported with the serdev bus.Signed-off-by: Rob Herring Reviewed-By: Sebastian Reichel Tested-By: Sebastian Reichel Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/tty/Makefile

4cebec60 - TTY: Add MIPS EJTAG Fast Debug Channel TTY driver

Thu, 29 Jan 2015 11:14:12 +0000

TTY: Add MIPS EJTAG Fast Debug Channel TTY driverAdd TTY driver and consoles for the MIPS EJTAG Fast Debug Channel (FDC),which is found on the per-CPU MIPS Common Device Mapped Memory (CDMM)bus.The FDC is a per-CPU device which is used to communicate with an EJTAGprobe. RX and TX FIFOs exist, containing 32-bits of data and 4-bitchannel numbers. 16 general data streams are implemented on this for TTYand console use by encoding up to 4 bytes on each 32-bit FDC word.The TTY devices are named e.g. /dev/ttyFDC3c2 for channel 2 of the FDCattached to logical CPU 3.These can be used for getting the kernel log, a login prompt, or as aGDB remote transport, all over EJTAG and without needing a serial port.It can have an interrupt to notify of when incoming data is available inthe RX FIFO or when the TX FIFO is no longer full. The detection of thisinterrupt occurs in architecture / platform code, but it may be sharedwith the timer and/or performance counter interrupt.Due to the per-CPU nature of the hardware, all outgoing TTY data iswritten out from a kthread which is pinned to the appropriate CPU.The console is not bound to a specific CPU, so output will appear on thechosen channel on whichever CPU the code is executing on. Enable withe.g. console=fdc1 in kernel arguments. /dev/console is bound to the samechannel on the boot CPU's FDC if it exists.Signed-off-by: James Hogan Cc: Ralf Baechle Cc: Greg Kroah-Hartman Cc: Jiri Slaby Cc: linux-mips@linux-mips.orgCc: linux-kernel@vger.kernel.orgPatchwork: https://patchwork.linux-mips.org/patch/9146/Signed-off-by: Ralf Baechle List of files: /linux-6.15/drivers/tty/Makefile