Changes in Makefile

72c81bb6 - memory: tegra: Add Tegra234 support

Fri, 06 May 2022 13:23:09 +0000

memory: tegra: Add Tegra234 supportThe memory controller and external memory controller found on Tegra234is similar to the version found on earlier SoCs but supports a number ofnew memory clients.Add initial memory client definitions for the Tegra234 so that the SMMUstream ID override registers can be properly programmed at boot time.Signed-off-by: Thierry Reding Link: https://lore.kernel.org/r/20220506132312.3910637-2-thierry.reding@gmail.comSigned-off-by: Krzysztof Kozlowski List of files: /linux-6.15/drivers/memory/tegra/Makefile

8fd9f632 - memory: tegra: Split Tegra194 data into separate file

Wed, 02 Jun 2021 16:33:02 +0000

memory: tegra: Split Tegra194 data into separate fileKeep the directory structure consistent by splitting the Tegra194 datainto a separate file.Signed-off-by: Thierry Reding Link: https://lore.kernel.org/r/20210602163302.120041-13-thierry.reding@gmail.comSigned-off-by: Krzysztof Kozlowski List of files: /linux-6.15/drivers/memory/tegra/Makefile

7355c7b9 - memory: tegra: Unify drivers

Wed, 02 Jun 2021 16:33:00 +0000

memory: tegra: Unify driversThe Tegra210 (and earlier) driver now supports all the functionalitythat the Tegra186 (and later) driver does, so they can be unified.Note that previously the Tegra186 (and later) driver could be unloaded,even if that was perhaps not very useful. Older chips don't support thatyet, but once they do this code can be reenabled.Signed-off-by: Thierry Reding Link: https://lore.kernel.org/r/20210602163302.120041-11-thierry.reding@gmail.comSigned-off-by: Krzysztof Kozlowski List of files: /linux-6.15/drivers/memory/tegra/Makefile

9b9d8632 - memory: tegra: Add EMC scaling sequence code for Tegra210

Wed, 29 May 2019 08:21:37 +0000

memory: tegra: Add EMC scaling sequence code for Tegra210This patch includes the sequence for clock tuning and the dynamictraining mechanism for the clock above 800MHz.And historically there have been different sequences to change the EMCclock. The sequence to be used is specified in the EMC table.However, for the currently supported upstreaming platform, only the mostrecent sequence is used. So only support that in this patch.Based on the work of Peter De Schrijver .Signed-off-by: Joseph Lo Signed-off-by: Thierry Reding List of files: /linux-6.15/drivers/memory/tegra/Makefile

10de2114 - memory: tegra: Add EMC scaling support code for Tegra210

Wed, 29 May 2019 08:21:36 +0000

memory: tegra: Add EMC scaling support code for Tegra210This is the initial patch for Tegra210 EMC frequency scaling. It has thecode to program various aspects of the EMC that are standardized, but itdoes not yet include the specific programming sequence needed for clockscaling.The driver is designed to support LPDDR4 SDRAM. Devices that use LPDDR4need to perform training of the RAM before it can be used. Firmware willperform this training during early boot and pass a table of supportedfrequencies to the kernel via device tree.For the frequencies above 800 MHz, periodic retraining is needed tocompensate for changes in timing. This periodic training will have to beperformed until the frequency drops back to or below 800 MHz.This driver provides helpers used during this runtime retraining thatwill be used by the sequence specific code in a follow-up patch.Based on work by Peter De Schrijver .Signed-off-by: Joseph Lo Signed-off-by: Thierry Reding List of files: /linux-6.15/drivers/memory/tegra/Makefile

a127e690 - memory: tegra: Add support for the Tegra194 memory controller

Sun, 22 Dec 2019 14:10:32 +0000

memory: tegra: Add support for the Tegra194 memory controllerThe memory and external memory controllers on Tegra194 are very similarto their predecessors from Tegra186. Add the necessary SoC-specific datato support the newer versions.Signed-off-by: Thierry Reding List of files: /linux-6.15/drivers/memory/tegra/Makefile

52d15dd2 - memory: tegra: Support DVFS on Tegra186 and later

Sun, 22 Dec 2019 14:10:30 +0000

memory: tegra: Support DVFS on Tegra186 and laterAdd a Tegra186 (and later) EMC driver that reads the EMC DVFS tablesfrom BPMP and uses the EMC clock to change the external memory clock.This currently only provides a debugfs interface to show the availablefrequencies and set lower and upper limits of the allowed range. Thiscan be used for testing the various frequencies. The goal is toeventually integrate this with the interconnect framework so that theEMC frequency can be scaled based on demand from memory clients.Signed-off-by: Thierry Reding List of files: /linux-6.15/drivers/memory/tegra/Makefile

e34212c7 - memory: tegra: Introduce Tegra30 EMC driver

Sun, 11 Aug 2019 21:00:40 +0000

memory: tegra: Introduce Tegra30 EMC driverIntroduce driver for the External Memory Controller (EMC) found on Tegra30chips, it controls the external DRAM on the board. The purpose of thisdriver is to program memory timing for external memory on the EMC clockrate change.Acked-by: Peter De Schrijver Signed-off-by: Dmitry Osipenko Tested-by: Peter Geis Signed-off-by: Thierry Reding List of files: /linux-6.15/drivers/memory/tegra/Makefile

96e5da7c - memory: tegra: Introduce Tegra20 EMC driver

Sun, 21 Oct 2018 18:30:52 +0000

memory: tegra: Introduce Tegra20 EMC driverIntroduce driver for the External Memory Controller (EMC) found on Tegra20chips, which controls the external DRAM on the board. The purpose of thisdriver is to program memory timing for external memory on the EMC clockrate change.Signed-off-by: Dmitry Osipenko Acked-by: Peter De Schrijver Signed-off-by: Thierry Reding List of files: /linux-6.15/drivers/memory/tegra/Makefile

a8d502fd - memory: tegra: Squash tegra20-mc into common tegra-mc driver

Mon, 09 Apr 2018 19:28:31 +0000

memory: tegra: Squash tegra20-mc into common tegra-mc driverTegra30+ has some minor differences in registers / bits layout comparedto Tegra20. Let's squash Tegra20 driver into the common tegra-mc driverin a preparation for the upcoming MC hot reset controls implementation,avoiding code duplication.Note that this currently doesn't report the value of MC_GART_ERROR_REQbecause it is located within the GART register area and cannot be safelyaccessed from the MC driver (this happens to work only by accident). Theproper solution is to integrate the GART driver with the MC driver, muchlike is done for the Tegra SMMU, but that is an invasive change and willbe part of a separate patch series.Signed-off-by: Dmitry Osipenko Signed-off-by: Thierry Reding List of files: /linux-6.15/drivers/memory/tegra/Makefile

02b0cc52 - memory: tegra: Add Tegra186 support

Wed, 13 Dec 2017 11:58:21 +0000

memory: tegra: Add Tegra186 supportThe memory controller found on Tegra186 is different in some respects toits predecessors. Most notably it no longer implements an SMMU, but doesassign ARM SMMU stream IDs for each memory client instead.Provide a driver that programs these registers so that memory clientscan translate addresses via the ARM SMMU.Signed-off-by: Thierry Reding List of files: /linux-6.15/drivers/memory/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/memory/tegra/Makefile

588c43a7 - memory: tegra: Add Tegra210 support

Mon, 23 Mar 2015 09:45:12 +0000

memory: tegra: Add Tegra210 supportAdd the table of memory clients and SWGROUPs for Tegra210 to enable SMMUsupport for this new SoC.Signed-off-by: Thierry Reding List of files: /linux-6.15/drivers/memory/tegra/Makefile

73a7f0a9 - memory: tegra: Add EMC (external memory controller) driver

Thu, 12 Mar 2015 14:48:03 +0000

memory: tegra: Add EMC (external memory controller) driverImplements functionality needed to change the rate of the memory busclock.Signed-off-by: Mikko Perttunen Signed-off-by: Tomeu Vizoso Signed-off-by: Thierry Reding List of files: /linux-6.15/drivers/memory/tegra/Makefile

242b1d71 - memory: tegra: Add Tegra132 support

Fri, 07 Nov 2014 15:10:41 +0000

memory: tegra: Add Tegra132 supportThe memory controller on Tegra132 is very similar to the one found onTegra124. But the Denver CPUs don't have an outer cache, so dcachemaintenance is done slightly differently.Signed-off-by: Thierry Reding List of files: /linux-6.15/drivers/memory/tegra/Makefile

89184651 - memory: Add NVIDIA Tegra memory controller support

Wed, 16 Apr 2014 07:24:44 +0000

memory: Add NVIDIA Tegra memory controller supportThe memory controller on NVIDIA Tegra exposes various knobs that can beused to tune the behaviour of the clients attached to it.Currently this driver sets up the latency allowance registers to the HWdefaults. Eventually an API should be exported by this driver (via acustom API or a generic subsystem) to allow clients to register latencyrequirements.This driver also registers an IOMMU (SMMU) that's implemented by thememory controller. It is supported on Tegra30, Tegra114 and Tegra124currently. Tegra20 has a GART instead.The Tegra SMMU operates on memory clients and SWGROUPs. A memory clientis a unidirectional, special-purpose DMA master. A SWGROUP represents aset of memory clients that form a logical functional unit correspondingto a single device. Typically a device has two clients: one client forread transactions and one client for write transactions, but there arealso devices that have only read clients, but many of them (such as thedisplay controllers).Because there is no 1:1 relationship between memory clients and devicesthe driver keeps a table of memory clients and the SWGROUPs that theybelong to per SoC. Note that this is an exception and due to the factthat the SMMU is tightly integrated with the rest of the Tegra SoC. Theuse of these tables is discouraged in drivers for generic IOMMU devicessuch as the ARM SMMU because the same IOMMU could be used in any numberof SoCs and keeping such tables for each SoC would not scale.Acked-by: Joerg Roedel Signed-off-by: Thierry Reding List of files: /linux-6.15/drivers/memory/tegra/Makefile