Eric Lee / smarc-fsl-linux-kernel

13 Jul, 2007

1 commit

  • 702ed6ef3   Merge master.kernel.org:/pub/scm/linux/kernel/git/davej/cpufreq ... Browse Code »

    * master.kernel.org:/pub/scm/linux/kernel/git/davej/cpufreq:
    [CPUFREQ] Fix sysfs_create_file return value handling
    [CPUFREQ] ondemand: fix tickless accounting and software coordination bug
    [CPUFREQ] ondemand: add a check to avoid negative load calculation
    [CPUFREQ] Keep userspace governor quiet when it is not being used
    [CPUFREQ] Longhaul - Proper register access
    [CPUFREQ] Kconfig powernow-k8 driver should depend on ACPI P-States driver
    [CPUFREQ] Longhaul - Replace ACPI functions with direct I/O
    [CPUFREQ] Longhaul - Remove duplicate multipliers
    [CPUFREQ] Longhaul - Embedded "conservative"
    [CPUFREQ] acpi-cpufreq: Proper ReadModifyWrite of PERF_CTL MSR
    [CPUFREQ] check return value of sysfs_create_file
    [CPUFREQ] Longhaul - Check ACPI "BM DMA in progress" bit
    [CPUFREQ] Longhaul - Move old_ratio to correct place
    [CPUFREQ] Longhaul - VT8237 support
    [CPUFREQ] Longhaul - Use all kinds of support
    [CPUFREQ] powernow-k8: clarify number of cores.

    Linus Torvalds
     

12 Jul, 2007

1 commit

  • 7b595756e   sysfs: kill unnecessary attribute->owner ... Browse Code »

    sysfs is now completely out of driver/module lifetime game. After
    deletion, a sysfs node doesn't access anything outside sysfs proper,
    so there's no reason to hold onto the attribute owners. Note that
    often the wrong modules were accounted for as owners leading to
    accessing removed modules.

    This patch kills now unnecessary attribute->owner. Note that with
    this change, userland holding a sysfs node does not prevent the
    backing module from being unloaded.

    For more info regarding lifetime rule cleanup, please read the
    following message.

    http://article.gmane.org/gmane.linux.kernel/510293

    (tweaked by Greg to not delete the field just yet, to make it easier to
    merge things properly.)

    Signed-off-by: Tejun Heo
    Cc: Cornelia Huck
    Cc: Andrew Morton
    Signed-off-by: Greg Kroah-Hartman

    Tejun Heo
     

22 Jun, 2007

1 commit

11 Feb, 2007

1 commit

  • c12006977   [CPUFREQ] Remove hotplug cpu crap ... Browse Code »

    The hotplug CPU locking in cpufreq is horrendous. No-one seems to care
    enough to fix it, so just remove it so that the 99.9% of the real world
    users of this code can use cpufreq without being bothered by warnings.

    Signed-off-by: Andrew Morton
    Signed-off-by: Dave Jones

    Dave Jones
     

21 Oct, 2006

1 commit

26 Jul, 2006

1 commit

  • 153d7f3fc   [PATCH] Reorganize the cpufreq cpu hotplug locking to not be totally bizare ... Browse Code »

    The patch below moves the cpu hotplugging higher up in the cpufreq
    layering; this is needed to avoid recursive taking of the cpu hotplug
    lock and to otherwise detangle the mess.

    The new rules are:
    1. you must do lock_cpu_hotplug() around the following functions:
    __cpufreq_driver_target
    __cpufreq_governor (for CPUFREQ_GOV_LIMITS operation only)
    __cpufreq_set_policy
    2. governer methods (.governer) must NOT take the lock_cpu_hotplug()
    lock in any way; they are called with the lock taken already
    3. if your governer spawns a thread that does things, like calling
    __cpufreq_driver_target, your thread must honor rule #1.
    4. the policy lock and other cpufreq internal locks nest within
    the lock_cpu_hotplug() lock.

    I'm not entirely happy about how the __cpufreq_governor rule ended up
    (conditional locking rule depending on the argument) but basically all
    callers pass this as a constant so it's not too horrible.

    The patch also removes the cpufreq_governor() function since during the
    locking audit it turned out to be entirely unused (so no need to fix it)

    The patch works on my testbox, but it could use more testing
    (otoh... it can't be much worse than the current code)

    Signed-off-by: Arjan van de Ven
    Signed-off-by: Linus Torvalds

    Arjan van de Ven
     

01 Jul, 2006

1 commit

28 Feb, 2006

1 commit

28 Jan, 2006

1 commit

  • c06728601   [CPUFREQ] Get rid of userspace policy struct, make userspace gov _PPC safe. ... Browse Code »

    Userspace governor need not to hold it's own cpufreq_policy,
    better make use of the global core policy.
    Also fixes a bug in case of frequency changes via _PPC.
    Old min/max values have wrongly been passed to __cpufreq_driver_target()
    (kind of buffered) and when max freq was available again, only the old
    max(normally lowest freq) was still active.

    Signed-off-by: Thomas Renninger
    Signed-off-by: Venkatesh Pallipadi
    Signed-off-by: Dave Jones

    cpufreq_userspace.c | 53 +++++++++++++++++++++++++++-------------------------
    1 files changed, 28 insertions(+), 25 deletions(-)

    Thomas Renninger
     

19 Jan, 2006

1 commit

17 Apr, 2005

1 commit

  • 1da177e4c   Linux-2.6.12-rc2 ... Browse Code »

    Initial git repository build. I'm not bothering with the full history,
    even though we have it. We can create a separate "historical" git
    archive of that later if we want to, and in the meantime it's about
    3.2GB when imported into git - space that would just make the early
    git days unnecessarily complicated, when we don't have a lot of good
    infrastructure for it.

    Let it rip!

    Linus Torvalds