Changes in Makefile

2e976f19 - arm64: dts: Add initial support for Blaize BLZP1600 CB2

Wed, 04 Dec 2024 16:05:27 +0000

arm64: dts: Add initial support for Blaize BLZP1600 CB2Add support for the Blaize CB2 development board based onthe BLZP1600 SoC. This consists of a Carrier-Board-2 and aSystem-on-Module.Both BLZP1600 SoM and CB2 are available as products.CB2 (Pathfinder) has multiple peripherals like UART, I2C,SPI, GPIO, CSI (camera), DSI (display), USB-3.0 and Ethernet.Enable support for the Cryptocell, UART and I2C which arealready fully supported by the drivers.The blaize-blzp1600.dtsi is the common part for the SoC,blaize-blzp1600-som.dtsi is the common part for the SoM andblaize-blzp1600-cb2.dts is the board specific file.Co-developed-by: James Cowgill Signed-off-by: James Cowgill Co-developed-by: Matt Redfearn Signed-off-by: Matt Redfearn Co-developed-by: Neil Jones Signed-off-by: Neil Jones Signed-off-by: Nikolaos Pasaloukos Reviewed-by: Krzysztof Kozlowski Signed-off-by: Arnd Bergmann List of files: /linux-6.15/scripts/dtc/include-prefixes/arm64/Makefile

ab52c591 - arm64: dts: Add Airoha EN7581 SoC and EN7581 Evaluation Board

Sat, 09 Mar 2024 09:32:15 +0000

arm64: dts: Add Airoha EN7581 SoC and EN7581 Evaluation BoardIntroduce the Airoha EN7581 SoC's dtsi and the Airoha EN7581 EvaluationBoard's dts file, as well as the required Makefiles.Reviewed-by: AngeloGioacchino Del Regno Signed-off-by: Daniel Danzberger Co-developed-by: Lorenzo Bianconi Signed-off-by: Lorenzo Bianconi Link: https://lore.kernel.org/r/f05a36dd7e8ef34ead8a63aa10fcffb542229404.1709975956.git.lorenzo@kernel.orgSigned-off-by: AngeloGioacchino Del Regno List of files: /linux-6.15/scripts/dtc/include-prefixes/arm64/Makefile

1c890754 - arm64: dts: st: add stm32mp257f-ev1 board support

Thu, 18 Nov 2021 11:26:49 +0000

arm64: dts: st: add stm32mp257f-ev1 board supportAdd STM32MP257F Evaluation board support. It embeds a STM32MP257FAI SoC,with 4GB of DDR4, TSN switch (2+1 ports), 2*USB typeA, 1*USB2 typeC,SNOR OctoSPI, mini PCIe, STPMIC2 for power distribution ...Signed-off-by: Alexandre Torgue List of files: /linux-6.15/scripts/dtc/include-prefixes/arm64/Makefile

6cc82f07 - arm64: dts: nuvoton: Add initial NPCM8XX device tree

Sun, 17 Jul 2022 09:16:07 +0000

arm64: dts: nuvoton: Add initial NPCM8XX device treeThis adds initial device tree support for the Nuvoton NPCM845 BoardManagement controller (BMC) SoC family.The NPCM845 based quad-core Cortex-A35 ARMv8 architecture and havevarious peripheral IPs.Signed-off-by: Tomer Maimon Reviewed-by: Krzysztof Kozlowski Signed-off-by: Arnd Bergmann List of files: /linux-6.15/scripts/dtc/include-prefixes/arm64/Makefile

18b1db6a - arm64: dts: fsd: Add initial device tree support

Mon, 24 Jan 2022 14:16:42 +0000

arm64: dts: fsd: Add initial device tree supportAdd initial device tree support for "Full Self-Driving" (FSD) SoCThis SoC contain three clusters of four cortex-a72 CPUs and variousperipheral IPs.Cc: linux-fsd@tesla.comReviewed-by: Krzysztof Kozlowski Signed-off-by: Arjun K V Signed-off-by: Aswani Reddy Signed-off-by: Ajay Kumar Signed-off-by: Sriranjani P Signed-off-by: Chandrasekar R Signed-off-by: Shashank Prashar Signed-off-by: Alim Akhtar Link: https://lore.kernel.org/r/20220124141644.71052-15-alim.akhtar@samsung.comSigned-off-by: Krzysztof Kozlowski List of files: /linux-6.15/scripts/dtc/include-prefixes/arm64/Makefile

7d2d16cc - arm64: apple: Add initial Apple Mac mini (M1, 2020) devicetree

Thu, 04 Feb 2021 13:30:21 +0000

arm64: apple: Add initial Apple Mac mini (M1, 2020) devicetreeThis currently supports:* SMP (via spin-tables)* AIC IRQs* Serial (with earlycon)* FramebufferA number of properties are dynamic, and based on system firmwaredecisions that vary from version to version. These are expectedto be filled in by the loader.Reviewed-by: Rob Herring Signed-off-by: Hector Martin List of files: /linux-6.15/scripts/dtc/include-prefixes/arm64/Makefile

89d4f98a - ARM: remove zte zx platform

Mon, 18 Jan 2021 13:06:09 +0000

ARM: remove zte zx platformThe ZTE ZX set-top-box SoC platform was added in 2015 by Jun Nie, withBaoyou Xie and Shawn Guo subsequently becoming maintainers after theaddition of the 64-bit variant.However, the only machines that were ever supported upstream are thereference designs, not actual set-top-box devices that would benefitfrom this support. All ZTE set-top-boxes from the past few years seemto be based on third-party SoCs. While there is very little informationabout zx296702 and zx296718 on the web, I found some references to otherchips from the same family, such as zx296716 and zx296719, which werenever submitted for upstream support. Finally, there is no support forthe GPU on either of them, with the lima and panfrost device drivershaving been added after work on the zx platform had stopped.Shawn confirmed that he has not seen any interest in this platform forthe past four years, and that it can be removed.Thanks to Jun and Shawn for maintaining this platform over the pastfive years.Cc: Jun Nie Cc: Shawn Guo Signed-off-by: Arnd Bergmann List of files: /linux-6.15/scripts/dtc/include-prefixes/arm64/Makefile

48dea9a7 - arm64: dts: visconti: Add device tree for TMPV7708 RM main board

Mon, 27 Apr 2020 20:59:12 +0000

arm64: dts: visconti: Add device tree for TMPV7708 RM main boardAdd basic support for the Visconti TMPV7708 SoC peripherals - - CPU - CA53 x 4 and 2 cluster. - not support PSCI, currently only spin-table is supported. - Interrupt controller (ARM Generic Interrupt Controller) - Timer (ARM architected timer) - UART (ARM PL011 UART controller) - SPI (ARM PL022 SPI controller) - I2C (Synopsys DesignWare APB I2C Controller) - Pin control (Visconti specific)Signed-off-by: Nobuhiro Iwamatsu Reviewed-by: Punit Agrawal List of files: /linux-6.15/scripts/dtc/include-prefixes/arm64/Makefile

39889b82 - arm64: dts: amazon: rename al folder to be amazon

Fri, 24 Jul 2020 13:26:50 +0000

arm64: dts: amazon: rename al folder to be amazonAs preparation to add device tree binding for Amazon's Annapurna LabsAlpine v3 support. Rename al device tree folder to be amazon.Link: https://lore.kernel.org/r/20200724132654.16549-3-hhhawa@amazon.comSigned-off-by: Hanna Hawa Acked-by: Antoine Tenart Signed-off-by: Arnd Bergmann List of files: /linux-6.15/scripts/dtc/include-prefixes/arm64/Makefile

6694aee0 - arm64: dts: sparx5: Add basic cpu support

Mon, 15 Jun 2020 13:32:35 +0000

arm64: dts: sparx5: Add basic cpu supportThis adds the basic DT structure for the Microchip Sparx5 SoC, and thereference boards, pcb125, pcb134 and pcb135. The two latter have aNAND vs a eMMC centric variant (as a mount option).Link: https://lore.kernel.org/r/20200615133242.24911-4-lars.povlsen@microchip.comReviewed-by: Alexandre Belloni Signed-off-by: Lars Povlsen Signed-off-by: Arnd Bergmann List of files: /linux-6.15/scripts/dtc/include-prefixes/arm64/Makefile

4b36daf9 - arm64: dts: agilex: Add initial support for Intel's Agilex SoCFPGA

Wed, 03 Apr 2019 21:43:51 +0000

arm64: dts: agilex: Add initial support for Intel's Agilex SoCFPGAAdd the initial device tree files for Intel's Agilex SoCFPGA platform.Signed-off-by: Dinh Nguyen List of files: /linux-6.15/scripts/dtc/include-prefixes/arm64/Makefile

c8ec3743 - arm64: dts: bitmain: Add BM1880 SoC support

Fri, 25 Jan 2019 16:37:02 +0000

arm64: dts: bitmain: Add BM1880 SoC supportAdd devicetree support for Bitmain BM1880 SoC, consisting of a Dualcore ARM Cortex A53 subsystem, a Single core RISC-V subsystem and a TensorProcessor subsystem. Only ARM Cortex A53 Application processor subsystemsupport is enabled for now.Signed-off-by: Manivannan Sadhasivam Acked-by: Arnd Bergmann List of files: /linux-6.15/scripts/dtc/include-prefixes/arm64/Makefile

d0a064be - arm64: dts: ti: Add support for AM654 EVM base board

Tue, 26 Jun 2018 16:26:15 +0000

arm64: dts: ti: Add support for AM654 EVM base boardThe EValuation Module(EVM) platform for AM654 consists of acommon Base board + one or more of daughter cards, which include:a) "Personality Modules", which can be specific to a profile, such as ICSSG enabled or Multi-media (including audio).b) SERDES modules, which may be 2 lane PCIe or two port PCIe + USB2c) Camera daughter cardd) various display panelsAmong other options. There are two basic configurations defined whichinclude an "EVM" configuration and "IDK" (Industrial development kit)which differ in the specific combination of daughter cards that areused.To simplify support, we choose to support just the base board as thecore device tree file and all daughter cards would be expected to bedevice tree overlays.Reviewed-by: Tony Lindgren Signed-off-by: Lokesh Vutla Signed-off-by: Nishanth Menon Signed-off-by: Tony Lindgren List of files: /linux-6.15/scripts/dtc/include-prefixes/arm64/Makefile

031106ce - arm64: dts: move berlin SoC files from marvell dir to synaptics dir

Wed, 16 May 2018 09:43:28 +0000

arm64: dts: move berlin SoC files from marvell dir to synaptics dirMove device tree files as part of transition from Marvell berlin toSynaptics berlin.Signed-off-by: Jisheng Zhang List of files: /linux-6.15/scripts/dtc/include-prefixes/arm64/Makefile

cbbde59b - arm64: dts: sort vendor subdirectories in Makefile alphabetically

Sat, 18 Nov 2017 03:10:03 +0000

arm64: dts: sort vendor subdirectories in Makefile alphabeticallyThe list is almost sorted. Move "lg" up to complete it.Signed-off-by: Masahiro Yamada Signed-off-by: Olof Johansson List of files: /linux-6.15/scripts/dtc/include-prefixes/arm64/Makefile

7e7962dd - kbuild: handle dtb-y and CONFIG_OF_ALL_DTBS natively in Makefile.lib

Sun, 05 Nov 2017 05:30:53 +0000

kbuild: handle dtb-y and CONFIG_OF_ALL_DTBS natively in Makefile.libIf CONFIG_OF_ALL_DTBS is enabled, "make ARCH=arm64 dtbs" compiles eachDTB twice; one from arch/arm64/boot/dts/*/Makefile and the other fromthe dtb-$(CONFIG_OF_ALL_DTBS) line in arch/arm64/boot/dts/Makefile.It could be a race problem when building DTBS in parallel.Another minor issue is CONFIG_OF_ALL_DTBS covers only *.dts in vendorsub-directories, so this broke when Broadcom added one more hierarchyin arch/arm64/boot/dts/broadcom//.One idea to fix the issues in a clean way is to move DTB handlingto Kbuild core scripts. Makefile.dtbinst already recognizes dtb-ynatively, so it should not hurt to do so.Add $(dtb-y) to extra-y, and $(dtb-) as well if CONFIG_OF_ALL_DTBS isenabled. All clutter things in Makefiles go away.As a bonus clean-up, I also removed dts-dirs. Just use subdir-ydirectly to traverse sub-directories.Signed-off-by: Masahiro Yamada Acked-by: Arnd Bergmann [robh: corrected BUILTIN_DTB to CONFIG_BUILTIN_DTB]Signed-off-by: Rob Herring List of files: /linux-6.15/scripts/dtc/include-prefixes/arm64/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/scripts/dtc/include-prefixes/arm64/Makefile

06edb80f - arm64: dts: Add Actions Semi S900 and Bubblegum-96

Tue, 14 Feb 2017 21:24:21 +0000

arm64: dts: Add Actions Semi S900 and Bubblegum-96Add Device Trees for Actions Semiconductor S900 SoC anduCRobotics Bubblegum-96 board.UART0/1/4/6 interrupts are guesses.Cc: 96boards@ucrobotics.comSigned-off-by: Andreas Färber List of files: /linux-6.15/scripts/dtc/include-prefixes/arm64/Makefile

72a7786c - ARM64: dts: Add Realtek RTD1295 and Zidoo X9S

Sat, 21 Jan 2017 01:18:34 +0000

ARM64: dts: Add Realtek RTD1295 and Zidoo X9SAdd initial device trees for the RTD1295 SoC and the Zidoo X9S TV box.The CPUs lack the enable-method property because the vendor device treeuses a custom "rtk-spin-table" method and "psci" did not appear to work.The UARTs lack the interrupts properties because the vendor device treeconnects them to a custom interrupt controller. earlycon works without.A list of memory reservations is adopted from v1.2.11 vendor device tree:0x02200000 can be used for an initrd, 0x01b00000 is audio-related;ion-related 0x02600000, 0x02c00000 and 0x11000000 are left out;0x10000000 is used for sharing the U-Boot environment; others remainto be investigated.Acked-by: Arnd Bergmann Reviewed-by: Rob Herring Signed-off-by: Andreas Färber List of files: /linux-6.15/scripts/dtc/include-prefixes/arm64/Makefile

4e388608 - arm64: dts: add Pine64 support

Tue, 19 Jan 2016 10:36:39 +0000

arm64: dts: add Pine64 supportThe Pine64 is a cost-efficient development board based on theAllwinner A64 SoC.There are three models: the basic version with Fast Ethernet and512 MB of DRAM (Pine64) and two Pine64+ versions, which bothfeature Gigabit Ethernet and additional connectors for touchscreensand a camera. Or as my son put it: "Those are smaller and these aremissing." ;-)The two Pine64+ models just differ in the amount of DRAM(1GB vs. 2GB). Since U-Boot will figure out the right size for us andpatches the DT accordingly we just need to provide one DT for thePine64+.Signed-off-by: Andre Przywara [Maxime: Removed the common DTSI and include directly the pine64 DTS]Signed-off-by: Maxime Ripard List of files: /linux-6.15/scripts/dtc/include-prefixes/arm64/Makefile