Changes in Makefile

ff60bfba - can: rockchip_canfd: add driver for Rockchip CAN-FD controller

Wed, 11 Oct 2023 14:02:32 +0000

can: rockchip_canfd: add driver for Rockchip CAN-FD controllerAdd driver for the Rockchip CAN-FD controller.The IP core on the rk3568v2 SoC has 12 documented errata. Correctionsfor these errata will be added in the upcoming patches.Since several workarounds are required for the TX path, only add thebase driver that only implements the RX path.Although the RX path implements CAN-FD support, it's not activated inctrlmode_supported, as the IP core in the rk3568v2 has problems withreceiving or sending certain CAN-FD frames.Tested-by: Alibek Omarov Acked-by: Heiko Stuebner Link: https://patch.msgid.link/20240904-rockchip-canfd-v5-4-8ae22bcb27cc@pengutronix.deSigned-off-by: Marc Kleine-Budde List of files: /linux-6.15/drivers/net/can/Makefile

9721866f - can: esd: add support for esd GmbH PCIe/402 CAN interface family

Wed, 22 Nov 2023 16:02:11 +0000

can: esd: add support for esd GmbH PCIe/402 CAN interface familyThis patch adds support for the PCI based PCIe/402 CAN interface familyfrom esd GmbH that is available with various form factors(https://esd.eu/en/products/402-series-can-interfaces).All boards utilize a FPGA based CAN controller solution developedby esd (esdACC). For more information on the esdACC seehttps://esd.eu/en/products/esdacc.This driver detects all available CAN interface board variants ofthe family but atm. operates the CAN-FD capable devices inClassic-CAN mode only! A later patch will introduce the CAN-FDfunctionality in this driver.Co-developed-by: Thomas Körper Signed-off-by: Thomas Körper Signed-off-by: Stefan Mätje Link: https://lore.kernel.org/all/20231122160211.2110448-3-stefan.maetje@esd.euSigned-off-by: Marc Kleine-Budde List of files: /linux-6.15/drivers/net/can/Makefile

f00647d8 - can: bxcan: add support for ST bxCAN controller

Tue, 28 Mar 2023 07:33:28 +0000

can: bxcan: add support for ST bxCAN controllerAdd support for the basic extended CAN controller (bxCAN) found in manylow- to middle-end STM32 SoCs. It supports the Basic Extended CANprotocol versions 2.0A and B with a maximum bit rate of 1 Mbit/s.The controller supports two channels (CAN1 as primary and CAN2 assecondary) and the driver can enable either or both of the channels. Theyshare some of the required logic (e. g. clocks and filters), and that meansyou cannot use the secondary CAN without enabling some hardware resourcesmanaged by the primary CAN.Each channel has 3 transmit mailboxes, 2 receive FIFOs with 3 stages and28 scalable filter banks.It also manages 4 dedicated interrupt vectors:- transmit interrupt- FIFO 0 receive interrupt- FIFO 1 receive interrupt- status change error interruptDriver uses all 3 available mailboxes for transmission and FIFO 0 forreception. Rx filter rules are configured to the minimum. They acceptall messages and assign filter 0 to CAN1 and filter 14 to CAN2 inidentifier mask mode with 32 bits width. It enables and uses transmit,receive buffers for FIFO 0 and error and status change interrupts.Signed-off-by: Dario Binacchi Reviewed-by: Vincent Mailhol Link: https://lore.kernel.org/all/20230328073328.3949796-6-dario.binacchi@amarulasolutions.comSigned-off-by: Marc Kleine-Budde List of files: /linux-6.15/drivers/net/can/Makefile

1dd1b521 - can: remove obsolete PCH CAN driver

Sat, 24 Sep 2022 17:44:24 +0000

can: remove obsolete PCH CAN driverThe PCH CAN driver is a driver for a Bosch C_CAN controller IP core whichis attached to the system via PCI. This code has been introduced in 2011by Oki Semiconductors developers to support the Intel Atom E6xx seriesI/O Hub (aka EG20T IOH PCH CAN). Since 2012 the driver only has beenmaintained by the kernel community.As there is a well maintained and continously tested C_CAN/D_CAN driverwhich also supports the PCI configuration from the PCH CAN EG20T setupthis driver became obsolete.Cc: Jacob Kroon Cc: Marc Kleine-Budde Cc: Dario Binacchi Cc: Wolfgang Grandegger Signed-off-by: Oliver Hartkopp Link: https://lore.kernel.org/all/20220924174424.86541-1-socketcan@hartkopp.netAcked-by: Jacob Kroon Signed-off-by: Marc Kleine-Budde List of files: /linux-6.15/drivers/net/can/Makefile

98b12064 - can: slcan: move driver into separate sub directory

Tue, 28 Jun 2022 16:31:33 +0000

can: slcan: move driver into separate sub directoryThis patch moves the slcan driver into a separate directory, a laterpatch will add more files.Link: https://lore.kernel.org/all/20220628163137.413025-10-dario.binacchi@amarulasolutions.comSigned-off-by: Dario Binacchi Signed-off-by: Marc Kleine-Budde List of files: /linux-6.15/drivers/net/can/Makefile

43da2f07 - can: can327: CAN/ldisc driver for ELM327 based OBD-II adapters

Sat, 18 Jun 2022 19:50:31 +0000

can: can327: CAN/ldisc driver for ELM327 based OBD-II adaptersThis is the can327 driver. It does a surprisingly good job at turningELM327 based OBD-II interfaces into cheap CAN interfaces for simplehomebrew projects.Please see the included documentation for details and limitations:Documentation/networking/device_drivers/can/can327.rstLink: https://lore.kernel.org/all/20220618195031.10975-1-max@enpas.orgSigned-off-by: Max Staudt Reviewed-by: Vincent Mailhol [mkl: minor coding style improvements]Signed-off-by: Marc Kleine-Budde List of files: /linux-6.15/drivers/net/can/Makefile

2dcb8e87 - can: ctucanfd: add support for CTU CAN FD open-source IP core - bus independent part.

Mon, 21 Mar 2022 23:32:30 +0000

can: ctucanfd: add support for CTU CAN FD open-source IP core - bus independent part.This driver adds support for the CTU CAN FD open-source IP core.More documentation and core sources at project page(https://gitlab.fel.cvut.cz/canbus/ctucanfd_ip_core).The core integration to Xilinx Zynq system as platform driveris available (https://gitlab.fel.cvut.cz/canbus/zynq/zynq-can-sja1000-top).Implementation on Intel FPGA based PCI Express board is availablefrom project (https://gitlab.fel.cvut.cz/canbus/pcie-ctucanfd).More about CAN bus related projects used and developed at CTU FEE athttps://canbus.pages.fel.cvut.cz/ .Link: https://lore.kernel.org/all/1906e4941560ae2ce4b8d181131fd4963aa31611.1647904780.git.pisa@cmp.felk.cvut.czSigned-off-by: Martin Jerabek Signed-off-by: Ondrej Ille Signed-off-by: Pavel Pisa Signed-off-by: Marc Kleine-Budde List of files: /linux-6.15/drivers/net/can/Makefile

bfd00e02 - can: flexcan: move driver into separate sub directory

Tue, 04 Jan 2022 15:15:01 +0000

can: flexcan: move driver into separate sub directoryThis patch moves the flexcan driver into a separate directory, a laterpatch will add more files.Link: https://lore.kernel.org/all/20220107193105.1699523-2-mkl@pengutronix.deSigned-off-by: Marc Kleine-Budde List of files: /linux-6.15/drivers/net/can/Makefile

3e77f70e - can: dev: move driver related infrastructure into separate subdir

Mon, 11 Jan 2021 14:19:17 +0000

can: dev: move driver related infrastructure into separate subdirThis patch moves the CAN driver related infrastructure into a separate subdir.It will be split into more files in the coming patches.Reviewed-by: Vincent Mailhol Link: https://lore.kernel.org/r/20210111141930.693847-3-mkl@pengutronix.deSigned-off-by: Marc Kleine-Budde List of files: /linux-6.15/drivers/net/can/Makefile

26ad340e - can: kvaser_pciefd: Add driver for Kvaser PCIEcan devices

Tue, 28 May 2019 12:48:21 +0000

can: kvaser_pciefd: Add driver for Kvaser PCIEcan devicesThis patch adds support for Kvaser PCIEcan devices. This includessupport for up to 4 CAN channels on a single card, depending on device.Signed-off-by: Henning Colliander Signed-off-by: Jimmy Assarsson Signed-off-by: Christer Beskow Signed-off-by: Marc Kleine-Budde List of files: /linux-6.15/drivers/net/can/Makefile

c7b2d3e5 - can: remove bfin_can driver

Fri, 09 Mar 2018 17:18:54 +0000

can: remove bfin_can driverThe blackfin architecture is getting removed, so this one is now obsolete.Acked-by: Aaron Wu Signed-off-by: Arnd Bergmann List of files: /linux-6.15/drivers/net/can/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/net/can/Makefile

a8f820a3 - can: add Virtual CAN Tunnel driver (vxcan)

Tue, 25 Apr 2017 06:19:44 +0000

can: add Virtual CAN Tunnel driver (vxcan)Similar to the virtual ethernet driver veth, vxcan implements alocal CAN traffic tunnel between two virtual CAN network devices.See Kconfig entry for details.Signed-off-by: Oliver Hartkopp Signed-off-by: Marc Kleine-Budde List of files: /linux-6.15/drivers/net/can/Makefile

8ac8321e - can: peak: add support for PEAK PCAN-PCIe FD CAN-FD boards

Thu, 19 Jan 2017 15:31:07 +0000

can: peak: add support for PEAK PCAN-PCIe FD CAN-FD boardsThis patch adds the support of the PCAN-PCI Express FD boards madeby PEAK-System, for computers using the PCI Express slot.The PCAN-PCI Express FD has one or two CAN FD channels, dependingon the model. A galvanic isolation of the CAN ports protectsthe electronics of the card and the respective computer againstdisturbances of up to 500 Volts. The PCAN-PCI Express FD can be operatedwith ambient temperatures in a range of -40 to +85 °C.Such boards run an extented version of the CAN-FD IP running into USBCAN-FD interfaces from PEAK-System, so this patch adds several new commandsand their corresponding data types to the PEAK CAN-FD common definitionsheader file too.Signed-off-by: Stephane Grosjean Signed-off-by: Marc Kleine-Budde List of files: /linux-6.15/drivers/net/can/Makefile

d254586c - can: rx-offload: Add support for HW fifo based irq offloading

Fri, 10 Oct 2014 15:30:10 +0000

can: rx-offload: Add support for HW fifo based irq offloadingSome CAN controllers have a usable FIFO already but can still benefitfrom off-loading the CAN controller FIFO. The CAN frames of the FIFO areread and put into a skb queue during interrupt and then transmitted in aNAPI context.Signed-off-by: David Jander Signed-off-by: Marc Kleine-Budde List of files: /linux-6.15/drivers/net/can/Makefile

6bdf1e0e - Makefile: drop -D__CHECK_ENDIAN__ from cflags

Thu, 15 Dec 2016 02:07:46 +0000

Makefile: drop -D__CHECK_ENDIAN__ from cflagsThat's the default now, no need for makefiles to set it.Signed-off-by: Michael S. Tsirkin Acked-by: Kalle Valo Acked-by: Marcel Holtmann Acked-by: Marc Kleine-Budde Acked-by: Greg Kroah-Hartman Acked-by: Arend van Spriel List of files: /linux-6.15/drivers/net/can/Makefile

a23b97e6 - can: rcar_can: Move Renesas CAN driver to rcar dir

Fri, 17 Jun 2016 08:20:56 +0000

can: rcar_can: Move Renesas CAN driver to rcar dirThis patch clubs the Renesas controller drivers in one rcar dir.Signed-off-by: Ramesh Shanmugasundaram Signed-off-by: Marc Kleine-Budde List of files: /linux-6.15/drivers/net/can/Makefile

dd3bd23e - can: rcar_canfd: Add Renesas R-Car CAN FD driver

Fri, 17 Jun 2016 08:20:55 +0000

can: rcar_canfd: Add Renesas R-Car CAN FD driverThis patch adds support for the CAN FD controller found in Renesas R-CarSoCs. The controller operates in CAN FD only mode by default.CAN FD mode supports both Classical CAN & CAN FD frame formats. Thecontroller supports ISO 11898-1:2015 CAN FD format only.This controller supports two channels and the driver can enable eitheror both of the channels.Driver uses Rx FIFOs (one per channel) for reception & Common FIFOs (oneper channel) for transmission. Rx filter rules are configured to theminimum (one per channel) and it accepts Standard, Extended, Data &Remote Frame combinations.Note: There are few documentation errors in R-Car Gen3 Hardware UserManual v0.5E with respect to CAN FD controller. They are listed below:1. CAN FD interrupt numbers 29 & 30 are listed as per channelinterrupts. However, they are common to both channels (i.e.) they areglobal and channel interrupts respectively.2. CANFD clock is derived from PLL1. This is not documented.3. CANFD clock is further divided by (1/2) within the CAN FD controller.This is not documented.4. The minimum value of NTSEG1 in RSCFDnCFDCmNCFG register is 2 Tq. Itis specified 4 Tq in the manual.5. The maximum number of message RAM area the controller can use is 3584bytes. It is specified 10752 bytes in the manual.Signed-off-by: Ramesh Shanmugasundaram Acked-by: Rob Herring Reviewed-by: Ulrich Hecht Signed-off-by: Marc Kleine-Budde List of files: /linux-6.15/drivers/net/can/Makefile

0c4d9c94 - can: ifi: Add IFI CANFD IP support

Wed, 20 Jan 2016 14:33:39 +0000

can: ifi: Add IFI CANFD IP supportThe patch adds support for IFI CAN/FD controller [1]. This drivercurrently supports sending and receiving both standard CAN and newCAN/FD frames. Both ISO and BOSCH variant of CAN/FD is supported.[1] http://www.ifi-pld.de/IP/CANFD/canfd.htmlSigned-off-by: Marek Vasut Cc: Marc Kleine-Budde Cc: Mark Rutland Cc: Oliver Hartkopp Cc: Wolfgang Grandegger Signed-off-by: Marc Kleine-Budde List of files: /linux-6.15/drivers/net/can/Makefile

47338082 - can: Makefile: Sort the Makefile

Mon, 11 Jan 2016 18:48:00 +0000

can: Makefile: Sort the MakefileJust sort the drivers in the Makefile, no functional change.Signed-off-by: Marek Vasut Cc: Marc Kleine-Budde Cc: Mark Rutland Cc: Oliver Hartkopp Cc: Wolfgang Grandegger Signed-off-by: Marc Kleine-Budde List of files: /linux-6.15/drivers/net/can/Makefile