Changes in Makefile

86d231b1 - PM / devfreq: mediatek: Introduce MediaTek CCI devfreq driver

Tue, 07 Jun 2022 14:05:56 +0000

PM / devfreq: mediatek: Introduce MediaTek CCI devfreq driverWe introduce a devfreq driver for the MediaTek Cache Coherent Interconnect(CCI) used by some MediaTek SoCs.In this driver, we use the passive devfreq driver to get target frequenciesand adjust voltages accordingly. In MT8183 and MT8186, the MediaTek CCIis supplied by the same regulators with the little core CPUs.Signed-off-by: Jia-Wei Chang Signed-off-by: Johnson Wang Acked-by: Chanwoo Choi Tested-by: Kevin Hilman Signed-off-by: Chanwoo Choi List of files: /linux-6.15/drivers/devfreq/Makefile

8bfd4858 - PM / devfreq: Add a driver for the sun8i/sun50i MBUS

Thu, 18 Nov 2021 03:18:41 +0000

PM / devfreq: Add a driver for the sun8i/sun50i MBUSThis driver works by adjusting the divider on the DRAM controller'smodule clock. Thus there is no fixed set of OPPs, only "full speed" downto "quarter speed" (or whatever the maximum divider is on that variant).It makes use of the MDFS hardware in the MBUS, in "DFS" mode, whichtakes care of updating registers during the critical section while DRAMis inaccessible.This driver should support several sunxi SoCs, starting with the A33,which have a DesignWare DDR3 controller with merged PHY register spaceand the matching MBUS register layout (so not A63 or later). However,the driver has only been tested on the A64/H5, so those are the onlycompatibles enabled for now.Acked-by: Chanwoo Choi Signed-off-by: Samuel Holland Signed-off-by: Chanwoo Choi List of files: /linux-6.15/drivers/devfreq/Makefile

98fd9972 - PM / devfreq: tegra20: Deprecate in a favor of emc-stat based driver

Mon, 23 Nov 2020 00:27:15 +0000

PM / devfreq: tegra20: Deprecate in a favor of emc-stat based driverRemove tegra20-devfreq in order to replace it with a EMC_STAT baseddevfreq driver. Previously we were going to use MC_STAT basedtegra20-devfreq driver because EMC_STAT wasn't working properly, butnow that problem is resolved. This resolves complications imposed bythe removed driver since it was depending on both EMC and MC driverssimultaneously.Acked-by: Chanwoo Choi Signed-off-by: Dmitry Osipenko Signed-off-by: Chanwoo Choi List of files: /linux-6.15/drivers/devfreq/Makefile

5173a975 - PM / devfreq: Add generic imx bus scaling driver

Mon, 06 Apr 2020 12:03:07 +0000

PM / devfreq: Add generic imx bus scaling driverAdd initial support for dynamic frequency switching on pieces of the imxinterconnect fabric.All this driver does is set a clk rate based on an opp table, it doesnot map register areas.Signed-off-by: Leonard Crestez Tested-by: Martin Kepplinger Acked-by: Chanwoo Choi Signed-off-by: Chanwoo Choi List of files: /linux-6.15/drivers/devfreq/Makefile

5af744eb - PM / devfreq: Add dynamic scaling for imx8m ddr controller

Fri, 22 Nov 2019 21:45:03 +0000

PM / devfreq: Add dynamic scaling for imx8m ddr controllerAdd driver for dynamic scaling the DDR Controller on imx8m chips. Actualfrequency switching is implemented inside TF-A, this driver wraps theSMC calls and synchronizes the clk tree.The DRAM clocks on imx8m have the following structure (abridged): +----------+ |\ +------+ | dram_pll |-------|M| dram_core | | +----------+ |U|---------->| D | /--|X| | D | dram_alt_root | |/ | R | | | C | +---------+ | | |FIX DIV/4| | | +---------+ | | composite: | | | +----------+ | | | | dram_alt |----/ | | +----------+ | | | dram_apb |-------------------->| | +----------+ +------+The dram_pll is used for higher rates and dram_alt is used for lowerrates. The dram_alt and dram_apb clocks are "imx composite" and theirparent can also be modified.This driver will prepare/enable the new parents ahead of switching (sothat the expected roots are enabled) and afterwards it will callclk_set_parent to ensure the parents in clock framework are up-to-date.The driver relies on dram_pll dram_alt and dram_apb being marked withCLK_GET_RATE_NOCACHE for rate updates.Signed-off-by: Leonard Crestez Acked-by: Chanwoo Choi [cw00.choi: Edit the COMPILE_TEST module dependency in Kconfig]Signed-off-by: Chanwoo Choi List of files: /linux-6.15/drivers/devfreq/Makefile

d196175e - PM / devfreq: Introduce driver for NVIDIA Tegra20

Wed, 01 May 2019 23:38:15 +0000

PM / devfreq: Introduce driver for NVIDIA Tegra20Add devfreq driver for NVIDIA Tegra20 SoC's. The driver periodicallyreads out Memory Controller counters and adjusts memory frequency basedon the memory clients activity.Reviewed-by: Chanwoo Choi Signed-off-by: Dmitry Osipenko [Removed MAINTAINERS updates by MyungJoo so that it can be sent elsewhere.]Signed-off-by: MyungJoo Ham List of files: /linux-6.15/drivers/devfreq/Makefile

23601752 - PM / devfreq: tegra: Rename tegra-devfreq.c to tegra30-devfreq.c

Wed, 01 May 2019 23:38:14 +0000

PM / devfreq: tegra: Rename tegra-devfreq.c to tegra30-devfreq.cIn order to reflect that driver serves NVIDIA Tegra30 and later SoCgenerations, let's rename the driver's source file to "tegra30-devfreq.c".This will make driver files to look more consistent after addition of adriver for Tegra20.Reviewed-by: Chanwoo Choi Signed-off-by: Dmitry Osipenko Signed-off-by: MyungJoo Ham List of files: /linux-6.15/drivers/devfreq/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/devfreq/Makefile

5a893e31 - PM / devfreq: rockchip: add devfreq driver for rk3399 dmc

Mon, 05 Sep 2016 05:06:10 +0000

PM / devfreq: rockchip: add devfreq driver for rk3399 dmcbase on dfi result, we do ddr frequency scaling, registerdmc driver to devfreq framework, and use simple-ondemandpolicy.Signed-off-by: Lin Huang Signed-off-by: MyngJoo Ham Reviewed-by: Chanwoo Choi List of files: /linux-6.15/drivers/devfreq/Makefile

bfcd6204 - PM / devfreq: exynos: Remove unused exynos4/5 busfreq driver

Mon, 23 Nov 2015 14:58:17 +0000

PM / devfreq: exynos: Remove unused exynos4/5 busfreq driverThis patch removes the unused exynos4/5 busfreq driver. Instead,generic exynos-bus frequency driver support the all Exynos SoCs.Signed-off-by: Chanwoo Choi Signed-off-by: MyungJoo Ham Acked-by: Krzysztof Kozlowski List of files: /linux-6.15/drivers/devfreq/Makefile

99613311 - PM / devfreq: Add new passive governor

Tue, 22 Mar 2016 04:44:03 +0000

PM / devfreq: Add new passive governorThis patch adds the new passive governor for DEVFREQ framework. The followinggovernors are already present and used for DVFS (Dynamic Voltage and FrequencyScaling) drivers. The following governors are independently used for one devicedriver which don't give the influence to other device drviers and also don'treceive the effect from other device drivers.- ondemand / performance / powersave / userspaceThe passive governor depends on operation of parent driver with specificgovernos extremely and is not able to decide the new frequency by oneself.According to the decided new frequency of parent driver with governor,the passive governor uses it to decide the appropriate frequency for owndevice driver. The passive governor must need the following informationfrom device tree:- the source clock and OPP tables- the instance of parent deviceFor exameple,there are one more devfreq device drivers which need to change their sourceclock according to their utilization on runtime. But, they share the samepower line (e.g., regulator). So, specific device driver is operated as parentwith ondemand governor and then the rest device driver with passive governoris influenced by parent device.Suggested-by: Myungjoo Ham Signed-off-by: Chanwoo Choi [tjakobi: Reported RCU locking issue and cw00.choi fix it]Reported-by: Tobias Jakobi [linux.amoon: Reported possible recursive locking and cw00.choi fix it]Reported-by: Anand Moon Signed-off-by: MyungJoo Ham Acked-by: Krzysztof Kozlowski List of files: /linux-6.15/drivers/devfreq/Makefile

0722249a - PM / devfreq: exynos: Add generic exynos bus frequency driver

Tue, 03 Nov 2015 10:04:16 +0000

PM / devfreq: exynos: Add generic exynos bus frequency driverThis patch adds the generic exynos bus frequency driver for AMBA AXI busof sub-blocks in exynos SoC with DEVFREQ framework. The Samsung Exynos SoChave the common architecture for bus between DRAM and sub-blocks in SoC.This driver can support the generic bus frequency driver for Exynos SoCs.In devicetree, Each bus block has a bus clock, regulator, operation-pointand devfreq-event devices which measure the utilization of each bus block.Signed-off-by: Chanwoo Choi [m.reichl and linux.amoon: Tested it on exynos4412-odroidu3 board]Tested-by: Markus Reichl Tested-by: Anand Moon Signed-off-by: MyungJoo Ham Acked-by: Krzysztof Kozlowski List of files: /linux-6.15/drivers/devfreq/Makefile

e6ee3192 - devfreq: Fix build break of devfreq-event class

Fri, 30 Jan 2015 04:54:08 +0000

devfreq: Fix build break of devfreq-event classThis patch fixes the build break of the exynos-ppmu driver because Makefilein drivers/devfreq don't include the entry of devfreq-event.c driver.The original patch[1] includes the entry to build devfreq-event.c withoutthe build break. This build break is generated in the process of merging thepatch.[1] https://lkml.org/lkml/2015/1/25/579- [PATCH v10 1/7] devfreq: event: Add new devfreq_event class to provide basic data for devfreq governorCC init/version.oLD init/built-in.odrivers/built-in.o: In function `exynos_ppmu_probe':binder.c:(.text+0x4447ec): undefined reference to `devm_devfreq_event_add_edev'make: *** [vmlinux] Error 1Cc: Rafael J. Wysocki Cc: MyungJoo Ham Signed-off-by: Chanwoo Choi List of files: /linux-6.15/drivers/devfreq/Makefile

f262f28c - PM / devfreq: event: Add devfreq_event class

Mon, 26 Jan 2015 04:16:27 +0000

PM / devfreq: event: Add devfreq_event classThis patch adds a new class in devfreq, devfreq_event, which providesraw data (e.g., memory bus utilization, GPU utilization) for devfreqgovernors.- devfreq_event device : Provides raw data for a governor of a devfreq device- devfreq device : Monitors device state and changes frequency/voltage of the device using the raw data from its devfreq_event device.A devfreq device dertermines performance states (normally the frequencyand the voltage vlues) based on the results its designtated devfreq governor:e.g., ondemand, performance, powersave.In order to give such results required by a devfreq device, the devfreqgovernor requires data that indicates the performance requirement givento the devfreq device. The conventional (previous) implementatino ofdevfreq subsystem requires a devfreq device driver to implement its ownmechanism to acquire performance requirement for its governor. However,there had been issues with such requirements:1. Although performance requirement of such devices is usually acquired from common devices (PMU/PPMU), we do not have any abstract structure to represent them properly.2. Such performance requirement devices (PMU/PPMU) are actual hardware pieces that may be represented by Device Tree directly while devfreq device itself is a virtual entity that are not considered to be represented by Device Tree according to Device Tree folks.In order to address such issues, a devferq_event device (represented bythis patch) provides a template for device drivers representingperformance monitoring unit, which gives the basic or raw data forpreformance requirement, which in turn, is required by devfreq governors.The following description explains the feature of two kind of devfreq class:- devfreq class (existing) : devfreq consumer device use raw data from devfreq_event device for determining proper current system state and change voltage/frequency dynamically using various governors.- devfreq_event class (new) : Provide measured raw data to devfreq device for governorCc: MyungJoo Ham Cc: Kyungmin Park Signed-off-by: Chanwoo Choi [Commit message rewritten & conflict resolved by MyungJoo]Signed-off-by: MyungJoo Ham List of files: /linux-6.15/drivers/devfreq/Makefile

6234f380 - PM / devfreq: tegra: add devfreq driver for Tegra Activity Monitor

Mon, 24 Nov 2014 12:28:17 +0000

PM / devfreq: tegra: add devfreq driver for Tegra Activity MonitorThe ACTMON block can monitor several counters, providing averaging and firinginterrupts based on watermarking configuration. This implementation monitorsthe MCALL and MCCPU counters to choose an appropriate frequency for theexternal memory clock.This patch is based on work by Alex Frid and MikkoPerttunen .Signed-off-by: Tomeu Vizoso Signed-off-by: MyungJoo Ham List of files: /linux-6.15/drivers/devfreq/Makefile

6ccce699 - PM / devfreq: Add Exynos5-bus devfreq driver for Exynos5250

Mon, 04 Feb 2013 12:14:48 +0000

PM / devfreq: Add Exynos5-bus devfreq driver for Exynos5250Exynos5-bus device devfreq driver monitors PPMU counters andadjusts operating frequencies and voltages with OPP. ASV shouldbe used to provide appropriate voltages as per the speed groupof the SoC rather than using a constant 1.025V.Signed-off-by: Abhilash Kesavan [myungjoo.ham@samsung.com: minor style update]Signed-off-by: MyungJoo Ham Cc: Jonghwan Choi Cc: Kukjin Kim List of files: /linux-6.15/drivers/devfreq/Makefile

537eb8e2 - PM / devfreq: Move exynos4 devfreq driver into a new sub-directory

Fri, 18 Jan 2013 13:24:29 +0000

PM / devfreq: Move exynos4 devfreq driver into a new sub-directoryIn anticipation of the new exynos5 devfreq and ppmu driver, createan exynos sub-directory. Move the existing exynos4 devfreq driverinto the same.Signed-off-by: Abhilash Kesavan Acked-by: MyungJoo Ham Cc: Jonghwan Choi Cc: Kukjin Kim List of files: /linux-6.15/drivers/devfreq/Makefile

7b405038 - PM/Devfreq: Add Exynos4-bus device DVFS driver for Exynos4210/4212/4412.

Thu, 14 Jul 2011 01:33:55 +0000

PM/Devfreq: Add Exynos4-bus device DVFS driver for Exynos4210/4212/4412.Exynos4-bus device devfreq driver add DVFS capability forExynos4210/4212/4412-Bus (memory). The driver monitors PPMU counters of memorycontrollers and adjusts operating frequencies and voltages with OPP.For Exynos4210, vdd_int is controlled. For exynos4412/4212, vdd_mif andvdd_int are controlled.Dependency (CONFIG_EXYNOS_ASV):Exynos4 ASV driver has been posted in the mailing list; however, itsi not yet upstreamed. Although the current revision of Exynos4 ASVpatch does not contain "CONFIG_EXYNOS_ASV", we have added the symbolto hide the dependent from compilers for now. As soon as Exynos4 ASVdrivers are merged, the #ifdef statement will be removed or thename will be changed.However, enabling ASV is essential in most Exynos4 chips to reducethe power consumption of Exynos4210 because without ASV, this Devfreqdriver assumes the worst case scenario, which consumes more power.Signed-off-by: MyungJoo Ham Signed-off-by: Kyungmin Park ---Changes from v1- Support 4212 and 4412 as well as 4210. List of files: /linux-6.15/drivers/devfreq/Makefile

ce26c5bb - PM / devfreq: Add basic governors

Sat, 01 Oct 2011 22:19:34 +0000

PM / devfreq: Add basic governorsFour cpufreq-like governors are provided as examples.powersave: use the lowest frequency possible. The user (device) shouldset the polling_ms as 0 because polling is useless for this governor.performance: use the highest freqeuncy possible. The user (device)should set the polling_ms as 0 because polling is useless for thisgovernor.userspace: use the user specified frequency stored atdevfreq.user_set_freq. With sysfs support in the following patch, a usermay set the value with the sysfs interface.simple_ondemand: simplified version of cpufreq's ondemand governor.When a user updates OPP entries (enable/disable/add), OPP frameworkautomatically notifies devfreq to update operating frequencyaccordingly. Thus, devfreq users (device drivers) do not need to updatedevfreq manually with OPP entry updates or set polling_ms for powersave, performance, userspace, or any other "static" governors.Note that these are given only as basic examples for governors and anydevices with devfreq may implement their own governors with the driversand use them.Signed-off-by: MyungJoo Ham Signed-off-by: Kyungmin Park Reviewed-by: Mike Turquette Acked-by: Kevin Hilman Signed-off-by: Rafael J. Wysocki List of files: /linux-6.15/drivers/devfreq/Makefile

a3c98b8b - PM: Introduce devfreq: generic DVFS framework with device-specific OPPs

Sat, 01 Oct 2011 22:19:15 +0000

PM: Introduce devfreq: generic DVFS framework with device-specific OPPsWith OPPs, a device may have multiple operable frequency and voltagesets. However, there can be multiple possible operable sets and a systemwill need to choose one from them. In order to reduce the powerconsumption (by reducing frequency and voltage) without affecting theperformance too much, a Dynamic Voltage and Frequency Scaling (DVFS)scheme may be used.This patch introduces the DVFS capability to non-CPU devices with OPPs.DVFS is a techique whereby the frequency and supplied voltage of adevice is adjusted on-the-fly. DVFS usually sets the frequency as lowas possible with given conditions (such as QoS assurance) and adjustsvoltage according to the chosen frequency in order to reduce powerconsumption and heat dissipation.The generic DVFS for devices, devfreq, may appear quite similar with/drivers/cpufreq. However, cpufreq does not allow to have multipledevices registered and is not suitable to have multiple heterogenousdevices with different (but simple) governors.Normally, DVFS mechanism controls frequency based on the demand forthe device, and then, chooses voltage based on the chosen frequency.devfreq also controls the frequency based on the governor's frequencyrecommendation and let OPP pick up the pair of frequency and voltagebased on the recommended frequency. Then, the chosen OPP is passed todevice driver's "target" callback.When PM QoS is going to be used with the devfreq device, the devicedriver should enable OPPs that are appropriate with the current PM QoSrequests. In order to do so, the device driver may call opp_enable andopp_disable at the notifier callback of PM QoS so that PM QoS'supdate_target() call enables the appropriate OPPs. Note that at leastone of OPPs should be enabled at any time; be careful when there is atransition.Signed-off-by: MyungJoo Ham Signed-off-by: Kyungmin Park Reviewed-by: Mike Turquette Acked-by: Kevin Hilman Signed-off-by: Rafael J. Wysocki List of files: /linux-6.15/drivers/devfreq/Makefile