16 Dec, 2009

1 commit


09 Sep, 2009

1 commit

  • With the reordered init order, the rtc device is not registered until
    later, while sh_rtc_irq_set_freq() was attempting to assign ->irq_freq
    directly, resulting in an oops. This is handled by the upper layers for
    us, so just kill off the problematic dereference completely.

    Reported-by: Guennadi Liakhovetski
    Signed-off-by: Paul Mundt

    Paul Mundt
     

20 Aug, 2009

1 commit

  • - simplifies irq set freq
    - ioctl() was duplicating functionalities of rtc-dev core
    - corrected initialization sequence
    - use platform_driver_probe

    Signed-off-by: Alessandro Zummo
    Cc: Angelo Castello
    Cc: Giuseppe Cavallaro
    Cc: Kay Sievers
    Cc: Jamie Lenehan
    Signed-off-by: Paul Mundt

    Alessandro Zummo
     

16 Apr, 2009

1 commit


02 Apr, 2009

1 commit

  • Modify the sh_rtc driver to use set_irq_wake() during suspend
    and resume. These functions are used to enable the rtc interrupts
    in the interrupt controller so the rtc can be used to wakeup the
    system from suspend.

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

    Magnus Damm
     

20 Mar, 2009

3 commits

  • Flag that the SuperH RTC supports wakeup.

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

    Magnus Damm
     
  • This patch modifies invalid time handling in the
    SuperH RTC driver. Instead of zeroing the returned
    value at read-out time we just return an error code
    and reset invalid values during probe.

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

    Magnus Damm
     
  • This patch modifies the SuperH RTC driver to only
    enable carry interrupts when needed. So by default
    no interrupts are enabled with this patch. Without
    this patch a suspending system will most likely
    wake up by the carry interrupt regardless if the
    alarm interrupt has been enabled or not.

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

    Magnus Damm
     

06 Mar, 2009

1 commit


27 Feb, 2009

1 commit

  • Add support for single IRQ hardware to the sh-rtc driver.

    This is useful for processors with limited interrupt masking
    support such as sh7750 and sh7780. With this patch in place we
    can add logic to the intc code that merges all RTC vectors into
    a single linux interrupt with proper masking/unmasking support.

    Specify a single IRQ in the platform data to use this new shared
    IRQ feature. Separate Periodic/Carry/Alarm IRQs are still supported.

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

    Magnus Damm
     

07 Jan, 2009

2 commits

  • Move the power of 2 check on frequencies down into individual rtc drivers

    This is to allow for non power of 2 real time clock periodic interrupts
    such as those on the pxa27x to be found in the new pxa27x-rtc driver

    Signed-off-by: Jonathan Cameron
    Signed-off-by: Alessandro Zummo
    Cc: David Brownell
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Jonathan Cameron
     
  • This patch fixes a bunch of irq checking misuses. Most drivers were
    getting irq via platform_get_irq(), which returns -ENXIO or r->start.

    rtc-cmos.c is special. It is using PNP and platform bindings. Hopefully
    nobody is using PNP IRQ 0 for RTC. So the changes should be safe.

    rtc-sh.c is using platform_get_irq, but was storing a result into an
    unsigned type, then was checking for < 0. This is fixed now.

    Signed-off-by: Anton Vorontsov
    Cc: Alessandro Zummo
    Acked-by: David Brownell
    Acked-by: Paul Mundt
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Anton Vorontsov
     

21 Oct, 2008

1 commit

  • * git://git.kernel.org/pub/scm/linux/kernel/git/lethal/sh-2.6: (112 commits)
    sh: Move SH-4 CPU headers down one more level.
    sh: Only build in gpio.o when CONFIG_GENERIC_GPIO is selected.
    sh: Migrate common board headers to mach-common/.
    sh: Move the CPU definition headers from asm/ to cpu/.
    serial: sh-sci: Add support SCIF of SH7723
    video: add sh_mobile_lcdc platform flags
    video: remove unused sh_mobile_lcdc platform data
    sh: remove consistent alloc cruft
    sh: add dynamic crash base address support
    sh: reduce Migo-R smc91x overruns
    sh: Fix up some merge damage.
    Fix debugfs_create_file's error checking method for arch/sh/mm/
    Fix debugfs_create_dir's error checking method for arch/sh/kernel/
    sh: ap325rxa: Add support RTC RX-8564LC in AP325RXA board
    sh: Use sh7720 GPIO on magicpanelr2 board
    sh: Add sh7720 pinmux code
    sh: Use sh7203 GPIO on rsk7203 board
    sh: Add sh7203 pinmux code
    sh: Use sh7723 GPIO on AP325RXA board
    sh: Add sh7723 pinmux code
    ...

    Linus Torvalds
     

20 Oct, 2008

2 commits


17 Oct, 2008

1 commit

  • Make the rtc framework consistent about disabling 1/second update IRQs
    that may have been activated through the /dev interface, when that /dev
    file is closed. (It may have closed because of coredump, etc.) This was
    previously done only for emulated update IRQs ... now, do it always.

    Also comment the current policy: repeating IRQs (periodic, update) that
    userspace enabled will be cleanly disabled, but alarms are left alone.
    Such repeating IRQs are a constant and pointless system load.

    Update some RTC drivers to remove now-needless release() methods. Most
    such methods just enforce that policy. The others all seem to be buggy,
    and mistreat in-kernel clients of periodic or alarm IRQs.

    Signed-off-by: David Brownell
    Acked-by: Andrew Sharp
    Cc: Angelo Castello
    Acked-by: Atsushi Nemoto
    Acked-by: Paul Mundt
    Cc: Thomas Hommel
    Acked-by: Alessandro Zummo
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    David Brownell
     

11 Sep, 2008

1 commit


08 May, 2008

1 commit


28 Apr, 2008

1 commit


19 Apr, 2008

1 commit


11 Apr, 2008

1 commit

  • Since 43cc71eed1250755986da4c0f9898f9a635cb3bf, the platform modalias is
    prefixed with "platform:". Add MODULE_ALIAS() to the hotpluggable RTC
    platform drivers, to re-enable module auto loading.

    [dbrownell@users.sourceforge.net: more drivers, minor fix]
    Signed-off-by: Kay Sievers
    Signed-off-by: David Brownell
    Cc: Greg KH
    Cc: Alessandro Zummo
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Kay Sievers
     

28 Jan, 2008

3 commits


07 Nov, 2007

2 commits


21 Sep, 2007

1 commit

  • All SH-4 parts have a 4-digit year, while the SH-3 parts typically
    only use a 2-digit one. The SH7705, SH7710, and SH7712 SH-3 parts
    however opted to extend it to 4-digit and still look and act like
    an SH-3 RTC in all other ways.

    This adds a capability flag (RTC_CAP_4_DIGIT_YEAR) that these
    corner-case CPU subtypes can set in their platform data and cleans
    up some of the ifdef mess in the driver as a result.

    Reported-by: Markus Brunner
    Signed-off-by: Paul Mundt

    Paul Mundt
     

26 Jul, 2007

1 commit


09 May, 2007

3 commits


23 Jan, 2007

1 commit


12 Jan, 2007

1 commit


12 Dec, 2006

3 commits

  • This adds alarm support for the RTC_ALM_SET, RTC_ALM_READ,
    RTC_WKALM_SET and RTC_WKALM_RD operations to rtc-sh.

    The only unusual part is the handling of the alarm interrupt. If you
    clear the alarm flag (AF) while the time in the RTC still matches the
    time in the alarm registers than AF is immediately re-set, and if the
    alarm interrupt (AIE) is still enabled then it re-triggers. I was
    originally getting around 20k+ interrupts generated during the second
    when the RTC and alarm registers matches.

    The solution I've used is to clear AIE when the alarm goes off and
    then use the carry interrupt to re-enabled it. The carry interrupt
    will check AF and re-enabled AIE if it's clear. If AF is not clear
    it'll clear it and then the check will be repeated next carry
    interrupt. This a bit in rtc structure that indicates that it's
    waiting to have AIE re-enabled so it doesn't turn it on when it
    wasn't enabled anyway.

    Signed-off-by: Jamie Lenehan
    Signed-off-by: Paul Mundt

    Jamie Lenehan
     
  • The RMONCNT register, which holds the month in the RTC, takes a value
    between 1 and 12 while the tm_mon field in the time structures takes
    a value between 0 and 11. This wasn't being taken into account in
    rtc-sh resulting in the month being out by one.

    eg, on my board during boot the RTC is set to:

    RTC is set to Thu Jul 01 09:00:00 1999

    but "hwclock -r" immediately after logging in was showing:

    Sun Aug 1 09:01:43 1999 0.000000 seconds

    Signed-off-by: Jamie Lenehan
    Signed-off-by: Paul Mundt

    Jamie Lenehan
     
  • When testing the per second interrupt support (RTC_UIE_ON/RTC_UIE_OFF)
    of the new RTC system it would die in sh_rtc_interrupt due to a null
    ptr dereference. The following gets it working correctly.

    Signed-off-by: Jamie Lenehan
    Signed-off-by: Paul Mundt

    Jamie Lenehan
     

06 Oct, 2006

1 commit


05 Oct, 2006

1 commit

  • Maintain a per-CPU global "struct pt_regs *" variable which can be used instead
    of passing regs around manually through all ~1800 interrupt handlers in the
    Linux kernel.

    The regs pointer is used in few places, but it potentially costs both stack
    space and code to pass it around. On the FRV arch, removing the regs parameter
    from all the genirq function results in a 20% speed up of the IRQ exit path
    (ie: from leaving timer_interrupt() to leaving do_IRQ()).

    Where appropriate, an arch may override the generic storage facility and do
    something different with the variable. On FRV, for instance, the address is
    maintained in GR28 at all times inside the kernel as part of general exception
    handling.

    Having looked over the code, it appears that the parameter may be handed down
    through up to twenty or so layers of functions. Consider a USB character
    device attached to a USB hub, attached to a USB controller that posts its
    interrupts through a cascaded auxiliary interrupt controller. A character
    device driver may want to pass regs to the sysrq handler through the input
    layer which adds another few layers of parameter passing.

    I've build this code with allyesconfig for x86_64 and i386. I've runtested the
    main part of the code on FRV and i386, though I can't test most of the drivers.
    I've also done partial conversion for powerpc and MIPS - these at least compile
    with minimal configurations.

    This will affect all archs. Mostly the changes should be relatively easy.
    Take do_IRQ(), store the regs pointer at the beginning, saving the old one:

    struct pt_regs *old_regs = set_irq_regs(regs);

    And put the old one back at the end:

    set_irq_regs(old_regs);

    Don't pass regs through to generic_handle_irq() or __do_IRQ().

    In timer_interrupt(), this sort of change will be necessary:

    - update_process_times(user_mode(regs));
    - profile_tick(CPU_PROFILING, regs);
    + update_process_times(user_mode(get_irq_regs()));
    + profile_tick(CPU_PROFILING);

    I'd like to move update_process_times()'s use of get_irq_regs() into itself,
    except that i386, alone of the archs, uses something other than user_mode().

    Some notes on the interrupt handling in the drivers:

    (*) input_dev() is now gone entirely. The regs pointer is no longer stored in
    the input_dev struct.

    (*) finish_unlinks() in drivers/usb/host/ohci-q.c needs checking. It does
    something different depending on whether it's been supplied with a regs
    pointer or not.

    (*) Various IRQ handler function pointers have been moved to type
    irq_handler_t.

    Signed-Off-By: David Howells
    (cherry picked from 1b16e7ac850969f38b375e511e3fa2f474a33867 commit)

    David Howells
     

27 Sep, 2006

1 commit