18 Jun, 2013

1 commit


22 May, 2013

1 commit

  • on i386:
    CONFIG_ACPI_PROCESSOR=m
    CONFIG_X86_E_POWERSAVER=y

    drivers/built-in.o: In function `eps_cpu_init.part.8':
    e_powersaver.c:(.text.unlikely+0x2243): undefined reference to `acpi_processor_register_performance'
    e_powersaver.c:(.text.unlikely+0x22a2): undefined reference to `acpi_processor_unregister_performance'
    e_powersaver.c:(.text.unlikely+0x246b): undefined reference to `acpi_processor_get_bios_limit'

    X86_E_POWERSAVER should also depend on ACPI_PROCESSOR.

    Signed-off-by: Rafal Bilski
    Acked-by: Viresh Kumar
    Signed-off-by: Rafael J. Wysocki

    Rafał Bilski
     

10 Apr, 2013

1 commit

  • Future AMD processors, starting with Family 16h, can provide software
    with feedback on how the workload may respond to frequency change --
    memory-bound workloads will not benefit from higher frequency, where
    as compute-bound workloads will. This patch enables this "frequency
    sensitivity feedback" to aid the ondemand governor to make better
    frequency change decisions by hooking into the powersave bias.

    Signed-off-by: Jacob Shin
    Acked-by: Thomas Renninger
    Acked-by: Borislav Petkov
    Acked-by: Viresh Kumar
    Signed-off-by: Rafael J. Wysocki

    Jacob Shin
     

22 Feb, 2013

1 commit

  • Pull driver core patches from Greg Kroah-Hartman:
    "Here is the big driver core merge for 3.9-rc1

    There are two major series here, both of which touch lots of drivers
    all over the kernel, and will cause you some merge conflicts:

    - add a new function called devm_ioremap_resource() to properly be
    able to check return values.

    - remove CONFIG_EXPERIMENTAL

    Other than those patches, there's not much here, some minor fixes and
    updates"

    Fix up trivial conflicts

    * tag 'driver-core-3.9-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core: (221 commits)
    base: memory: fix soft/hard_offline_page permissions
    drivercore: Fix ordering between deferred_probe and exiting initcalls
    backlight: fix class_find_device() arguments
    TTY: mark tty_get_device call with the proper const values
    driver-core: constify data for class_find_device()
    firmware: Ignore abort check when no user-helper is used
    firmware: Reduce ifdef CONFIG_FW_LOADER_USER_HELPER
    firmware: Make user-mode helper optional
    firmware: Refactoring for splitting user-mode helper code
    Driver core: treat unregistered bus_types as having no devices
    watchdog: Convert to devm_ioremap_resource()
    thermal: Convert to devm_ioremap_resource()
    spi: Convert to devm_ioremap_resource()
    power: Convert to devm_ioremap_resource()
    mtd: Convert to devm_ioremap_resource()
    mmc: Convert to devm_ioremap_resource()
    mfd: Convert to devm_ioremap_resource()
    media: Convert to devm_ioremap_resource()
    iommu: Convert to devm_ioremap_resource()
    drm: Convert to devm_ioremap_resource()
    ...

    Linus Torvalds
     

16 Feb, 2013

1 commit

  • Load order is important in order for intel_pstate to take over as the
    default scaling driver from acpi-cpufreq.

    If both are built-in, acpi-cpufreq uses late_initcall() and
    intel_pstate uses device_initcall() so it will be able to register as
    the scaling before acpi-cpufreq for the processors supported by
    intel_pstate.

    If acpi-cpufreq is built as a module then intel_pstate still gets
    first option to become the scaling driver.

    Signed-off-by: Dirk Brandewie
    Acked-by: Viresh Kumar
    Signed-off-by: Rafael J. Wysocki

    Dirk Brandewie
     

09 Feb, 2013

1 commit

  • Add a P-state driver for the Intel Sandy bridge processor. In cpufreq
    terminology this driver implements a scaling driver with an internal
    governor.

    When built into the the kernel this driver will be the preferred
    scaling driver for Sandy bridge processors.

    In addition to the interfaces provided by the cpufreq subsystem for
    controlling scaling drivers. The user may control the behavior of the
    driver via three sysfs files located in
    "/sys/devices/system/cpu/intel_pstate".

    max_perf_pct: limits the maximum P state that will be requested by
    the driver stated as a percentage of the avail performance.

    min_perf_pct: limits the minimum P state that will be requested by
    the driver stated as a percentage of the avail performance.

    no_turbo: limits the driver to selecting P states below the turbo
    frequency range.

    Signed-off-by: Dirk Brandewie
    Acked-by: Viresh Kumar
    Signed-off-by: Rafael J. Wysocki

    Dirk Brandewie
     

26 Jan, 2013

1 commit


18 Jan, 2013

1 commit

  • Andreas reports in https://bugzilla.kernel.org/show_bug.cgi?id=51741
    that with his Gentoo config, acpi-cpufreq wasn't enabled and
    powernow-k8 couldn't handoff properly to acpi-cpufreq leading to
    running without P-state support (i.e., cores are constantly in P0).

    To alleaviate that, we need to make powernow-k8 depend on acpi-cpufreq
    so that acpi-cpufreq is always present.

    References: https://bugzilla.kernel.org/show_bug.cgi?id=51741
    Reported-by: Andreas
    Signed-off-by: Borislav Petkov
    Cc: 3.7+
    Signed-off-by: Rafael J. Wysocki

    Borislav Petkov
     

12 Jan, 2013

1 commit


10 Sep, 2012

3 commits

  • The powernow-k8 driver supported a sysfs knob called "cpb", which was
    instantiated per CPU, but actually acted globally for the whole
    system. To keep some compatibility with this feature, we re-introduce
    this behavior here, but:
    a) only enable it on AMD CPUs and
    b) protect it with a Kconfig switch

    I'd like to consider this feature obsolete. Lets keep it around for
    some kernel versions and then phase it out.

    Signed-off-by: Andre Przywara
    Signed-off-by: Rafael J. Wysocki

    Andre Przywara
     
  • cpufreq modules are often loaded from init scripts that assume that
    all recent AMD systems will use powernow-k8.
    To inform the user of the change of support and ease the transition
    to acpi-cpufreq, emit a warning message.

    Signed-off-by: Andre Przywara
    Signed-off-by: Rafael J. Wysocki

    Andre Przywara
     
  • The programming model for P-states on modern AMD CPUs is very similar to
    that of Intel and VIA. It makes sense to consolidate this support into one
    driver rather than duplicating functionality between two of them. This
    patch adds support for AMDs with hardware P-state control to acpi-cpufreq.

    Signed-off-by: Matthew Garrett
    Signed-off-by: Andre Przywara
    Signed-off-by: Rafael J. Wysocki

    Matthew Garrett
     

20 May, 2011

2 commits

  • * 'x86-cpu-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/linux-2.6-tip:
    x86, cpu: Fix detection of Celeron Covington stepping A1 and B0
    Documentation, ABI: Update L3 cache index disable text
    x86, AMD, cacheinfo: Fix L3 cache index disable checks
    x86, AMD, cacheinfo: Fix fallout caused by max3 conversion
    x86, cpu: Change NOP selection for certain Intel CPUs
    x86, cpu: Clean up and unify the NOP selection infrastructure
    x86, percpu: Use ASM_NOP4 instead of hardcoding P6_NOP4
    x86, cpu: Move AMD Elan Kconfig under "Processor family"

    Fix up trivial conflicts in alternative handling (commit dc326fca2b64
    "x86, cpu: Clean up and unify the NOP selection infrastructure" removed
    some hacky 5-byte instruction stuff, while commit d430d3d7e646 "jump
    label: Introduce static_branch() interface" renamed HAVE_JUMP_LABEL to
    CONFIG_JUMP_LABEL in the code that went away)

    Linus Torvalds
     
  • Signed-off-by: Dave Jones

    Dave Jones