<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="/rss.xsl.xml"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
    <title>Changes in Kconfig</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>91d7f3f8 - PM / devfreq: exynos: Rename Exynos to lowercase</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/devfreq/event/Kconfig#91d7f3f8</link>
        <description>PM / devfreq: exynos: Rename Exynos to lowercaseFix up inconsistent usage of upper and lowercase letters in &quot;Exynos&quot;name.&quot;EXYNOS&quot; is not an abbreviation but a regular trademarked name.Therefore it should be written with lowercase letters starting withcapital letter.The lowercase &quot;Exynos&quot; name is promoted by its manufacturer SamsungElectronics Co., Ltd., in advertisement materials and on website.Signed-off-by: Krzysztof Kozlowski &lt;krzk@kernel.org&gt;Signed-off-by: Chanwoo Choi &lt;cw00.choi@samsung.com&gt;

            List of files:
            /linux-6.15/drivers/devfreq/event/Kconfig</description>
        <pubDate>Sat, 04 Jan 2020 15:21:00 +0000</pubDate>
        <dc:creator>Krzysztof Kozlowski &lt;krzk@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>eff5d31f - PM / devfreq: rk3399_dmc: Add COMPILE_TEST and HAVE_ARM_SMCCC dependency</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/devfreq/event/Kconfig#eff5d31f</link>
        <description>PM / devfreq: rk3399_dmc: Add COMPILE_TEST and HAVE_ARM_SMCCC dependencyTo build test, add COMPILE_TEST depedency to both ARM_RK3399_DMC_DEVFREQand DEVFREQ_EVENT_ROCKCHIP_DFI configuration. And ARM_RK3399_DMC_DEVFREQused the SMCCC interface so that add HAVE_ARM_SMCCC dependency to preventthe build break.Reported-by: kbuild test robot &lt;lkp@intel.com&gt;Signed-off-by: Chanwoo Choi &lt;cw00.choi@samsung.com&gt;

            List of files:
            /linux-6.15/drivers/devfreq/event/Kconfig</description>
        <pubDate>Thu, 12 Dec 2019 02:20:30 +0000</pubDate>
        <dc:creator>Chanwoo Choi &lt;cw00.choi@samsung.com&gt;</dc:creator>
    </item>
<item>
        <title>ec8f24b7 - treewide: Add SPDX license identifier - Makefile/Kconfig</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/devfreq/event/Kconfig#ec8f24b7</link>
        <description>treewide: Add SPDX license identifier - Makefile/KconfigAdd SPDX license identifiers to all Make/Kconfig files which: - Have no license information of any formThese files fall under the project license, GPL v2 only. The resulting SPDXlicense identifier is:  GPL-2.0-onlySigned-off-by: Thomas Gleixner &lt;tglx@linutronix.de&gt;Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/drivers/devfreq/event/Kconfig</description>
        <pubDate>Sun, 19 May 2019 12:07:45 +0000</pubDate>
        <dc:creator>Thomas Gleixner &lt;tglx@linutronix.de&gt;</dc:creator>
    </item>
<item>
        <title>69e67a06 - PM / devfreq: exynos-nocp: Select REGMAP_MMIO</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/devfreq/event/Kconfig#69e67a06</link>
        <description>PM / devfreq: exynos-nocp: Select REGMAP_MMIOThis driver uses devm_regmap_init_mmio(), so select REGMAP_MMIO to avoidbuild failure.Signed-off-by: Axel Lin &lt;axel.lin@ingics.com&gt;Acked-by: Chanwoo Choi &lt;cw00.choi@samsung.com&gt;Signed-off-by: Rafael J. Wysocki &lt;rafael.j.wysocki@intel.com&gt;

            List of files:
            /linux-6.15/drivers/devfreq/event/Kconfig</description>
        <pubDate>Sun, 25 Sep 2016 12:13:57 +0000</pubDate>
        <dc:creator>Axel Lin &lt;axel.lin@ingics.com&gt;</dc:creator>
    </item>
<item>
        <title>b9d1262b - PM / devfreq: event: support rockchip dfi controller</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/devfreq/event/Kconfig#b9d1262b</link>
        <description>PM / devfreq: event: support rockchip dfi controlleron rk3399 platform, there is dfi conroller can monitorddr load, base on this result, we can do ddr freqencyscaling.Signed-off-by: Lin Huang &lt;hl@rock-chips.com&gt;Signed-off-by: MyungJoo Ham &lt;myungjoo.ham@samsung.com&gt;Acked-by: Chanwoo Choi &lt;cw00.choi@samsung.com&gt;

            List of files:
            /linux-6.15/drivers/devfreq/event/Kconfig</description>
        <pubDate>Mon, 05 Sep 2016 05:06:08 +0000</pubDate>
        <dc:creator>Lin Huang &lt;hl@rock-chips.com&gt;</dc:creator>
    </item>
<item>
        <title>797da559 - PM / devfreq: Add COMPILE_TEST for build coverage</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/devfreq/event/Kconfig#797da559</link>
        <description>PM / devfreq: Add COMPILE_TEST for build coverageThe SoC-specific devfreq and devfreq-event drivers can be build testedon all architectures.Signed-off-by: Krzysztof Kozlowski &lt;k.kozlowski@samsung.com&gt;Reviewed-by: Chanwoo Choi &lt;cw00.choi@samsung.com&gt;Signed-off-by: MyungJoo Ham &lt;myungjoo.ham@samsung.com&gt;

            List of files:
            /linux-6.15/drivers/devfreq/event/Kconfig</description>
        <pubDate>Fri, 19 Aug 2016 06:36:55 +0000</pubDate>
        <dc:creator>Krzysztof Kozlowski &lt;k.kozlowski@samsung.com&gt;</dc:creator>
    </item>
<item>
        <title>a63eb1a6 - PM / devfreq: make event/exynos-ppmu DEVFREQ_EVENT_EXYNOS_PPMU tristate</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/devfreq/event/Kconfig#a63eb1a6</link>
        <description>PM / devfreq: make event/exynos-ppmu DEVFREQ_EVENT_EXYNOS_PPMU tristateThe Kconfig currently controlling compilation of this code is:config DEVFREQ_EVENT_EXYNOS_PPMU  bool &quot;EXYNOS PPMU (Platform Performance Monitoring Unit) DEVFREQ event Driver&quot;...meaning that it currently is not being built as a module by anyone.Rather than rip out the existing modular code, Chanwoo indicatedthat he&apos;d rather see the driver offered as tristate.I don&apos;t have the hardware for runtime validation, so this changeis only validated for compile and modpost.Signed-off-by: Paul Gortmaker &lt;paul.gortmaker@windriver.com&gt;Acked-by: Chanwoo Choi &lt;cw00.choi@samsung.com&gt;Signed-off-by: MyungJoo Ham &lt;myungjoo.ham@samsung.com&gt;

            List of files:
            /linux-6.15/drivers/devfreq/event/Kconfig</description>
        <pubDate>Sat, 25 Jun 2016 18:43:51 +0000</pubDate>
        <dc:creator>Paul Gortmaker &lt;paul.gortmaker@windriver.com&gt;</dc:creator>
    </item>
<item>
        <title>64cb7f67 - PM / devfreq: make event/exynos-nocp DEVFREQ_EVENT_EXYNOS_NOCP tristate</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/devfreq/event/Kconfig#64cb7f67</link>
        <description>PM / devfreq: make event/exynos-nocp DEVFREQ_EVENT_EXYNOS_NOCP tristateThe Kconfig currently controlling compilation of this code is:event/Kconfig:config DEVFREQ_EVENT_EXYNOS_NOCPevent/Kconfig:  bool &quot;EXYNOS NoC (Network On Chip) Probe DEVFREQ event Driver&quot;...meaning that it currently is not being built as a module by anyone.Rather than rip out the existing modular code, Chanwoo indicatedthat he&apos;d rather see the driver offered as tristate.I don&apos;t have the hardware for runtime validation, so this changeis only validated for compile and modpost.Signed-off-by: Paul Gortmaker &lt;paul.gortmaker@windriver.com&gt;Acked-by: Chanwoo Choi &lt;cw00.choi@samsung.com&gt;Signed-off-by: MyungJoo Ham &lt;myungjoo.ham@samsung.com&gt;

            List of files:
            /linux-6.15/drivers/devfreq/event/Kconfig</description>
        <pubDate>Sat, 25 Jun 2016 18:43:50 +0000</pubDate>
        <dc:creator>Paul Gortmaker &lt;paul.gortmaker@windriver.com&gt;</dc:creator>
    </item>
<item>
        <title>0179a913 - PM / devfreq: event: Add new Exynos NoC probe driver</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/devfreq/event/Kconfig#0179a913</link>
        <description>PM / devfreq: event: Add new Exynos NoC probe driverThis patch adds NoC (Network on Chip) Probe driver which providesthe primitive values to get the performance data. The packets that the Networkon Chip (NoC) probes detects are transported over the network infrastructure.Exynos542x bus has multiple NoC probes to provide bandwidth information aboutbehavior of the SoC that you can use while analyzing system performance.Signed-off-by: Chanwoo Choi &lt;cw00.choi@samsung.com&gt;Tested-by: Markus Reichl &lt;m.reichl@fivetechno.de&gt;Tested-by: Anand Moon &lt;linux.amoon@gmail.com&gt;Reviewed-by: Krzysztof Kozlowski &lt;k.kozlowski@samsung.com&gt;

            List of files:
            /linux-6.15/drivers/devfreq/event/Kconfig</description>
        <pubDate>Thu, 07 Apr 2016 02:29:11 +0000</pubDate>
        <dc:creator>Chanwoo Choi &lt;cw00.choi@samsung.com&gt;</dc:creator>
    </item>
<item>
        <title>f262f28c - PM / devfreq: event: Add devfreq_event class</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/devfreq/event/Kconfig#f262f28c</link>
        <description>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 &lt;myungjoo.ham@samsung.com&gt;Cc: Kyungmin Park &lt;kyungmin.park@samsung.com&gt;Signed-off-by: Chanwoo Choi &lt;cw00.choi@samsung.com&gt;[Commit message rewritten &amp; conflict resolved by MyungJoo]Signed-off-by: MyungJoo Ham &lt;myungjoo.ham@samsung.com&gt;

            List of files:
            /linux-6.15/drivers/devfreq/event/Kconfig</description>
        <pubDate>Mon, 26 Jan 2015 04:16:27 +0000</pubDate>
        <dc:creator>Chanwoo Choi &lt;cw00.choi@samsung.com&gt;</dc:creator>
    </item>
</channel>
</rss>
