)]}'
{
  "log": [
    {
      "commit": "7b4050381127ae11fcfc74a106d715a5fbbf888a",
      "tree": "9f3b90d254776e92bf69a1be658198ad34ac7651",
      "parents": [
        "390f998509bf049019df0b078c0a6606e0d57fb4"
      ],
      "author": {
        "name": "MyungJoo Ham",
        "email": "myungjoo.ham@samsung.com",
        "time": "Thu Jul 14 10:33:55 2011 +0900"
      },
      "committer": {
        "name": "MyungJoo Ham",
        "email": "myungjoo.ham@samsung.com",
        "time": "Tue Dec 20 14:08:08 2011 +0900"
      },
      "message": "PM/Devfreq: Add Exynos4-bus device DVFS driver for Exynos4210/4212/4412.\n\nExynos4-bus device devfreq driver add DVFS capability for\nExynos4210/4212/4412-Bus (memory). The driver monitors PPMU counters of memory\ncontrollers and adjusts operating frequencies and voltages with OPP.\nFor Exynos4210, vdd_int is controlled. For exynos4412/4212, vdd_mif and\nvdd_int are controlled.\n\nDependency (CONFIG_EXYNOS_ASV):\nExynos4 ASV driver has been posted in the mailing list; however, it\nsi not yet upstreamed. Although the current revision of Exynos4 ASV\npatch does not contain \"CONFIG_EXYNOS_ASV\", we have added the symbol\nto hide the dependent from compilers for now. As soon as Exynos4 ASV\ndrivers are merged, the #ifdef statement will be removed or the\nname will be changed.\n\nHowever, enabling ASV is essential in most Exynos4 chips to reduce\nthe power consumption of Exynos4210 because without ASV, this Devfreq\ndriver assumes the worst case scenario, which consumes more power.\n\nSigned-off-by: MyungJoo Ham \u003cmyungjoo.ham@samsung.com\u003e\nSigned-off-by: Kyungmin Park \u003ckyungmin.park@samsung.com\u003e\n\n---\nChanges from v1\n- Support 4212 and 4412 as well as 4210.\n"
    },
    {
      "commit": "6c81f90588972b8631bda4d538ffd0199a3e1b41",
      "tree": "ccf3fb4b293ac0416423566f07812050220388f6",
      "parents": [
        "9f3bdd4f937a75c4589a867dc1f8fefe09c1a618"
      ],
      "author": {
        "name": "MyungJoo Ham",
        "email": "myungjoo.ham@samsung.com",
        "time": "Mon Nov 14 23:31:35 2011 +0100"
      },
      "committer": {
        "name": "Rafael J. Wysocki",
        "email": "rjw@sisk.pl",
        "time": "Mon Nov 14 23:31:35 2011 +0100"
      },
      "message": "PM / devfreq: correct Kconfig dependency\n\nDevfreq does not depend on OPP. The dependency is removed.\n\nSigned-off-by: MyungJoo Ham \u003cmyungjoo.ham@samsung.com\u003e\nSigned-off-by: Kyungmin Park \u003ckyungmin.park@samsung.com\u003e\nSigned-off-by: Rafael J. Wysocki \u003crjw@sisk.pl\u003e\n"
    },
    {
      "commit": "ce26c5bb9569d8b826f01b8620fc16d8da6821e9",
      "tree": "3960fee73ec26f939295c92a231a09abcb4c816e",
      "parents": [
        "9005b65099ee4f14b6be691c4574612fe947531a"
      ],
      "author": {
        "name": "MyungJoo Ham",
        "email": "myungjoo.ham@samsung.com",
        "time": "Sun Oct 02 00:19:34 2011 +0200"
      },
      "committer": {
        "name": "Rafael J. Wysocki",
        "email": "rjw@sisk.pl",
        "time": "Sun Oct 02 00:19:34 2011 +0200"
      },
      "message": "PM / devfreq: Add basic governors\n\nFour cpufreq-like governors are provided as examples.\n\npowersave: use the lowest frequency possible. The user (device) should\nset the polling_ms as 0 because polling is useless for this governor.\n\nperformance: use the highest freqeuncy possible. The user (device)\nshould set the polling_ms as 0 because polling is useless for this\ngovernor.\n\nuserspace: use the user specified frequency stored at\ndevfreq.user_set_freq. With sysfs support in the following patch, a user\nmay set the value with the sysfs interface.\n\nsimple_ondemand: simplified version of cpufreq\u0027s ondemand governor.\n\nWhen a user updates OPP entries (enable/disable/add), OPP framework\nautomatically notifies devfreq to update operating frequency\naccordingly. Thus, devfreq users (device drivers) do not need to update\ndevfreq manually with OPP entry updates or set polling_ms for powersave\n, performance, userspace, or any other \"static\" governors.\n\nNote that these are given only as basic examples for governors and any\ndevices with devfreq may implement their own governors with the drivers\nand use them.\n\nSigned-off-by: MyungJoo Ham \u003cmyungjoo.ham@samsung.com\u003e\nSigned-off-by: Kyungmin Park \u003ckyungmin.park@samsung.com\u003e\nReviewed-by: Mike Turquette \u003cmturquette@ti.com\u003e\nAcked-by: Kevin Hilman \u003ckhilman@ti.com\u003e\nSigned-off-by: Rafael J. Wysocki \u003crjw@sisk.pl\u003e\n"
    },
    {
      "commit": "a3c98b8b2ede1f4230f49f9af7135cd902e71e83",
      "tree": "7016d0409796b8bbe7443b18addd93eaba869d68",
      "parents": [
        "03ca370fbf7b76d6d002380dbdc2cdc2319f9c80"
      ],
      "author": {
        "name": "MyungJoo Ham",
        "email": "myungjoo.ham@samsung.com",
        "time": "Sun Oct 02 00:19:15 2011 +0200"
      },
      "committer": {
        "name": "Rafael J. Wysocki",
        "email": "rjw@sisk.pl",
        "time": "Sun Oct 02 00:19:15 2011 +0200"
      },
      "message": "PM: Introduce devfreq: generic DVFS framework with device-specific OPPs\n\nWith OPPs, a device may have multiple operable frequency and voltage\nsets. However, there can be multiple possible operable sets and a system\nwill need to choose one from them. In order to reduce the power\nconsumption (by reducing frequency and voltage) without affecting the\nperformance too much, a Dynamic Voltage and Frequency Scaling (DVFS)\nscheme may be used.\n\nThis patch introduces the DVFS capability to non-CPU devices with OPPs.\nDVFS is a techique whereby the frequency and supplied voltage of a\ndevice is adjusted on-the-fly. DVFS usually sets the frequency as low\nas possible with given conditions (such as QoS assurance) and adjusts\nvoltage according to the chosen frequency in order to reduce power\nconsumption and heat dissipation.\n\nThe generic DVFS for devices, devfreq, may appear quite similar with\n/drivers/cpufreq.  However, cpufreq does not allow to have multiple\ndevices registered and is not suitable to have multiple heterogenous\ndevices with different (but simple) governors.\n\nNormally, DVFS mechanism controls frequency based on the demand for\nthe device, and then, chooses voltage based on the chosen frequency.\ndevfreq also controls the frequency based on the governor\u0027s frequency\nrecommendation and let OPP pick up the pair of frequency and voltage\nbased on the recommended frequency. Then, the chosen OPP is passed to\ndevice driver\u0027s \"target\" callback.\n\nWhen PM QoS is going to be used with the devfreq device, the device\ndriver should enable OPPs that are appropriate with the current PM QoS\nrequests. In order to do so, the device driver may call opp_enable and\nopp_disable at the notifier callback of PM QoS so that PM QoS\u0027s\nupdate_target() call enables the appropriate OPPs. Note that at least\none of OPPs should be enabled at any time; be careful when there is a\ntransition.\n\nSigned-off-by: MyungJoo Ham \u003cmyungjoo.ham@samsung.com\u003e\nSigned-off-by: Kyungmin Park \u003ckyungmin.park@samsung.com\u003e\nReviewed-by: Mike Turquette \u003cmturquette@ti.com\u003e\nAcked-by: Kevin Hilman \u003ckhilman@ti.com\u003e\nSigned-off-by: Rafael J. Wysocki \u003crjw@sisk.pl\u003e\n"
    }
  ]
}