Changes in Makefile

27e0fef6 - soc: tegra: Move powergate-bpmp driver to the genpd dir

Wed, 05 Jul 2023 22:18:03 +0000

soc: tegra: Move powergate-bpmp driver to the genpd dirTo simplify with maintenance let's move the powergate-bpmp driver to thenew genpd directory. Going forward, patches are intended to be managedthrough a separate git tree, according to MAINTAINERS.Note that, we leave the pmc driver in the soc directory for now, as itlooks like it may need some re-structuring before it's ready to be moved.Cc: Thierry Reding Cc: Jonathan Hunter Cc: Mikko Perttunen Cc: Acked-by: Thierry Reding Signed-off-by: Ulf Hansson List of files: /linux-6.15/drivers/soc/tegra/Makefile

b7134422 - soc/tegra: cbb: Add CBB 1.0 driver for Tegra194

Wed, 11 May 2022 20:16:47 +0000

soc/tegra: cbb: Add CBB 1.0 driver for Tegra194Adding driver to handle errors from Control Backbone (CBB) which aregenerated due to illegal accesses. CBB 1.0 is used in Tegra194 SoCs.When an error is reported from a NOC within CBB, the driver prints debuginformation about failed transaction like Error Code, Error Description,Master, Address, AXI ID, Cache, Protection, Security Group etc. It thencauses system crash using BUG_ON() or call WARN() based on whether theerror type is fatal or not.Signed-off-by: Sumit Gupta Signed-off-by: Thierry Reding List of files: /linux-6.15/drivers/soc/tegra/Makefile

29962197 - soc/tegra: Add Tegra186 ARI driver

Thu, 17 Jun 2021 12:13:07 +0000

soc/tegra: Add Tegra186 ARI driverAdd a driver to hook into panic notifiers and print machine checkstatus for debugging. Status information is retrieved via SMC. Thisis supported by upstream ARM Trusted Firmware.Signed-off-by: Mikko Perttunen Signed-off-by: Thierry Reding List of files: /linux-6.15/drivers/soc/tegra/Makefile

78380743 - soc/tegra: regulators: Add regulators coupler for Tegra30

Thu, 25 Jul 2019 15:18:32 +0000

soc/tegra: regulators: Add regulators coupler for Tegra30Add regulators coupler for Tegra30 SoCs that performs voltage balancingof a coupled regulators and thus provides voltage scaling functionality.There are 2 coupled regulators on all Tegra30 SoCs: CORE and CPU. Thecoupled regulator voltages shall be in a range of 300mV from each otherand CORE voltage shall be higher than the CPU by N mV, where N dependson the CPU voltage.Signed-off-by: Dmitry Osipenko Acked-By: Peter De Schrijver Signed-off-by: Thierry Reding List of files: /linux-6.15/drivers/soc/tegra/Makefile

496747e7 - soc/tegra: regulators: Add regulators coupler for Tegra20

Thu, 25 Jul 2019 15:18:31 +0000

soc/tegra: regulators: Add regulators coupler for Tegra20Add regulators coupler for Tegra20 SoCs that performs voltage balancingof a coupled regulators and thus provides voltage scaling functionality.There are 3 coupled regulators on all Tegra20 SoCs: CORE, RTC and CPU.The CORE and RTC voltages shall be in range of 170mV from each other andthey both shall be higher than the CPU voltage by at least 120mV. Thissounds like it could be handle by a generic voltage balancer, but the COREvoltage scaling isn't implemented in any of the upstream drivers yet.It will take quite some time and effort to hook up voltage scaling forall of the drivers, hence we will use a custom coupler that will managethe CPU voltage scaling for the starter.Signed-off-by: Dmitry Osipenko Acked-By: Peter De Schrijver Signed-off-by: Thierry Reding List of files: /linux-6.15/drivers/soc/tegra/Makefile

c641ec6e - soc/tegra: pmc: Consolidate Tegra186 support

Wed, 30 Aug 2017 10:42:34 +0000

soc/tegra: pmc: Consolidate Tegra186 supportMove Tegra186 support to the consolidated PMC driver to reduce some ofthe duplication and also gain I/O pad functionality on the new SoC as aside-effect.Signed-off-by: Thierry Reding List of files: /linux-6.15/drivers/soc/tegra/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/soc/tegra/Makefile

e7149a7a - soc/tegra: bpmp: Implement generic PM domains

Wed, 29 Mar 2017 16:34:52 +0000

soc/tegra: bpmp: Implement generic PM domainsThe BPMP firmware, found on Tegra186 and later, provides an ABI that canbe used to enable and disable power to several power partitions in TegraSoCs. The ABI allows for enumeration of the available power partitions,so the driver can be reused on future generations, provided the BPMP ABIremains stable.Based on work by Stefan Kristiansson and MikkoPerttunen .Signed-off-by: Thierry Reding Reviewed-by: Ulf Hansson Signed-off-by: Thierry Reding List of files: /linux-6.15/drivers/soc/tegra/Makefile

7e10cf74 - soc/tegra: Move Tegra flowctrl driver

Tue, 28 Mar 2017 12:42:54 +0000

soc/tegra: Move Tegra flowctrl driverThe flowctrl driver is required for both ARM and ARM64 Tegra devicesand in order to enable support for it for ARM64, move the Tegra flowctrldriver into drivers/soc/tegra.By moving the flowctrl driver, tegra_flowctrl_init() is now called byvia an early initcall and to prevent this function from attempting tomapping IO space for a non-Tegra device, a test for 'soc_is_tegra()'is also added.Signed-off-by: Jon Hunter Signed-off-by: Thierry Reding List of files: /linux-6.15/drivers/soc/tegra/Makefile

5e7d4c65 - soc/tegra: Implement Tegra186 PMC support

Thu, 23 Feb 2017 17:11:57 +0000

soc/tegra: Implement Tegra186 PMC supportThe power management controller on Tegra186 has changed in backwards-incompatible ways with respect to earlier generations. This implements anew driver that supports inversion of the PMU interrupt as well as the"recovery", "bootloader" and "forced-recovery" reboot commands.Acked-by: Rob Herring Signed-off-by: Thierry Reding List of files: /linux-6.15/drivers/soc/tegra/Makefile

7c9fd23f - soc: tegra: Remove redundant $(CONFIG_ARCH_TEGRA) in Makefile

Fri, 31 Jul 2015 05:58:21 +0000

soc: tegra: Remove redundant $(CONFIG_ARCH_TEGRA) in MakefileKbuild descends into drivers/soc/tegra/ only when CONFIG_ARCH_TEGRAis enabled. (see drivers/soc/Makefile)$(CONFIG_ARCH_TEGRA) in drivers/soc/tegra/Makefile always evaluatesto 'y'.Signed-off-by: Masahiro Yamada Signed-off-by: Thierry Reding List of files: /linux-6.15/drivers/soc/tegra/Makefile

7232398a - ARM: tegra: Convert PMC to a driver

Fri, 11 Jul 2014 11:19:06 +0000

ARM: tegra: Convert PMC to a driverThis commit converts the PMC support code to a platform driver. Becausethe boot process needs to call into this driver very early, also set upa minimal environment via an early initcall.Signed-off-by: Thierry Reding List of files: /linux-6.15/drivers/soc/tegra/Makefile

a2686766 - soc/tegra: Implement runtime check for Tegra SoCs

Wed, 16 Jul 2014 12:01:44 +0000

soc/tegra: Implement runtime check for Tegra SoCsSubsequent patches will move some of the initialization code from SoCsetup code to regular initcalls. To prevent breakage on other SoCs inmulti-platform builds, these initcalls need to check that they indeedrun on Tegra.Signed-off-by: Thierry Reding List of files: /linux-6.15/drivers/soc/tegra/Makefile

783c8f4c - soc/tegra: Add efuse driver for Tegra

Thu, 12 Jun 2014 15:36:37 +0000

soc/tegra: Add efuse driver for TegraImplement fuse driver for Tegra20, Tegra30, Tegra114 and Tegra124. Thisreplaces functionality previously provided in arch/arm/mach-tegra, whichis removed in this patch.While at it, move the only user of the global tegra_revision variableover to tegra_sku_info.revision and export tegra_fuse_readl() to allowdrivers to read calibration fuses.Signed-off-by: Peter De Schrijver Signed-off-by: Stephen Warren Signed-off-by: Thierry Reding List of files: /linux-6.15/drivers/soc/tegra/Makefile