Changes in Makefile

cb7dd712 - octeon_ep_vf: Add driver framework and device initialization

Thu, 08 Feb 2024 10:18:33 +0000

octeon_ep_vf: Add driver framework and device initializationAdd driver framework and device setup and initialization for OcteonPCI Endpoint NIC VF.Add implementation to load module, initialize, register network device,cleanup and unload module.Signed-off-by: Shinas Rasheed Signed-off-by: David S. Miller List of files: /linux-6.15/drivers/net/ethernet/marvell/Makefile

63c7234f - Revert "octeon_ep_vf: add octeon_ep_vf driver"

Thu, 04 Jan 2024 21:00:44 +0000

Revert "octeon_ep_vf: add octeon_ep_vf driver"This reverts commit c902ba322cfda8ebe54ffd53392ef7e2ef5d1c65.This reverts commit 50648968b3e3c193b45eaca07840111c9d4fdb74.This reverts commit 77cef1e02104529f54c5b8b4126317eda3ff132d.This reverts commit 8f8d322bc47c1c5ecab1f2238b644e30f69cc475.This reverts commit 6ca7b5486ebd5e7985f0c98a2ac7ae49078043a4.This reverts commit db468f92c3b9437dfeb1dcf55d9b7d1b97769a6c.This reverts commit 5f8c64c2344c888a03fa4b7fd8c3b5e0c235d879.This reverts commit ebdc193b2ce209bfc1ebec2f777cd7bac00b547c.The driver needs more work.Signed-off-by: Jakub Kicinski List of files: /linux-6.15/drivers/net/ethernet/marvell/Makefile

ebdc193b - octeon_ep_vf: Add driver framework and device initialization

Sat, 23 Dec 2023 13:39:53 +0000

862cd659 - octeon_ep: Add driver framework and device initialization

Wed, 13 Apr 2022 03:34:57 +0000

octeon_ep: Add driver framework and device initializationAdd driver framework and device setup and initialization for OcteonPCI Endpoint NIC.Add implementation to load module, initilaize, register network device,cleanup and unload module.Signed-off-by: Veerasenareddy Burru Signed-off-by: Abhijit Ayarekar Signed-off-by: Satananda Burla Signed-off-by: David S. Miller List of files: /linux-6.15/drivers/net/ethernet/marvell/Makefile

501ef306 - net: marvell: prestera: Add driver for Prestera family ASIC devices

Wed, 16 Sep 2020 16:30:57 +0000

net: marvell: prestera: Add driver for Prestera family ASIC devicesMarvell Prestera 98DX326x integrates up to 24 ports of 1GbE with 8ports of 10GbE uplinks or 2 ports of 40Gbps stacking for a largelywireless SMB deployment.The current implementation supports only boards designed for the MarvellSwitchdev solution and requires special firmware.The core Prestera switching logic is implemented in prestera_main.c,there is an intermediate hw layer between core logic and firmware. It isimplemented in prestera_hw.c, the purpose of it is to encapsulate hwrelated logic, in future there is a plan to support more devices withdifferent HW related configurations.This patch contains only basic switch initialization and RX/TX supportover SDMA mechanism.Currently supported devices have DMA access range <= 32bit and requireZONE_DMA to be enabled, for such cases SDMA driver checks if the skballocated in proper range supported by the Prestera device.Also meanwhile there is no TX interrupt support in current firmwareversion so recycling work is scheduled on each xmit.Port's mac address is generated from the switch base mac which may beprovided via device-tree (static one or as nvme cell), or randomlygenerated. This is required by the firmware.Co-developed-by: Andrii Savka Signed-off-by: Andrii Savka Co-developed-by: Oleksandr Mazur Signed-off-by: Oleksandr Mazur Co-developed-by: Serhiy Boiko Signed-off-by: Serhiy Boiko Co-developed-by: Serhiy Pshyk Signed-off-by: Serhiy Pshyk Co-developed-by: Taras Chornyi Signed-off-by: Taras Chornyi Co-developed-by: Volodymyr Mytnyk Signed-off-by: Volodymyr Mytnyk Signed-off-by: Vadym Kochan Signed-off-by: David S. Miller List of files: /linux-6.15/drivers/net/ethernet/marvell/Makefile

54494aa5 - octeontx2-af: Add Marvell OcteonTX2 RVU AF driver

Wed, 10 Oct 2018 12:44:21 +0000

octeontx2-af: Add Marvell OcteonTX2 RVU AF driverThis patch adds basic template for Marvell OcteonTX2'sresource virtualization unit (RVU) admin function (AF)driver. Just the driver registration and probe.Signed-off-by: Sunil Goutham Signed-off-by: David S. Miller List of files: /linux-6.15/drivers/net/ethernet/marvell/Makefile

db9d7d36 - net: mvpp2: Split the PPv2 driver to a dedicated directory

Thu, 31 May 2018 08:07:43 +0000

net: mvpp2: Split the PPv2 driver to a dedicated directoryAs the mvpp2 driver is growing, move this driver to a dedicateddirectory and split it into several files.Since this driver has a lot of register defines and structuredefinitions, it can benefit from having all of this into a dedicatedheader file, named mvpp2.h.A good chunk of the mvpp2 code is dedicated to Header Parser handling, sowe introduce mvpp2_prs.h where all Header Parser definitions are located,and mvpp2_prs.c containing the related code.In the same way, mvpp2_cls.h and mvpp2_cls.c are created to containClassifier and RSS related code.The former 'mvpp2.c' file is renamed 'mvpp2_main.c' so that we can keepthe driver binary named 'mvpp2'.This commit is only about spliting the driver into multiple files anddoesn't introduce any new function, feature or fix besides removing'static' keywords when needed.Signed-off-by: Maxime Chevallier Tested-by: Antoine Tenart Signed-off-by: David S. Miller List of files: /linux-6.15/drivers/net/ethernet/marvell/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/ethernet/marvell/Makefile

dc35a10f - net: mvneta: bm: add support for hardware buffer management

Mon, 14 Mar 2016 08:39:03 +0000

net: mvneta: bm: add support for hardware buffer managementBuffer manager (BM) is a dedicated hardware unit that can be used by allethernet ports of Armada XP and 38x SoC's. It allows to offload CPU on RXpath by sparing DRAM access on refilling buffer pool, hardware-basedfilling of descriptor ring data and better memory utilization due to HWarbitration for using 'short' pools for small packets.Tests performed with A388 SoC working as a network bridge between twopacket generators showed increase of maximum processed 64B packets by~20k (~555k packets with BM enabled vs ~535 packets without BM). Alsowhen pushing 1500B-packets with a line rate achieved, CPU load decreasedfrom around 25% without BM to 20% with BM.BM comprise up to 4 buffer pointers' (BP) rings kept in DRAM, whichare called external BP pools - BPPE. Allocating and releasing bufferpointers (BP) to/from BPPE is performed indirectly by write/read accessto a dedicated internal SRAM, where internal BP pools (BPPI) are placed.BM hardware controls status of BPPE automatically, as well as assigningproper buffers to RX descriptors. For more details please refer toFunctional Specification of Armada XP or 38x SoC.In order to enable support for a separate hardware block, common for allports, a new driver has to be implemented ('mvneta_bm'). It providesinitialization sequence of address space, clocks, registers, SRAM,empty pools' structures and also obtaining optional configurationfrom DT (please refer to device tree binding documentation). mvneta_bmexposes also a necessary API to mvneta driver, as well as a dedicatedstructure with BM information (bm_priv), whose presence is used as aflag notifying of BM usage by port. It has to be ensured that mvneta_bmprobe is executed prior to the ones in ports' driver. In case BM is notused or its probe fails, mvneta falls back to use software buffermanagement.A sequence executed in mvneta_probe function is modified in order to havean access to needed resources before possible port's BM initialization isdone. According to port-pools mapping provided by DT appropriate registersare configured and the buffer pools are filled. RX path is modifiedaccordingly. Becaues the hardware allows a wide variety of configurationoptions, following assumptions are made:* using BM mechanisms can be selectively disabled/enabled basing on DT configuration among the ports* 'long' pool's single buffer size is tied to port's MTU* using 'long' pool by port is obligatory and it cannot be shared* using 'short' pool for smaller packets is optional* one 'short' pool can be shared among all portsThis commit enables hardware buffer management operation cooperating withexisting mvneta driver. New device tree binding documentation is added andthe one of mvneta is updated accordingly.[gregory.clement@free-electrons.com: removed the suspend/resume part]Signed-off-by: Marcin Wojtas Signed-off-by: Gregory CLEMENT Signed-off-by: David S. Miller List of files: /linux-6.15/drivers/net/ethernet/marvell/Makefile

3f518509 - ethernet: Add new driver for Marvell Armada 375 network unit

Thu, 10 Jul 2014 19:52:13 +0000

ethernet: Add new driver for Marvell Armada 375 network unitThis commit adds a new network driver for the network controller in MarvellArmada 375 SoC.Given the controller is very different from the ones in the other MarvellSoCs that use the mv643xx_eth (Kirkwood, Orion, Discovery) and mvneta(Armada 370/38x/XP) drivers, a new driver is needed.Signed-off-by: Marcin Wojtas [Ezequiel: coding style cleanup]Signed-off-by: Ezequiel Garcia Signed-off-by: David S. Miller List of files: /linux-6.15/drivers/net/ethernet/marvell/Makefile

c3a07134 - mv643xx_eth: convert to use the Marvell Orion MDIO driver

Fri, 22 Mar 2013 03:39:28 +0000

mv643xx_eth: convert to use the Marvell Orion MDIO driverThis patch converts the Marvell MV643XX ethernet driver to use theMarvell Orion MDIO driver. As a result, PowerPC and ARM platformsregistering the Marvell MV643XX ethernet driver are also updated toregister a Marvell Orion MDIO driver. This driver voluntarily overlapswith the Marvell Ethernet shared registers because it will use a subsetof this shared register (shared_base + 0x4 to shared_base + 0x84). TheEthernet driver is also updated to look up for a PHY device using theOrion MDIO bus driver.For ARM and PowerPC we register a single instance of the "mvmdio" driverin the system like it used to be done with the use of the "shared_smi"platform_data cookie on ARM.Note that it is safe to register the mvmdio driver only for the "ge00"instance of the driver because this "ge00" interface is guaranteed toalways be explicitely registered by consumers ofarch/arm/plat-orion/common.c and other instances (ge01, ge10 and ge11)were all pointing their shared_smi to ge00. For PowerPC the in-treeDevice Tree Source files mention only one MV643XX ethernet MAC instanceso the MDIO bus driver is registered only when id == 0.Signed-off-by: Florian Fainelli Signed-off-by: David S. Miller List of files: /linux-6.15/drivers/net/ethernet/marvell/Makefile

c5aff182 - net: mvneta: driver for Marvell Armada 370/XP network unit

Fri, 17 Aug 2012 11:04:28 +0000

net: mvneta: driver for Marvell Armada 370/XP network unitThis patch contains a new network driver for the network unit of theARM Marvell Armada 370 and the Armada XP. Both SoCs use the PJ4Bprocessor, a Marvell-developed ARM core that implements the ARMv7instruction set.Compared to previous ARM Marvell SoCs (Kirkwood, Orion, Discovery),the network unit in Armada 370 and Armada XP is highly different. Thisis the reason why this new 'mvneta' driver is needed, while the olderARM Marvell SoCs use the 'mv643xx_eth' driver.Here is an overview of the most important hardware changes thatrequire a new, specific, driver for the network unit of Armada 370/XP: - The new network unit has a completely different design and layout for the RX and TX descriptors. They are now organized as a simple array (each RX and TX queue has base address and size of this array) rather than a linked list as in the old SoCs. - The new network unit has a different RXQ and TXQ management: this management is done using special read/write counter registers, while in the Old SocS, it was done using the Ownership bit in RX and TX descriptors. - The new network unit has different interrupt registers - The new network unit way of cleaning of interrupts is not done by writing to the cause register, but by updating per-queue counters - The new network unit has different GMAC registers (link, speed, duplex configuration) and different WRR registers. - The new network unit has lots of new units like PnC (Parser and Classifier), PMT, BM (Memory Buffer Management), xPON, and more.The driver proposed in the current patch only handles the basicfeatures. Additional hardware features will progressively be supportedas needed.This code has originally been written by Rami Rosen, and then reviewed and cleaned up by ThomasPetazzoni .Signed-off-by: Thomas Petazzoni Acked-by: David S. Miller List of files: /linux-6.15/drivers/net/ethernet/marvell/Makefile

fc8f5ade - net: mvmdio: new Marvell MDIO driver

Mon, 12 Nov 2012 16:03:47 +0000

net: mvmdio: new Marvell MDIO driverThis patch adds a separate driver for the MDIO interface of theMarvell Ethernet controllers. There are two reasons to have a separatedriver rather than including it inside the MAC driver itself: *) The MDIO interface is shared by all Ethernet ports, so a driver must guarantee non-concurrent accesses to this MDIO interface. The most logical way is to have a separate driver that handles this single MDIO interface, used by all Ethernet ports. *) The MDIO interface is the same between the existing mv643xx_eth driver and the new mvneta driver. Even though it is for now only used by the mvneta driver, it will in the future be used by the mv643xx_eth driver as well.Signed-off-by: Thomas Petazzoni Acked-by: David S. Miller List of files: /linux-6.15/drivers/net/ethernet/marvell/Makefile

527a6266 - skge/sky2/mv643xx/pxa168: Move the Marvell Ethernet drivers

Sat, 21 May 2011 03:18:55 +0000

skge/sky2/mv643xx/pxa168: Move the Marvell Ethernet driversMove the Marvell Ethernet drivers into drivers/net/ethernet/marvell/and make the necessary Kconfig and Makefile changes.CC: Sachin Sanap CC: Zhangfei Gao CC: Philip Rakity CC: Mark Brown CC: Lennert Buytenhek CC: Stephen Hemminger Signed-off-by: Jeff Kirsher List of files: /linux-6.15/drivers/net/ethernet/marvell/Makefile