Changes in Makefile

f8970fdc - pinctrl: mvebu: pinctrl driver for 98DX2530 SoC

Thu, 14 Apr 2022 23:30:53 +0000

pinctrl: mvebu: pinctrl driver for 98DX2530 SoCThis pinctrl driver supports the 98DX25xx and 98DX35xx family of chipsfrom Marvell. It is based on the Marvell SDK with additions for various(non-gpio) pin configurations based on the datasheet.Signed-off-by: Chris Packham Reviewed-by: Andrew Lunn Link: https://lore.kernel.org/r/20220414233055.586962-3-chris.packham@alliedtelesis.co.nzSigned-off-by: Linus Walleij List of files: /linux-6.15/drivers/pinctrl/mvebu/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/pinctrl/mvebu/Makefile

def8e228 - pinctrl: mvebu: add driver for Armada CP110 pinctrl

Mon, 12 Jun 2017 15:34:57 +0000

pinctrl: mvebu: add driver for Armada CP110 pinctrlThis commit adds a pinctrl driver for the CP110 part of the MarvellArmada 7K and 8K SoCs. The Armada 7K has a single CP110, where almost allthe MPP pins are available. On the other side, the Armada 8K has twoCP110, and the available MPPs are split between the master CP110 (MPPs 32to 62) and the slave CP110 (MPPs 0 to 31).The register interface to control the MPPs is however the same as allother mvebu SoCs, so we can reuse the common pinctrl-mvebu.c logic.Signed-off-by: Hanna Hawa Reviewed-by: Shadi Ammouri [updated for mvebu pinctrl and 4.9 changes: - converted to simple_mmio - converted to syscon/regmap - removed unimplemented .remove function - dropped DTS changes - defered gpio ranges to DT - fixed warning - properly set soc->nmodes -- rmk]Signed-off-by: Russell King [ add missing MPP[61:56] function 14 (SDIO)-- Konstantin Porotchkin]Signed-off-by: Konstantin Porotchkin [ allow to properly register more then one instance of this driver-- Grzegorz Jaszczyk]Signed-off-by: Grzegorz Jaszczyk [ - rebased on 4.12-rc1 - fixed the 80 character limit for mvebu_mpp_mode array - aligned the compatible name on the ones already used - fixed the MPP table for CP110: some MPP are not available on Armada 7K-- Gregory CLEMENT]Signed-off-by: Gregory CLEMENT Tested-by: Thomas Petazzoni Signed-off-by: Linus Walleij List of files: /linux-6.15/drivers/pinctrl/mvebu/Makefile

86fbd094 - pinctrl: mvebu: add driver for Armada AP806 pinctrl

Mon, 12 Jun 2017 15:34:56 +0000

pinctrl: mvebu: add driver for Armada AP806 pinctrlThis commit adds a pinctrl driver for the pin-muxing controller found inthe AP806 part of the Marvell Armada 7K and 8K SoCs. Its registerinterface is compatible with the one used by previous mvebu pincontrollers, so the common logic in drivers/pinctrl/mvebu/pinctrl-mvebu.cis used.Signed-off-by: Hanna Hawa Reviewed-by: Shadi Ammouri [updated for mvebu pinctrl changes - converted to simple_mmio - removed unimplemented .remove function - removed DTS description - converted to use syscon/regmap --rmk]Signed-off-by: Russell King Reviewed-by: Thomas Petazzoni Signed-off-by: Gregory CLEMENT Signed-off-by: Linus Walleij List of files: /linux-6.15/drivers/pinctrl/mvebu/Makefile

87466ccd - pinctrl: armada-37xx: Add pin controller support for Armada 37xx

Wed, 05 Apr 2017 15:18:04 +0000

pinctrl: armada-37xx: Add pin controller support for Armada 37xxThe Armada 37xx SoC come with 2 pin controllers: one on the southbridge (managing 28 pins) and one on the north bridge (managing 36 pins).At the hardware level the controller configure the pins by group and notpin by pin. This constraint is reflected in the design of the driver:only the group related functions are implemented.Signed-off-by: Gregory CLEMENT Signed-off-by: Linus Walleij List of files: /linux-6.15/drivers/pinctrl/mvebu/Makefile

973bbcfa - pinctrl: mvebu: guard sub-directory with CONFIG_PINCTRL_MVEBU

Tue, 24 Nov 2015 11:45:23 +0000

pinctrl: mvebu: guard sub-directory with CONFIG_PINCTRL_MVEBUCONFIG_PINCTRL_MVEBU is more suitable than CONFIG_PLAT_ORIONto guard the drivers/pinctrl/mvebu/ directory.Signed-off-by: Masahiro Yamada Signed-off-by: Linus Walleij List of files: /linux-6.15/drivers/pinctrl/mvebu/Makefile

ee086577 - pinctrl: mvebu: add pinctrl driver for Marvell Armada 39x

Fri, 06 Feb 2015 15:57:53 +0000

pinctrl: mvebu: add pinctrl driver for Marvell Armada 39xThis commit adds a new pinctrl driver for the Marvell Armada 39xfamily of processors, which hooks into the existing infrastructure tosupport pin-muxing on Marvell EBU processors. Two variants of theArmada 39x are supported: 88F6920 (Armada 390) and 88F6928 (Armada398), which have a few differences in the available functions forcertain pins.Signed-off-by: Thomas Petazzoni Signed-off-by: Linus Walleij List of files: /linux-6.15/drivers/pinctrl/mvebu/Makefile

fd67f884 - pinctrl: mvebu: new driver for Orion platforms

Tue, 22 Apr 2014 21:26:07 +0000

pinctrl: mvebu: new driver for Orion platformsThis commit extends the pinctrl mvebu logic with a new driver to coverOrion5x SoC. It supports the definitions for the 5181l, 5182 and 5281variants of Orion5x, which are the three ones supported by the oldstyle MPP code in arch/arm/mach-orion5x/.Signed-off-by: Thomas Petazzoni Acked-by: Sebastian Hesselbarth Signed-off-by: Linus Walleij List of files: /linux-6.15/drivers/pinctrl/mvebu/Makefile

ca6d9a08 - pinctrl: mvebu: add pin-muxing driver for the Marvell Armada 380/385

Mon, 10 Feb 2014 17:04:56 +0000

pinctrl: mvebu: add pin-muxing driver for the Marvell Armada 380/385The Marvell Armada 380/385 are new ARM SoCs from Marvell, part of themvebu family, but using a Cortex-A9 CPU core. In terms of pin-muxing,it is similar to Armada 370 and XP for the register layout, onlydifferent in the number of available pins and theirfunctions. Therefore, we simply use the existingdrivers/pinctrl/mvebu/ infrastructure, with no other changes that thelist of pins and corresponding functions.Signed-off-by: Thomas Petazzoni Signed-off-by: Sebastian Hesselbarth List of files: /linux-6.15/drivers/pinctrl/mvebu/Makefile

ce3ed59d - pinctrl: mvebu: add pin-muxing driver for the Marvell Armada 375

Mon, 10 Feb 2014 17:04:55 +0000

pinctrl: mvebu: add pin-muxing driver for the Marvell Armada 375The Marvell Armada 375 is a new ARM SoC from Marvell, part of themvebu family, but using a Cortex-A9 CPU core. In terms of pin-muxing,it is similar to Armada 370 and XP for the register layout, onlydifferent in the number of available pins and theirfunctions. Therefore, we simply use the existingdrivers/pinctrl/mvebu/ infrastructure, with no other changes that thelist of pins and corresponding functions.Signed-off-by: Thomas Petazzoni Signed-off-by: Sebastian Hesselbarth Reviewed-by: Gregory CLEMENT List of files: /linux-6.15/drivers/pinctrl/mvebu/Makefile

06763c74 - pinctrl: mvebu: move to its own directory

Wed, 24 Oct 2012 21:38:58 +0000

pinctrl: mvebu: move to its own directoryLike the spear platform, the mvebu platform has multiple files: onecore file, and then one file per SoC family. More files will be addedlater, as support for mach-orion5x and mach-mv78xx0 SoCs is added topinctrl-mvebu. For those reasons, having a separate subdirectory,drivers/pinctrl/mvebu/ makes sense, and it had already been suggestedby Linus Wallej when the driver was originally submitted.Signed-off-by: Thomas Petazzoni Signed-off-by: Linus Walleij List of files: /linux-6.15/drivers/pinctrl/mvebu/Makefile