Changes in Makefile

b8b248de - arm64: tegra: Create SKU8 AGX Orin board file

Tue, 10 Sep 2024 19:04:57 +0000

arm64: tegra: Create SKU8 AGX Orin board fileThe existing tegra234-p3737-0000+p3701-0000.dtb is compatiblewith the following modules:p3701-0000p3701-0004p3701-0005Add support for p3701-0008. Move data that is common to all SKUsto a new file called tegra234-p3737-0000+p3701.dtsi. Update Makefile.Signed-off-by: Dara Stotland Reviewed-by: Brad Griffis Signed-off-by: Thierry Reding List of files: /linux-6.15/scripts/dtc/include-prefixes/arm64/nvidia/Makefile

4d921162 - arm64: tegra: Support Jetson Orin Nano Developer Kit

Tue, 16 May 2023 09:58:50 +0000

arm64: tegra: Support Jetson Orin Nano Developer KitThe NVIDIA Jetson Orin Nano Developer Kit is the combination of theNVIDIA Jetson Orin Nano (P3767, SKU 5) module and the P3768 carrierboard.Signed-off-by: Thierry Reding List of files: /linux-6.15/scripts/dtc/include-prefixes/arm64/nvidia/Makefile

c95711d7 - arm64: tegra: Add support for IGX Orin

Mon, 08 May 2023 10:27:33 +0000

arm64: tegra: Add support for IGX OrinAdd support for the NVIDIA IGX Orin development kit having P3701module with P3740 carrier board.Signed-off-by: Shubhi Garg Signed-off-by: Thierry Reding List of files: /linux-6.15/scripts/dtc/include-prefixes/arm64/nvidia/Makefile

e63472ed - arm64: tegra: Support Jetson Orin NX reference platform

Fri, 31 Mar 2023 16:29:14 +0000

arm64: tegra: Support Jetson Orin NX reference platformAdd support for the combination of the NVIDIA Jetson Orin NX (P3767, SKU0) module and the P3768 carrier board.Signed-off-by: Thierry Reding List of files: /linux-6.15/scripts/dtc/include-prefixes/arm64/nvidia/Makefile

b7e70391 - arm64: tegra: Enable device-tree overlay support

Thu, 03 Feb 2022 18:43:27 +0000

arm64: tegra: Enable device-tree overlay supportAdd the '-@' DTC option for the Jetson TX1, Jetson Nano, Jetson TX2,Jetson TX2 NX, Jetson AGX Xavier, Jetson Xavier NX and Jetson AGX Orinplatforms. This option populates the '__symbols__' node that containsall the necessary symbols for supporting device-tree overlays on theseplatforms. These Jetson platforms have various expansion headers,including a 40-pin GPIO header, that allow various add-on modules to beconnected and this permits users to create device-tree overlays forthese modules.Please note that this change does increase the size of the resulting DTBfrom between 30-50%. For example, with v5.17-rc1 increase in size is asfollows: tegra210-p2371-2180.dtb: 79580 -> 105744 bytes tegra210-p3450-0000.dtb: 57465 -> 81357 bytes tegra186-p2771-0000.dtb: 64763 -> 99553 bytes tegra186-p3509-0000+p3636-0001.dtb: 48078 -> 62464 bytes tegra194-p2972-0000.dtb: 75303 -> 111545 bytes tegra194-p3509-0000+p3668-0000.dtb: 74762 -> 111995 bytes tegra194-p3509-0000+p3668-0001.dtb: 74578 -> 111748 bytes tegra234-p3737-0000+p3701-0000.dtb: 11229 -> 12917 bytesSigned-off-by: Jon Hunter Signed-off-by: Thierry Reding List of files: /linux-6.15/scripts/dtc/include-prefixes/arm64/nvidia/Makefile

533337d5 - arm64: tegra: Add NVIDIA Jetson AGX Orin Developer Kit support

Fri, 12 Nov 2021 12:35:42 +0000

arm64: tegra: Add NVIDIA Jetson AGX Orin Developer Kit supportThe Jetson AGX Orin Developer Kit is a continuation of the JetsonDeveloper Kit line using the new NVIDIA Tegra234 (Orin) SoC.Signed-off-by: Mikko Perttunen Signed-off-by: Thierry Reding List of files: /linux-6.15/scripts/dtc/include-prefixes/arm64/nvidia/Makefile

8a9dee7e - arm64: tegra: Add NVIDIA Jetson TX2 NX Developer Kit support

Thu, 12 Aug 2021 12:26:17 +0000

arm64: tegra: Add NVIDIA Jetson TX2 NX Developer Kit supportThe Jetson TX2 NX Developer Kit is very similar to the Jetson Nano, butuses the more powerful Tegra186 SoC.Signed-off-by: Thierry Reding List of files: /linux-6.15/scripts/dtc/include-prefixes/arm64/nvidia/Makefile

f1601302 - arm64: tegra: Add support for Jetson Xavier NX with eMMC

Thu, 28 Jan 2021 12:08:51 +0000

arm64: tegra: Add support for Jetson Xavier NX with eMMCAdd support for the variant of the Jetson Xavier NX Developer Kit thathas a system-on-module which includes an eMMC.Signed-off-by: Jon Hunter Signed-off-by: Thierry Reding List of files: /linux-6.15/scripts/dtc/include-prefixes/arm64/nvidia/Makefile

63944891 - arm64: tegra: Initial Tegra234 VDK support

Thu, 17 Sep 2020 10:07:52 +0000

arm64: tegra: Initial Tegra234 VDK supportThe NVIDIA Tegra234 VDK is a simulation platform for the Orin SoC. Itsupports a subset of the peripherals that will be available in the finalchip and serves as a bootstrapping platform.Reviewed-by: Jon Hunter Signed-off-by: Thierry Reding List of files: /linux-6.15/scripts/dtc/include-prefixes/arm64/nvidia/Makefile

3f9efbbe - arm64: tegra: Add support for Jetson Xavier NX

Mon, 13 Jul 2020 16:17:01 +0000

arm64: tegra: Add support for Jetson Xavier NXAdd the device-tree source files for the Tegra194 Jetson Xavier NXDeveloper Kit. The Xavier NX Developer Kit consists of a small formfactor system-on-module (SOM) board (part number p3668-0000) and acarrier board (part number p3509-0000).The Xavier NX Developer Kit SOM features a micro-SD card slot, however,there is also a variant of the SOM available that features a 16GB eMMC.Given that the carrier board can be used with the different SOMvariants, that have different part numbers, both the compatible stringand file name of the device-tree source file for the Developer Kit is aconcatenation of the SOM and carrier board part numbers.Based on some initial work by Thierry Reding .Signed-off-by: Jon Hunter Signed-off-by: Thierry Reding List of files: /linux-6.15/scripts/dtc/include-prefixes/arm64/nvidia/Makefile

6772cd0e - arm64: tegra: Add NVIDIA Jetson Nano Developer Kit support

Fri, 18 Jan 2019 12:27:44 +0000

arm64: tegra: Add NVIDIA Jetson Nano Developer Kit supportThe Jetson Nano Developer Kit is a Tegra X1 based development board. Itis similar to Jetson TX1 but it is not pin compatible. It features 4 GBof LPDDR4, an SPI NOR flash for early boot firmware and an SD card slotused for storage.HDMI 2.0 or DP 1.2 are available for display, four USB ports (3 USB 2.0and 1 USB 3.0) can be used to attach a variety of peripherals and a PCIEthernet controller provides onboard network connectivity. An M.2 Key-Eslot with PCIe x1 adds additional possibilities.A 40-pin header on the board can be used to extend the capabilities andexposed interfaces of the Jetson Nano.Acked-by: Jon Hunter Signed-off-by: Thierry Reding List of files: /linux-6.15/scripts/dtc/include-prefixes/arm64/nvidia/Makefile

dd03aeef - arm64: tegra: Add support for NVIDIA Shield TV

Fri, 11 Jan 2019 02:38:45 +0000

arm64: tegra: Add support for NVIDIA Shield TVAdd initial device-tree support for NVIDIA Shield TV (a.k.a. Darcy)based upon Tegra210 SoC with 3 GiB of LPDDR4 RAM.Signed-off-by: Mark Zhang Signed-off-by: Thierry Reding List of files: /linux-6.15/scripts/dtc/include-prefixes/arm64/nvidia/Makefile

b8656c67 - arm64: tegra: Add device tree for the Tegra194 P2972-0000 board

Tue, 20 Feb 2018 11:58:12 +0000

arm64: tegra: Add device tree for the Tegra194 P2972-0000 boardAdd device tree files for the Tegra194 P2972-0000 development board.The board consists of the P2888 compute module and the P2822 baseboard.Signed-off-by: Mikko Perttunen Signed-off-by: Thierry Reding List of files: /linux-6.15/scripts/dtc/include-prefixes/arm64/nvidia/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/nvidia/Makefile

74ce1896 - kbuild: clean up .dtb and .dtb.S patterns from top-level Makefile

Thu, 02 Nov 2017 02:51:25 +0000

kbuild: clean up *.dtb and *.dtb.S patterns from top-level MakefileWe need to add "clean-files" in Makfiles to clean up DT blobs, but weoften miss to do so.Since there are no source files that end with .dtb or .dtb.S, so wecan clean-up those files from the top-level Makefile.Signed-off-by: Masahiro Yamada Acked-by: Arnd Bergmann Signed-off-by: Rob Herring List of files: /linux-6.15/scripts/dtc/include-prefixes/arm64/nvidia/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/nvidia/Makefile

99575bce - arm64: tegra: Add NVIDIA P2771 board support

Tue, 05 Jul 2016 09:04:31 +0000

arm64: tegra: Add NVIDIA P2771 board supportThe NVIDIA P2771 is composed of a P3310 processor module that connectsto the P2597 I/O board. It comes with a 1200x1920 MIPI DSI panel that isconnected via the P2597's display connector and has several connectorssuch as HDMI, USB 3.0, PCIe and ethernet.Signed-off-by: Joseph Lo Signed-off-by: Thierry Reding List of files: /linux-6.15/scripts/dtc/include-prefixes/arm64/nvidia/Makefile

5d17ba6e - arm64: tegra: Add support for Google Pixel C

Tue, 09 Feb 2016 12:26:49 +0000

arm64: tegra: Add support for Google Pixel CAdd initial device-tree support for Google Pixel C (a.k.a. Smaug) basedupon Tegra210 SoC with 3 GiB of LPDDR4 RAM.Signed-off-by: Jon Hunter Tested-by: Alexandre Courbot Reviewed-by: Andrew Bresticker Tested-by: Andrew Bresticker Signed-off-by: Thierry Reding List of files: /linux-6.15/scripts/dtc/include-prefixes/arm64/nvidia/Makefile

336f79c7 - arm64: tegra: Add NVIDIA Jetson TX1 Developer Kit support

Wed, 09 Sep 2015 14:28:59 +0000

arm64: tegra: Add NVIDIA Jetson TX1 Developer Kit supportThe Jetson TX1 Development Kit is the successor of the Jetson TK1. TheJetson TX1 is composed of the Jetson TX1 module (P2180) that connects tothe P2597 I/O board. It comes with a 1200x1920 MIPI DSI panel connectedvia the P2597's display connector.Signed-off-by: Thierry Reding List of files: /linux-6.15/scripts/dtc/include-prefixes/arm64/nvidia/Makefile

2cc85bd9 - arm64: tegra: Add NVIDIA P2571 board support

Mon, 23 Mar 2015 09:32:57 +0000

arm64: tegra: Add NVIDIA P2571 board supportThe NVIDIA P2571 is an internal reference design that's very similar tothe P2371, but targetting different use-cases.Signed-off-by: Thierry Reding List of files: /linux-6.15/scripts/dtc/include-prefixes/arm64/nvidia/Makefile