1. 20 Feb, 2010 1 commit
  2. 01 Feb, 2010 1 commit
  3. 25 Jan, 2010 1 commit
    • Ben Dooks's avatar
      ARM: S3C64XX: Merge mach-s3c6400 and mach-s3c6410 · 431107ea
      Ben Dooks authored
      As per discussions with Russell King on linux-arm-kernel, it appears that
      both mach-s3c6400 and mach-s3c6410 are so close together that they should
      simply be merged into mach-s3c64xx.
      
      Note, this patch does not eliminate any of the bits that are still common,
      it is simply a move of the two directories together, any further common
      code will be eliminated or moved in further patches.
      Signed-off-by: default avatarBen Dooks <ben-linux@fluff.org>
      431107ea
  4. 15 Jan, 2010 1 commit
  5. 11 Jan, 2010 1 commit
  6. 06 Jan, 2010 1 commit
  7. 13 Dec, 2009 1 commit
    • Russell King's avatar
      ARM: fix sa1100 build · 1937f5b9
      Russell King authored
      Fix:
      
      arch/arm/mach-sa1100/generic.c:117: error: redefinition of 'cpufreq_get'
      include/linux/cpufreq.h:299: error: previous definition of 'cpufreq_get' was here
      
      cpufreq_get() is used on these platforms to tell drivers what the CPU
      frequency is, and therefore the bus frequency - which is critical for
      setting the PCMCIA and LCD timings.  Adding ifdefs to these drivers to
      select cpufreq_get() or some other interface adds confusion.  Making
      these drivers use some other interface for the normal paths and cpufreq
      stuff for the cpufreq notifier is insane as well.
      
      (Why x86 can't provide a version of cpufreq_get() which returns the
      CPU frequency when CPUFREQ is disabled is beyond me, rather than
      requiring a dummy zero-returning cpufreq_get().  Especially as they
      do:
      
      			unsigned long khz = cpufreq_get(cpu);
      			if (!khz)
      				khz = tsc_khz;
      
      In other words, if CPUFREQ is disabled, get it from tsc_khz - why
      not provide a dummy cpufreq_get() which returns tsc_khz?)
      Signed-off-by: default avatarRussell King <rmk+kernel@arm.linux.org.uk>
      1937f5b9
  8. 30 Nov, 2009 1 commit
    • Ben Dooks's avatar
      ARM: SAMSUNG: Add plat-samsung as starting point for plat-s3c* moves · cf383678
      Ben Dooks authored
      We inted to re-organise the plat-s3c/plat-s3c24xx/plat-s3c64xx into a
      more generic plat-samsung with less code in the other plat- directories
      to make it easier to port new devices and try and clear up some of the
      naming issues with newer devices.
      
      Start by creating a small arch/arm/plat-samsung with no actuall code in
      so we can move items in as we process them.
      
      Add this to arch/arm to allow it to build things once support is added.
      Signed-off-by: default avatarBen Dooks <ben-linux@fluff.org>
      cf383678
  9. 28 Nov, 2009 2 commits
  10. 27 Nov, 2009 1 commit
  11. 29 Oct, 2009 2 commits
    • Mikael Pettersson's avatar
      iop: enable generic time · 980f2296
      Mikael Pettersson authored
      This updates the IOP platform to use the kernel's generic time
      framework. With clockevent support in place, this reduces to
      selecting GENERIC_TIME and removing the platform's private timer
      ->offset() operation (iop_gettimeoffset).
      
      Tested on n2100, compile-tested for all plat-iop machines.
      Signed-off-by: default avatarMikael Pettersson <mikpe@it.uu.se>
      Signed-off-by: default avatarDan Williams <dan.j.williams@intel.com>
      980f2296
    • Mikael Pettersson's avatar
      iop: clockevent support · 469d3044
      Mikael Pettersson authored
      This updates the IOP platform to expose the interrupting
      timer 0 as a clockevent object. The timer interrupt handler
      is changed to call the clockevent ->event_handler() instead
      of timer_tick(), and ->set_next_event() and ->set_mode()
      operations are added to allow the mode of the timer to be
      updated (required for ONESHOT/NOHZ mode).
      
      Timer 0 must now be properly initialised, which requires
      a new write_tcr0() function from the mach-specific code.
      
      The mode of timer 0 must be read at the start of ->set_mode(),
      which requires a new read_tmr0() function from the mach-
      specific code.
      
      Initial setup of timer 0 is also rewritten to be more robust.
      
      Tested on n2100, compile-tested for all plat-iop machines.
      Signed-off-by: default avatarMikael Pettersson <mikpe@it.uu.se>
      Signed-off-by: default avatarDan Williams <dan.j.williams@intel.com>
      469d3044
  12. 15 Sep, 2009 1 commit
  13. 17 Aug, 2009 1 commit
  14. 16 Aug, 2009 1 commit
    • Byungho Min's avatar
      ARM: S5PC100: Kconfigs and Makefiles · 5a7652f2
      Byungho Min authored
      S5PC100 is a new SoC with ARM coretex-A8 and numerous peripherals. This SoC is
      successor of S3C64XX. S5PC100 has peripherals which are still similar to S3C
      families so some drivers in "arch/arm/plat-s3c" can be shared. S5PC100 specific
      drivers will be added in "arch/arm/plat-s5pcxx" or "arch/arm/mach-s5pc100"
      Signed-off-by: default avatarByungho Min <bhmin@samsung.com>
      [ben-linux@fluff.org: tidy and edit description]
      Signed-off-by: default avatarBen Dooks <ben-linux@fluff.org>
      5a7652f2
  15. 15 Aug, 2009 3 commits
  16. 13 Aug, 2009 2 commits
    • Uwe Kleine-König's avatar
      [ARM] let arch/arm/Kconfig source drivers/Kconfig · ac25150f
      Uwe Kleine-König authored
      The changes introduced by this change are:
        - drivers/mtd/Kconfig doesn't depend on ALIGNMENT_TRAP ||
          !CPU_CP15_MMU any more
        - the following files are sourced additionally:
          + drivers/macintosh/Kconfig
            completely depends on PPC || MAC || X86
          + drivers/telephony/Kconfig
            new
          + drivers/pps/Kconfig
            new
          + drivers/infiniband/Kconfig
            new
          + drivers/edac/Kconfig
            depends on X86 || PPC
          + drivers/vlynq/Kconfig
            depends on AR7 && EXPERIMENTAL (that is ARCH_MIPS)
          + drivers/xen/Kconfig
            everything depends on XEN
          + drivers/platform/Kconfig
            depends on X86
        - drivers/regulator/Kconfig is sourced later as is
          drivers/accessibility/Kconfig
      Signed-off-by: default avatarUwe Kleine-König <u.kleine-koenig@pengutronix.de>
      ac25150f
    • Uwe Kleine-König's avatar
      Use kernel/Kconfig.preempt for ARM · d45a398f
      Uwe Kleine-König authored
      before this patch ARM had it's own definition of CONFIG_PREEMPT.
      Instead of that use the general definition provided in
      kernel/Kconfig.preempt.
      
      This patch changes the available options in *config.  Namely PREEMPT
      isn't a stand alone bool anymore, but part of a 'choice' the
      following Kconfig symbols are added:
      
      	PREEMPT_NONE
      	PREEMPT_VOLUNTARY
      
      Selecting PREEMPT_NONE now produces exactly the code as not selecting
      PREEMPT before (apart from a comment in
      /sys/kernel/debug/tracing/(per_cpu/cpuX/)?trace).  The only difference
      PREEMPT_VOLUNTARY does is that might_resched might reschedule.  Both
      should't introduce regressions.
      Signed-off-by: default avatarUwe Kleine-König <u.kleine-koenig@pengutronix.de>
      Cc: Russell King <linux@arm.linux.org.uk>
      d45a398f
  17. 30 Jul, 2009 3 commits
  18. 24 Jul, 2009 3 commits
  19. 17 Jul, 2009 1 commit
  20. 06 Jul, 2009 2 commits
  21. 02 Jul, 2009 2 commits
  22. 16 Jun, 2009 1 commit
    • Mark Brown's avatar
      [ARM] S3C64XX: Initial support for DVFS · b3748ddd
      Mark Brown authored
      This patch provides initial support for CPU frequency scaling on the
      Samsung S3C ARM processors. Currently only S3C6410 processors are
      supported, though addition of another data table with supported clock
      rates should be sufficient to enable support for further CPUs.
      
      Use the regulator framework to provide optional support for DVFS in
      the S3C cpufreq driver. When a software controllable regulator is
      configured the driver will use it to lower the supply voltage when
      running at a lower frequency, giving improved power savings.
      
      When regulator support is disabled or no regulator can be obtained
      for VDDARM the driver will fall back to scaling only the frequency.
      Signed-off-by: default avatarMark Brown <broonie@opensource.wolfsonmicro.com>
      Signed-off-by: default avatarBen Dooks <ben-linux@fluff.org>
      b3748ddd
  23. 11 Jun, 2009 2 commits
  24. 09 Jun, 2009 1 commit
  25. 08 Jun, 2009 1 commit
  26. 31 May, 2009 1 commit
  27. 30 May, 2009 2 commits