1. 11 Sep, 2018 1 commit
  2. 12 Oct, 2017 4 commits
  3. 08 Nov, 2015 1 commit
  4. 05 Sep, 2015 1 commit
  5. 13 Nov, 2013 1 commit
  6. 18 Sep, 2013 1 commit
    • John Stultz's avatar
      rtc: rtc-pl031: Set wakeup flag prior to registering rtcdev · 07783397
      John Stultz authored
      In some recent testing, I noticed the CLOCK_REALTIME_ALARM clockid
      wasn't functioning on my vexpress qemu environment. Looking into it
      I noticed the pl031 rtc driver doesn't set the wakeup flag on the
      device until after registering the device with the RTC subsystem.
      
      This causes the alarmtimer subsystem to not see the pl031 driver
      as a valid backing device, and that resuls in alarm clockids
      getting ENOTSUPP errors.
      
      Thus be sure to set the wakeup flag on the device prior to
      registering the rtcdev so the pl031 rtc driver can be used as
      the backing alarmtimer device.
      
      Cc: Linus Walleij <linus.walleij@linaro.org>
      Cc: Alessandro Zummo <a.zummo@towertech.it>
      Cc: "Jon Medhurst (Tixy)" <tixy@linaro.org>
      Cc: linux-arm-kernel@lists.infradead.org
      Acked-by: default avatarLinus Walleij <linus.walleij@linaro.org>
      Signed-off-by: default avatarJohn Stultz <john.stultz@linaro.org>
      07783397
  7. 24 May, 2013 1 commit
  8. 22 Feb, 2013 1 commit
  9. 12 Feb, 2013 1 commit
  10. 05 Feb, 2013 1 commit
  11. 31 Jul, 2012 3 commits
  12. 29 May, 2012 1 commit
  13. 18 May, 2012 1 commit
  14. 12 Apr, 2012 1 commit
  15. 23 Mar, 2012 1 commit
  16. 16 Mar, 2012 1 commit
  17. 22 Nov, 2011 1 commit
  18. 09 Mar, 2011 2 commits
    • John Stultz's avatar
      RTC: Cleanup rtc_class_ops->irq_set_freq() · 696160fe
      John Stultz authored
      With the generic rtc code now emulating PIE mode irqs via an
      hrtimer, no one calls the rtc_class_ops->irq_set_freq call.
      
      This patch removes the hook and deletes the driver functions
      if no one else calls them.
      
      CC: Thomas Gleixner <tglx@linutronix.de>
      CC: Alessandro Zummo <a.zummo@towertech.it>
      CC: Marcelo Roberto Jimenez <mroberto@cpti.cetuc.puc-rio.br>
      CC: rtc-linux@googlegroups.com
      Signed-off-by: default avatarJohn Stultz <john.stultz@linaro.org>
      696160fe
    • John Stultz's avatar
      RTC: Cleanup rtc_class_ops->irq_set_state · 80d4bb51
      John Stultz authored
      With PIE mode interrupts now emulated in generic code via an hrtimer,
      no one calls rtc_class_ops->irq_set_state(), so this patch removes it
      along with driver implementations.
      
      CC: Thomas Gleixner <tglx@linutronix.de>
      CC: Alessandro Zummo <a.zummo@towertech.it>
      CC: Marcelo Roberto Jimenez <mroberto@cpti.cetuc.puc-rio.br>
      CC: rtc-linux@googlegroups.com
      Signed-off-by: default avatarJohn Stultz <john.stultz@linaro.org>
      80d4bb51
  19. 23 Feb, 2011 1 commit
  20. 10 Sep, 2010 1 commit
  21. 11 Aug, 2010 1 commit
  22. 27 Jul, 2010 1 commit
    • Russell King's avatar
      ARM: Fix section build warnings for AMBA drivers · 2c39c9e1
      Russell King authored
      Found in the Versatile build:
      
      WARNING: drivers/built-in.o(.data+0x14c): Section mismatch in reference from the variable pl061_gpio_driver to the (unknown reference) .init.data:(unknown)
      The variable pl061_gpio_driver references
      the (unknown reference) __initdata (unknown)
      
      WARNING: drivers/built-in.o(.data+0x40f8): Section mismatch in reference from the variable pl011_driver to the (unknown reference) .init.data:(unknown)
      The variable pl011_driver references
      the (unknown reference) __initdata (unknown)
      
      WARNING: drivers/built-in.o(.data+0x5ab4): Section mismatch in reference from the variable pl031_driver to the (unknown reference) .init.data:(unknown)
      The variable pl031_driver references
      the (unknown reference) __initdata (unknown)
      
      Basically, amba_id structures must not be __initdata.  Also fix:
      
      WARNING: drivers/built-in.o(.data+0x138): Section mismatch in reference from the variable pl061_gpio_driver to the function .init.text:pl061_probe()
      The variable pl061_gpio_driver references
      the function __init pl061_probe()
      
      which is an incorrectly annotated probe function.  Fix it to reflect
      the other AMBA bus probe functions by removing the __init attributation.
      Signed-off-by: default avatarRussell King <rmk+kernel@arm.linux.org.uk>
      2c39c9e1
  23. 30 Mar, 2010 1 commit
    • Tejun Heo's avatar
      include cleanup: Update gfp.h and slab.h includes to prepare for breaking... · 5a0e3ad6
      Tejun Heo authored
      include cleanup: Update gfp.h and slab.h includes to prepare for breaking implicit 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: default avatarTejun Heo <tj@kernel.org>
      Guess-its-ok-by: default avatarChristoph Lameter <cl@linux-foundation.org>
      Cc: Ingo Molnar <mingo@redhat.com>
      Cc: Lee Schermerhorn <Lee.Schermerhorn@hp.com>
      5a0e3ad6
  24. 04 Feb, 2010 1 commit
  25. 16 Dec, 2009 1 commit
  26. 11 Jun, 2009 1 commit
    • Linus Walleij's avatar
      [ARM] 5544/1: Trust PrimeCell resource sizes · dc890c2d
      Linus Walleij authored
      I found the PrimeCell/AMBA Bus drivers distrusting the resource
      passed in as part of the struct amba_device abstraction. This
      patch removes all hard coded resource sizes found in the PrimeCell
      drivers and move the responsibility of this definition back to
      the platform/board device definition, which already exist and
      appear to be correct for all in-tree users of these drivers.
      We do this using the resource_size() inline function which was
      also replicated in the only driver using the resource size, so
      that has been changed too. The KMI_SIZE was left in kmi.h in case
      someone likes it. Test-compiled against Versatile and Integrator
      defconfigs, seems to work but I don't posess these boards and
      cannot test them.
      Signed-off-by: default avatarLinus Walleij <linus.walleij@stericsson.com>
      Signed-off-by: default avatarRussell King <rmk+kernel@arm.linux.org.uk>
      dc890c2d
  27. 20 May, 2009 1 commit
  28. 16 Oct, 2008 1 commit
  29. 22 May, 2008 1 commit
  30. 19 Oct, 2007 1 commit
  31. 08 May, 2007 1 commit
  32. 05 Oct, 2006 1 commit
    • David Howells's avatar
      IRQ: Maintain regs pointer globally rather than passing to IRQ handlers · 7d12e780
      David Howells authored
      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: default avatarDavid Howells <dhowells@redhat.com>
      (cherry picked from 1b16e7ac850969f38b375e511e3fa2f474a33867 commit)
      7d12e780
  33. 01 Oct, 2006 1 commit
  34. 02 Jul, 2006 1 commit