Changes in Makefile

63da297f - arm64: dts: exynos: Add initial support for Samsung Galaxy S9 (SM-G960F)

Sat, 14 Dec 2024 14:56:47 +0000

arm64: dts: exynos: Add initial support for Samsung Galaxy S9 (SM-G960F)Samsung Galaxy S9 (SM-G960F), codenamed starlte, is a mobile phonereleased in 2017. It has 4GB of RAM, 64GB of UFS storage, Exynos9810SoC and 1440x2960 Super AMOLED display.This initial device tree enables the framebuffer pre-initialisedby bootloader and physical buttons of the device, with more supportto come in the future.Co-developed-by: Maksym Holovach Signed-off-by: Maksym Holovach Signed-off-by: Markuss Broks Link: https://lore.kernel.org/r/20241214-exynos9810-v4-2-4e91fbbc2133@gmail.comSigned-off-by: Krzysztof Kozlowski List of files: /linux-6.15/scripts/dtc/include-prefixes/arm64/exynos/Makefile

4ccb27d4 - arm64: dts: exynos: Add initial support for Samsung Galaxy S20 (x1slte)

Mon, 09 Dec 2024 08:00:59 +0000

arm64: dts: exynos: Add initial support for Samsung Galaxy S20 (x1slte)Add initial support for the Samsung Galaxy S20 (x1slte/SM-G980F)phone. It was launched in 2020, and it's based on the Exynos 990 SoC. Ithas only one configuration with 8GB of RAM and 128GB of UFS 3.0 storage.This device tree adds support for the following:- SimpleFB- 8GB RAM- ButtonsSigned-off-by: Umer Uddin Link: https://lore.kernel.org/r/20241209080059.11891-5-umer.uddin@mentallysanemainliners.orgSigned-off-by: Krzysztof Kozlowski List of files: /linux-6.15/scripts/dtc/include-prefixes/arm64/exynos/Makefile

e7c07584 - arm64: dts: exynos: Add initial support for Samsung Galaxy S20 5G (x1s)

Mon, 09 Dec 2024 08:00:58 +0000

arm64: dts: exynos: Add initial support for Samsung Galaxy S20 5G (x1s)Add initial support for the Samsung Galaxy S20 5G (x1s/SM-G981B)phone. It was launched in 2020, and it's based on the Exynos 990 SoC. Ithas only one configuration with 12GB of RAM and 128GB of UFS 3.0 storage.This device tree adds support for the following:- SimpleFB- 12GB RAM- ButtonsSigned-off-by: Umer Uddin Link: https://lore.kernel.org/r/20241209080059.11891-4-umer.uddin@mentallysanemainliners.orgSigned-off-by: Krzysztof Kozlowski List of files: /linux-6.15/scripts/dtc/include-prefixes/arm64/exynos/Makefile

706119fb - arm64: dts: exynos: Add initial support for Samsung Galaxy S20 FE (r8s)

Thu, 14 Nov 2024 14:36:36 +0000

arm64: dts: exynos: Add initial support for Samsung Galaxy S20 FE (r8s)Add initial support for the Samsung Galaxy S20 FE (r8s/SM-G780F) device.Its launch was in 2020 and also based on the Exynos 990 SoC.It is only configured with 6GB of RAM, although storage options may differ.This device tree adds support for the following:- SimpleFB- 6GB RAM- ButtonsSigned-off-by: Denzeel Oliva Link: https://lore.kernel.org/r/20241114143636.374-3-wachiturroxd150@gmail.comSigned-off-by: Krzysztof Kozlowski List of files: /linux-6.15/scripts/dtc/include-prefixes/arm64/exynos/Makefile

8354f854 - arm64: dts: exynos: Add initial support for Samsung Galaxy Note20 5G (c1s)

Wed, 16 Oct 2024 15:47:47 +0000

arm64: dts: exynos: Add initial support for Samsung Galaxy Note20 5G (c1s)Add initial support for the Samsung Galaxy Note20 5G (c1s/SM-N981B)phone. It was launched in 2020, and it's based on the Exynos 990 SoC. Ithas only one configuration with 8GB of RAM, albeit storage options maydiffer.This device tree adds support for the following:- SimpleFB- 8GB RAM- ButtonsSigned-off-by: Igor Belwon Link: https://lore.kernel.org/r/20241016154747.64343-7-igor.belwon@mentallysanemainliners.orgSigned-off-by: Krzysztof Kozlowski List of files: /linux-6.15/scripts/dtc/include-prefixes/arm64/exynos/Makefile

296621bf - arm64: dts: exynos: Add initial support for Samsung Galaxy S8

Fri, 20 Sep 2024 15:45:08 +0000

arm64: dts: exynos: Add initial support for Samsung Galaxy S8Samsung Galaxy S8 (SM-G950F), codenamed dreamlte, is a mobile phonefrom 2017. It features 4GB RAM, 64GB UFS 2.1, Exynos 8895 SoC and a1440x2960 Super AMOLED display.This initial device tree enables SimpleFB, PSTORE and GPIO keys.Signed-off-by: Ivaylo Ivanov Link: https://lore.kernel.org/r/20240920154508.1618410-11-ivo.ivanov.ivanov1@gmail.comSigned-off-by: Krzysztof Kozlowski List of files: /linux-6.15/scripts/dtc/include-prefixes/arm64/exynos/Makefile

6a5713fc - arm64: dts: exynos: google: Add initial Oriole/pixel 6 board support

Mon, 11 Dec 2023 16:23:30 +0000

arm64: dts: exynos: google: Add initial Oriole/pixel 6 board supportAdd initial board support for the Pixel 6 phone code named Oriole. Thishas been tested with a minimal busybox initramfs and boots to a shell.Tested-by: Will McVicker Reviewed-by: Sam Protsenko Signed-off-by: Peter Griffin Reviewed-by: Alim Akhtar Link: https://lore.kernel.org/r/20231211162331.435900-16-peter.griffin@linaro.orgSigned-off-by: Krzysztof Kozlowski List of files: /linux-6.15/scripts/dtc/include-prefixes/arm64/exynos/Makefile

57de428e - arm64: dts: exynos: add minimal support for exynosautov920 sadk board

Fri, 08 Dec 2023 07:45:25 +0000

arm64: dts: exynos: add minimal support for exynosautov920 sadk boardExynosAutov920 SADK is ExynosAutov920 SoC based SADK(Samsung AutomotiveDevelopment Kit) board. It has 16GB(8GB + 8GB) LPDDR5 RAM and 256GB(128GB + 128GB) UFS.This is minimal support board device-tree. * Serial console * GPIO Key * PWM FANSigned-off-by: Jaewon Kim Link: https://lore.kernel.org/r/20231208074527.50840-3-jaewon02.kim@samsung.comSigned-off-by: Krzysztof Kozlowski List of files: /linux-6.15/scripts/dtc/include-prefixes/arm64/exynos/Makefile

06874015 - arm64: dts: exynos: Add initial device tree support for Exynos7885 SoC

Mon, 21 Feb 2022 19:49:56 +0000

arm64: dts: exynos: Add initial device tree support for Exynos7885 SoCAdd initial Exynos7885 device tree nodes with dts for the Samsung GalaxyA8 (2018), a.k.a. "jackpotlte", with model number "SM-A530F".Currently this includes some clock support, UART support, and I2C nodes.Signed-off-by: David Virag Reviewed-by: Sam Protsenko Link: https://lore.kernel.org/r/20220221194958.117361-2-virag.david003@gmail.comSigned-off-by: Krzysztof Kozlowski List of files: /linux-6.15/scripts/dtc/include-prefixes/arm64/exynos/Makefile

363e5299 - arm64: dts: exynos: Add initial E850-96 board support

Mon, 31 Jan 2022 13:08:49 +0000

arm64: dts: exynos: Add initial E850-96 board supportE850-96 is a 96boards development board manufactured by WinLink. Itincorporates Samsung Exynos850 SoC, and is compatible with 96boardsmezzanine boards [1], as it follows 96boards standards.This patch adds minimal support for E850-96 board. Next features areenabled in board dts file and verified with minimal BusyBox rootfs: * User buttons * LEDs * Serial console * Watchdog timers * RTC * eMMC[1] https://www.96boards.org/products/mezzanine/Signed-off-by: Sam Protsenko Link: https://lore.kernel.org/r/20220131130849.2667-3-semen.protsenko@linaro.orgSigned-off-by: Krzysztof Kozlowski List of files: /linux-6.15/scripts/dtc/include-prefixes/arm64/exynos/Makefile

2b663ae7 - arm64: dts: exynos: add minimal support for exynosautov9 sadk board

Tue, 12 Oct 2021 00:23:14 +0000

arm64: dts: exynos: add minimal support for exynosautov9 sadk boardSADK(Samsung Automotive Development Kit) is the development kit toevaluate Exynos Auto v9 SoC. It has 16GB LPDDR4 DRAM and two256GB Samsung UFS. This patch enables only serial console and ufs0device.Signed-off-by: Chanho Park Link: https://lore.kernel.org/r/20211012002314.38965-4-chanho61.park@samsung.comSigned-off-by: Krzysztof Kozlowski List of files: /linux-6.15/scripts/dtc/include-prefixes/arm64/exynos/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/exynos/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/exynos/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/exynos/Makefile

8ac46fc5 - arm64: dts: exynos: Add dts file for Exynos5433-based TM2E board

Thu, 03 Nov 2016 06:39:09 +0000

arm64: dts: exynos: Add dts file for Exynos5433-based TM2E boardThis patch adds the Device Tree source for Exynos5433-based Samsung TM2Eboard. TM2E board is very similar to the TM2 board so theexynos5433-tm2e.dts includes the TM2 DTS and overrides the differences.Signed-off-by: Chanwoo Choi Signed-off-by: Jaehoon Chung Signed-off-by: Seung-Woo Kim Signed-off-by: Joonyoung Shim Signed-off-by: Inki Dae Signed-off-by: Jonghwa Lee Signed-off-by: Beomho Seo Signed-off-by: Jaewon Kim Signed-off-by: Hyungwon Hwang Signed-off-by: Inha Song Signed-off-by: Ingi kim Signed-off-by: Marek Szyprowski Signed-off-by: Andrzej Hajda Signed-off-by: Sylwester Nawrocki Reviewed-by: Krzysztof Kozlowski Acked-by: Rob Herring Reviewed-by: Javier Martinez Canillas Tested-by: Andi Shyti Signed-off-by: Krzysztof Kozlowski List of files: /linux-6.15/scripts/dtc/include-prefixes/arm64/exynos/Makefile

01e5d235 - arm64: dts: exynos: Add dts file for Exynos5433-based TM2 board

Thu, 03 Nov 2016 06:39:08 +0000

arm64: dts: exynos: Add dts file for Exynos5433-based TM2 boardThis patch adds the Device Tree source for Exynos5433-based Samsung TM2board.This patch adds support for following devices:1. basic SoC- Initial booting for Samsung Exynos5433 SoC- DRAM LPDDR3 (3GB)- eMMC (32GB)- ARM architecture timer2. power management devices- Sasmung S2MPS13 PMIC for the power supply- CPUFREQ for big.LITTLE cores- TMU for big.LITTLE cores and GPU- ADC with thermistor to measure the temperature of AP/Battery/Charger- Maxim MAX77843 Interface PMIC (MUIC/Haptic/Regulator)3. sound devices- I2S for sound bus- LPASS for sound power control- Wolfson WM5110 for sound codec- Maxim MAX98504 for speaker amplifier- TM2 ASoC Machine device driver node3. display devices- DECON, DSI and MIC for the panel output4. USB devices- USB 3.0 DRD (Dual Role Device)- USB 3.0 Host controller5. storage devices- MSHC (Mobile Storage Host Controller) for eMMC device6. misc devices- gpio-keys (power, volume up/down, home key)- PWM (Pulse Width Modulation Timer)Signed-off-by: Chanwoo Choi Signed-off-by: Jaehoon Chung Signed-off-by: Seung-Woo Kim Signed-off-by: Joonyoung Shim Signed-off-by: Inki Dae Signed-off-by: Jonghwa Lee Signed-off-by: Beomho Seo Signed-off-by: Jaewon Kim Signed-off-by: Hyungwon Hwang Signed-off-by: Inha Song Signed-off-by: Ingi kim Signed-off-by: Marek Szyprowski Signed-off-by: Andrzej Hajda Signed-off-by: Sylwester Nawrocki Reviewed-by: Krzysztof Kozlowski Reviewed-by: Javier Martinez Canillas Tested-by: Andi Shyti Signed-off-by: Krzysztof Kozlowski List of files: /linux-6.15/scripts/dtc/include-prefixes/arm64/exynos/Makefile

c87b3e97 - arm64: EXYNOS: Consolidate ARCH_EXYNOS7 symbol into ARCH_EXYNOS

Mon, 16 Nov 2015 01:09:13 +0000

arm64: EXYNOS: Consolidate ARCH_EXYNOS7 symbol into ARCH_EXYNOSThe ARMv8 Exynos family SoCs in Linux kernel are currently: - Exynos5433 (controlled by ARCH_EXYNOS), - Exynos7 (controlled by ARCH_EXYNOS7).It duplicates Kconfig symbols unnecessarily, so consolidate them intoone ARCH_EXYNOS. Future SoCs could fall also under the ARCH_EXYNOSsymbol.The commit should not bring any visible functional change.Signed-off-by: Krzysztof Kozlowski Reviewed-by: Chanwoo Choi Reviewed-by: Pankaj Dubey Tested-by: Alim Akhtar Reviewed-by: Tomasz Figa Reviewed-by: Javier Martinez Canillas Reviewed-by: Andi Shyti List of files: /linux-6.15/scripts/dtc/include-prefixes/arm64/exynos/Makefile

b9024cbc - arm64: dts: Add initial device tree support for exynos7

Sat, 22 Nov 2014 13:41:23 +0000

arm64: dts: Add initial device tree support for exynos7Add initial device tree nodes for exynos7 SoC and board dts fileto support espresso board based on exynos7 SoC.Signed-off-by: Naveen Krishna Ch Signed-off-by: Abhilash Kesavan Reviewed-by: Thomas Abraham Tested-by: Thomas Abraham Cc: Rob Herring Cc: Catalin Marinas Signed-off-by: Kukjin Kim List of files: /linux-6.15/scripts/dtc/include-prefixes/arm64/exynos/Makefile