1. 30 3月, 2015 2 次提交
  2. 12 2月, 2015 1 次提交
  3. 30 1月, 2015 2 次提交
    • C
      devfreq: Fix build break of devfreq-event class · e6ee3192
      Chanwoo Choi 提交于
      This patch fixes the build break of the exynos-ppmu driver because Makefile
      in drivers/devfreq don't include the entry of devfreq-event.c driver.
      
      The original patch[1] includes the entry to build devfreq-event.c without
      the build break. This build break is generated in the process of merging the
      patch.
      [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 governor
      
      CC      init/version.o
      LD      init/built-in.o
      drivers/built-in.o: In function `exynos_ppmu_probe':
      binder.c:(.text+0x4447ec): undefined reference to `devm_devfreq_event_add_edev'
      make: *** [vmlinux] Error 1
      
      Cc: Rafael J. Wysocki <rjw@rjwysocki.net>
      Cc: MyungJoo Ham <myungjoo.ham@samsung.com>
      Signed-off-by: NChanwoo Choi <cw00.choi@samsung.com>
      e6ee3192
    • C
      PM / devfreq: event: Add devfreq_event class · f262f28c
      Chanwoo Choi 提交于
      This patch adds a new class in devfreq, devfreq_event, which provides
      raw data (e.g., memory bus utilization, GPU utilization) for devfreq
      governors.
      
      - 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 frequency
      and 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 devfreq
      governor requires data that indicates the performance requirement given
      to the devfreq device. The conventional (previous) implementatino of
      devfreq subsystem requires a devfreq device driver to implement its own
      mechanism 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 by
      this patch) provides a template for device drivers representing
      performance monitoring unit, which gives the basic or raw data for
      preformance 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 governor
      
      Cc: MyungJoo Ham <myungjoo.ham@samsung.com>
      Cc: Kyungmin Park <kyungmin.park@samsung.com>
      Signed-off-by: NChanwoo Choi <cw00.choi@samsung.com>
      [Commit message rewritten & conflict resolved by MyungJoo]
      Signed-off-by: NMyungJoo Ham <myungjoo.ham@samsung.com>
      f262f28c
  4. 29 1月, 2015 1 次提交
  5. 07 1月, 2015 1 次提交
    • P
      rcu: Make SRCU optional by using CONFIG_SRCU · 83fe27ea
      Pranith Kumar 提交于
      SRCU is not necessary to be compiled by default in all cases. For tinification
      efforts not compiling SRCU unless necessary is desirable.
      
      The current patch tries to make compiling SRCU optional by introducing a new
      Kconfig option CONFIG_SRCU which is selected when any of the components making
      use of SRCU are selected.
      
      If we do not select CONFIG_SRCU, srcu.o will not be compiled at all.
      
         text    data     bss     dec     hex filename
         2007       0       0    2007     7d7 kernel/rcu/srcu.o
      
      Size of arch/powerpc/boot/zImage changes from
      
         text    data     bss     dec     hex filename
       831552   64180   23944  919676   e087c arch/powerpc/boot/zImage : before
       829504   64180   23952  917636   e0084 arch/powerpc/boot/zImage : after
      
      so the savings are about ~2000 bytes.
      Signed-off-by: NPranith Kumar <bobby.prani@gmail.com>
      CC: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
      CC: Josh Triplett <josh@joshtriplett.org>
      CC: Lai Jiangshan <laijs@cn.fujitsu.com>
      Signed-off-by: NPaul E. McKenney <paulmck@linux.vnet.ibm.com>
      [ paulmck: resolve conflict due to removal of arch/ia64/kvm/Kconfig. ]
      83fe27ea
  6. 20 10月, 2014 1 次提交
  7. 29 9月, 2014 3 次提交
  8. 23 7月, 2014 1 次提交
  9. 24 5月, 2014 15 次提交
  10. 21 3月, 2014 1 次提交
  11. 28 1月, 2014 1 次提交
  12. 19 12月, 2013 3 次提交
  13. 02 12月, 2013 1 次提交
  14. 28 10月, 2013 5 次提交
  15. 26 10月, 2013 2 次提交