22 Aug, 2013

1 commit

  • Add support for CMT hardware with 32-bit control and counter
    registers, as found on r8a73a4 and r8a7790. To use the CMT
    with 32-bit hardware a second I/O memory resource needs to
    point out the CMSTR register and it needs to be 32 bit wide.

    Signed-off-by: Magnus Damm
    Reviewed-by: Daniel Lezcano
    Signed-off-by: Simon Horman

    Magnus Damm
     

13 Mar, 2013

9 commits


04 Jan, 2013

1 commit

  • CONFIG_HOTPLUG is going away as an option. As a result, the __dev*
    markings need to be removed.

    This change removes the use of __devinit, __devexit_p, __devinitdata,
    __devinitconst, and __devexit from these drivers.

    Based on patches originally written by Bill Pemberton, but redone by me
    in order to handle some of the coding style issues better, by hand.

    Cc: Bill Pemberton
    Cc: John Stultz
    Cc: Thomas Gleixner
    Signed-off-by: Greg Kroah-Hartman

    Greg Kroah-Hartman
     

04 Sep, 2012

4 commits

  • Modify the SH CMT clock source/clock event device driver to support
    runtime PM at a basic level (i.e. device clocks can be disabled and
    enabled, but domain power must be on, because the devices have to
    be marked as "irq safe").

    Signed-off-by: Rafael J. Wysocki
    Acked-by: Magnus Damm

    Rafael J. Wysocki
     
  • The syscore device PM flag is used to mark the devices (belonging to
    a PM domain) that should never be turned off, except for the system
    core (syscore) suspend/hibernation and resume stages. That flag is
    stored in the device's struct pm_subsys_data object whose address is
    available from struct device. However, in some situations it may be
    convenient to set that flag before the device is added to a PM
    domain, so it is better to move it directly to the "power" member of
    struct device. Then, it can be checked by the routines in
    drivers/base/power/runtime.c and drivers/base/power/main.c, which is
    more straightforward.

    This also reduces the number of dev_gpd_data() invocations in the
    generic PM domains framework, so the overhead related to the syscore
    flag is slightly smaller.

    Signed-off-by: Rafael J. Wysocki
    Acked-by: Magnus Damm

    Rafael J. Wysocki
     
  • The always_on device flag is used to mark the devices (belonging to
    a PM domain) that should never be turned off, except for the system
    core (syscore) suspend/hibernation and resume stages. Change name
    of that flag to "syscore" to better reflect its purpose.

    Signed-off-by: Rafael J. Wysocki
    Acked-by: Magnus Damm

    Rafael J. Wysocki
     
  • Introduce suspend/resume routines for SH CMT clock event devices and
    modify the suspend/resume routines for SH CMT clock sources such that
    if those devices belong to a PM domain, the generic PM domains
    framework will be notified that the given domain may be turned off
    (during system suspend) or that it has to be turned on (during system
    resume).

    Signed-off-by: Rafael J. Wysocki
    Acked-by: Magnus Damm

    Rafael J. Wysocki
     

11 Jun, 2012

1 commit


17 Mar, 2012

1 commit


01 Nov, 2011

1 commit


21 Jul, 2011

1 commit

  • Add code to the CMT driver to wait for CMCNT V2. This to let
    the register value settle before starting the timer channel.
    Makes the driver more robust.

    Needed for CMT2 on sh7372 and certain CMT channels on sh73a0.

    Signed-off-by: Magnus Damm
    Signed-off-by: Paul Mundt

    Magnus Damm
     

31 May, 2011

1 commit


23 May, 2011

2 commits

  • Add Runtime PM support to the CMT driver.

    The hardware device is enabled as long as the clocksource
    or the clockevent portion of the driver is used.

    Signed-off-by: Magnus Damm
    Acked-by: John Stultz
    Signed-off-by: Paul Mundt

    Magnus Damm
     
  • This patch updates the clocksource part of the CMT driver
    to make use of the __clocksource_updatefreq_hz() function.

    Without this patch the old code uses clocksource_register()
    together with a hack that assumes a never changing clock rate
    (see clk_enable(), clk_get_rate() and clk_disable()).

    The patch uses clocksource_register_hz() with 1 Hz as initial
    value, then lets the ->enable() callback update the value
    with __clocksource_updatefreq_hz() once the struct clk has
    been enabled and the frequency is stable.

    Signed-off-by: Magnus Damm
    Acked-by: John Stultz
    Signed-off-by: Paul Mundt

    Magnus Damm
     

17 Dec, 2010

1 commit

  • There are control flow that sh_cmt_set_next() does double
    spin-lock. The callers sh_cmt_{start,stop}() already have
    lock. But another callers sh_cmt_clock_event_{start,next}()
    does not.

    Now sh_cmt_set_next() does not lock by itself. All the
    callers should hold spin-lock before calling it.

    [damm@opensource.se: use __sh_cmt_set_next() to simplify code]
    [damm@opensource.se: added stable, suitable for v2.6.35 + v2.6.36]
    Cc: stable@kernel.org
    Signed-off-by: Takashi YOSHII
    Signed-off-by: Magnus Damm
    Signed-off-by: Paul Mundt

    Takashi YOSHII
     

31 Oct, 2010

1 commit


04 Aug, 2010

2 commits


22 Jun, 2010

1 commit


02 Jun, 2010

1 commit


26 Apr, 2010

1 commit


15 Apr, 2010

1 commit


30 Mar, 2010

1 commit

  • …it slab.h inclusion from percpu.h

    percpu.h is included by sched.h and module.h and thus ends up being
    included when building most .c files. percpu.h includes slab.h which
    in turn includes gfp.h making everything defined by the two files
    universally available and complicating inclusion dependencies.

    percpu.h -> slab.h dependency is about to be removed. Prepare for
    this change by updating users of gfp and slab facilities include those
    headers directly instead of assuming availability. As this conversion
    needs to touch large number of source files, the following script is
    used as the basis of conversion.

    http://userweb.kernel.org/~tj/misc/slabh-sweep.py

    The script does the followings.

    * Scan files for gfp and slab usages and update includes such that
    only the necessary includes are there. ie. if only gfp is used,
    gfp.h, if slab is used, slab.h.

    * When the script inserts a new include, it looks at the include
    blocks and try to put the new include such that its order conforms
    to its surrounding. It's put in the include block which contains
    core kernel includes, in the same order that the rest are ordered -
    alphabetical, Christmas tree, rev-Xmas-tree or at the end if there
    doesn't seem to be any matching order.

    * If the script can't find a place to put a new include (mostly
    because the file doesn't have fitting include block), it prints out
    an error message indicating which .h file needs to be added to the
    file.

    The conversion was done in the following steps.

    1. The initial automatic conversion of all .c files updated slightly
    over 4000 files, deleting around 700 includes and adding ~480 gfp.h
    and ~3000 slab.h inclusions. The script emitted errors for ~400
    files.

    2. Each error was manually checked. Some didn't need the inclusion,
    some needed manual addition while adding it to implementation .h or
    embedding .c file was more appropriate for others. This step added
    inclusions to around 150 files.

    3. The script was run again and the output was compared to the edits
    from #2 to make sure no file was left behind.

    4. Several build tests were done and a couple of problems were fixed.
    e.g. lib/decompress_*.c used malloc/free() wrappers around slab
    APIs requiring slab.h to be added manually.

    5. The script was run on all .h files but without automatically
    editing them as sprinkling gfp.h and slab.h inclusions around .h
    files could easily lead to inclusion dependency hell. Most gfp.h
    inclusion directives were ignored as stuff from gfp.h was usually
    wildly available and often used in preprocessor macros. Each
    slab.h inclusion directive was examined and added manually as
    necessary.

    6. percpu.h was updated not to include slab.h.

    7. Build test were done on the following configurations and failures
    were fixed. CONFIG_GCOV_KERNEL was turned off for all tests (as my
    distributed build env didn't work with gcov compiles) and a few
    more options had to be turned off depending on archs to make things
    build (like ipr on powerpc/64 which failed due to missing writeq).

    * x86 and x86_64 UP and SMP allmodconfig and a custom test config.
    * powerpc and powerpc64 SMP allmodconfig
    * sparc and sparc64 SMP allmodconfig
    * ia64 SMP allmodconfig
    * s390 SMP allmodconfig
    * alpha SMP allmodconfig
    * um on x86_64 SMP allmodconfig

    8. percpu.h modifications were reverted so that it could be applied as
    a separate patch and serve as bisection point.

    Given the fact that I had only a couple of failures from tests on step
    6, I'm fairly confident about the coverage of this conversion patch.
    If there is a breakage, it's likely to be something in one of the arch
    headers which should be easily discoverable easily on most builds of
    the specific arch.

    Signed-off-by: Tejun Heo <tj@kernel.org>
    Guess-its-ok-by: Christoph Lameter <cl@linux-foundation.org>
    Cc: Ingo Molnar <mingo@redhat.com>
    Cc: Lee Schermerhorn <Lee.Schermerhorn@hp.com>

    Tejun Heo
     

29 Mar, 2010

1 commit

  • We want to get rid of the clock string from platform data entirely,
    depending on the clkdev-based clock lookup to do the right thing for us
    instead.

    This converts all of the SH drivers to request their associated function
    clocks directly, and if there is no match for that then we fall back on
    the legacy lookup while warning about it. After all of the outstanding
    CPUs have been converted to clkdev lookups the clock string will be
    killed off completely.

    Signed-off-by: Paul Mundt

    Paul Mundt
     

10 Mar, 2010

1 commit


02 Mar, 2010

1 commit


25 Feb, 2010

1 commit

  • All of the SH clocksource drivers follow the scheme that the IRQ is setup
    prior to registering the clockevent. The interrupt handler in the
    clockevent cases looks to the event handler function pointer being filled
    in by the registration code, permitting us to get in to situations where
    asserted IRQs step in to the handler before registration has had a chance
    to complete and hitting a NULL pointer deref.

    In practice this is not an issue for most platforms, but some of them
    with fairly special loaders (or that are chain-loading from another
    kernel) may enter in to this situation. This fixes up the oops reported
    by Rafael on hp6xx.

    Reported-and-tested-by: Rafael Ignacio Zurita
    Cc: stable@kernel.org
    Signed-off-by: Paul Mundt

    Paul Mundt
     

05 Feb, 2010

1 commit

  • Add code to start the CMT timer on clocksource resume. While at it handle
    the suspend case as well. Remove the platform device specific suspend
    calls.

    This makes sure the timer is started during sysdev_resume(). Without this
    patch the clocksource may be read as suspended, this after sysdev resume
    but before platform device resume.

    Signed-off-by: Magnus Damm
    Cc: john stultz
    Cc: Paul Mundt
    Signed-off-by: Andrew Morton
    Signed-off-by: Thomas Gleixner

    Magnus Damm
     

15 Aug, 2009

1 commit

  • This patch updates the SuperH CMT driver with suspend and resume
    callbacks for the suspend-to-ram case. This patch stops the CMT
    channel at suspend time to avoid unwanted wake up events.

    Signed-off-by: Magnus Damm
    Signed-off-by: Paul Mundt

    Magnus Damm
     

17 Jun, 2009

1 commit

  • Modify the CMT and TMU drivers to disable interrupts when
    disabling the timer. Only using start/stop bits is not
    enough.

    This fixes a bootup hang on Migo-R when the CMT is replaced
    by TMU for clockevents but the CMT keeps on delivering irqs
    even though the timer start bit is off.

    Signed-off-by: Magnus Damm
    Signed-off-by: Paul Mundt

    Magnus Damm
     

14 Jun, 2009

1 commit


03 May, 2009

1 commit