15 Dec, 2014

1 commit

  • Pull driver core update from Greg KH:
    "Here's the set of driver core patches for 3.19-rc1.

    They are dominated by the removal of the .owner field in platform
    drivers. They touch a lot of files, but they are "simple" changes,
    just removing a line in a structure.

    Other than that, a few minor driver core and debugfs changes. There
    are some ath9k patches coming in through this tree that have been
    acked by the wireless maintainers as they relied on the debugfs
    changes.

    Everything has been in linux-next for a while"

    * tag 'driver-core-3.19-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core: (324 commits)
    Revert "ath: ath9k: use debugfs_create_devm_seqfile() helper for seq_file entries"
    fs: debugfs: add forward declaration for struct device type
    firmware class: Deletion of an unnecessary check before the function call "vunmap"
    firmware loader: fix hung task warning dump
    devcoredump: provide a one-way disable function
    device: Add dev__once variants
    ath: ath9k: use debugfs_create_devm_seqfile() helper for seq_file entries
    ath: use seq_file api for ath9k debugfs files
    debugfs: add helper function to create device related seq_file
    drivers/base: cacheinfo: remove noisy error boot message
    Revert "core: platform: add warning if driver has no owner"
    drivers: base: support cpu cache information interface to userspace via sysfs
    drivers: base: add cpu_device_create to support per-cpu devices
    topology: replace custom attribute macros with standard DEVICE_ATTR*
    cpumask: factor out show_cpumap into separate helper function
    driver core: Fix unbalanced device reference in drivers_probe
    driver core: fix race with userland in device_add()
    sysfs/kernfs: make read requests on pre-alloc files use the buffer.
    sysfs/kernfs: allow attributes to request write buffer be pre-allocated.
    fs: sysfs: return EGBIG on write if offset is larger than file size
    ...

    Linus Torvalds
     

13 Nov, 2014

1 commit

  • The only place where the time is invalid is when the ACPI_CSTATE_FFH entry
    method is not set. Otherwise for all the drivers, the time can be correctly
    measured.

    Instead of duplicating the CPUIDLE_FLAG_TIME_VALID flag in all the drivers
    for all the states, just invert the logic by replacing it by the flag
    CPUIDLE_FLAG_TIME_INVALID, hence we can set this flag only for the acpi idle
    driver, remove the former flag from all the drivers and invert the logic with
    this flag in the different governor.

    Signed-off-by: Daniel Lezcano
    Signed-off-by: Rafael J. Wysocki

    Daniel Lezcano
     

20 Oct, 2014

1 commit


30 Dec, 2013

1 commit

  • Commit 60a66e370007e8535b7a561353b07b37deaf35ba changed the Calxeda
    cpuidle driver to a platform driver, copying the __init tag from the
    _init() to the newly used _probe() function. However, "probe should
    not be __init." (Rob said ;-)
    Remove the __init tag to fix a section mismatch in the Calxeda
    cpuidle driver.

    Signed-off-by: Andre Przywara
    Signed-off-by: Daniel Lezcano

    Andre Przywara
     

02 Oct, 2013

3 commits


12 Aug, 2013

1 commit

  • Added missing __iomem annotation in order to fix the following
    sparse warnings:

    drivers/cpuidle/cpuidle-calxeda.c:44:24: warning: incorrect type in argument 1 (different address spaces)
    drivers/cpuidle/cpuidle-calxeda.c:44:24: expected void [noderef] *
    drivers/cpuidle/cpuidle-calxeda.c:44:24: got void *extern [addressable] [toplevel] scu_base_addr
    drivers/cpuidle/cpuidle-calxeda.c:56:24: warning: incorrect type in argument 1 (different address spaces)
    drivers/cpuidle/cpuidle-calxeda.c:56:24: expected void [noderef] *
    drivers/cpuidle/cpuidle-calxeda.c:56:24: got void *extern [addressable] [toplevel] scu_base_addr

    Signed-off-by: Jingoo Han
    Signed-off-by: Daniel Lezcano

    Jingoo Han
     

30 May, 2013

1 commit


27 Apr, 2013

1 commit

  • Currently cpuidle drivers are spread across different archs.

    As a result, there are several different paths for cpuidle patch
    submissions: cpuidle core changes go through linux-pm, ARM driver
    changes go to the arm-soc or SoC-specific trees, sh changes go
    through the sh arch tree, pseries changes go through the PowerPC tree
    and finally intel changes go through the Len's tree while ACPI idle
    changes go through linux-pm.

    That makes it difficult to consolidate code and to propagate
    modifications from the cpuidle core to the different drivers.

    Hopefully, a movement has started to put the majority of cpuidle
    drivers under drivers/cpuidle like cpuidle-calxeda.c and
    cpuidle-kirkwood.c.

    Add a maintainer entry for cpuidle to MAINTAINERS to clarify the
    situation and to indicate to new cpuidle driver authors that those
    drivers should not go into arch-specific directories.

    The upstreaming process is unchanged: Rafael takes patches for
    merging into his tree, but with an Acked-by: tag from the driver's
    maintainer, so indicate in the drivers' headers who maintains them.

    The arrangement will be the same as for cpufreq.

    [rjw: Changelog]
    Signed-off-by: Daniel Lezcano
    Acked-by: Linus Walleij
    Acked-by: Andrew Lunn #for kirkwood
    Acked-by: Jason Cooper #for kirkwood
    Acked-by: Kevin Hilman
    Signed-off-by: Rafael J. Wysocki

    Daniel Lezcano
     

23 Apr, 2013

2 commits


08 Nov, 2012

1 commit