1. 22 4月, 2009 1 次提交
  2. 29 3月, 2009 1 次提交
  3. 24 3月, 2009 34 次提交
  4. 20 3月, 2009 1 次提交
    • R
      [ARM] pass reboot command line to arch_reset() · be093beb
      Russell King 提交于
      OMAP wishes to pass state to the boot loader upon reboot in order to
      instruct it whether to wait for USB-based reflashing or not.  There is
      already a facility to do this via the reboot() syscall, except we ignore
      the string passed to machine_restart().
      
      This patch fixes things to pass this string to arch_reset().  This means
      that we keep the reboot mode limited to telling the kernel _how_ to
      perform the reboot which should be independent of what we request the
      boot loader to do.
      Acked-by: NTony Lindgren <tony@atomide.com>
      Signed-off-by: NRussell King <rmk+kernel@arm.linux.org.uk>
      be093beb
  5. 16 3月, 2009 1 次提交
    • N
      [ARM] make page_to_dma() highmem aware · 58edb515
      Nicolas Pitre 提交于
      If a machine class has a custom __virt_to_bus() implementation then it
      must provide a __arch_page_to_dma() implementation as well which is
      _not_ based on page_address() to support highmem.
      
      This patch fixes existing __arch_page_to_dma() and provide a default
      implementation otherwise.  The default implementation for highmem is
      based on __pfn_to_bus() which is defined only when no custom
      __virt_to_bus() is provided by the machine class.
      
      That leaves only ebsa110 and footbridge which cannot support highmem
      until they provide their own __arch_page_to_dma() implementation.
      But highmem support on those legacy platforms with limited memory is
      certainly not a priority.
      Signed-off-by: NNicolas Pitre <nico@marvell.com>
      58edb515
  6. 05 3月, 2009 2 次提交
    • A
      ARM: OMAP: Allow I2C bus driver to be compiled as a module · e9516516
      Aaro Koskinen 提交于
      Fixes a linker error when OMAP I2C bus driver is compiled as a module:
      
         ERROR: "i2c_register_board_info" [arch/arm/plat-omap/i2c.ko] undefined!
      
      The I2C utility functions used for board initialization should be always
      built-in.
      Signed-off-by: NAaro Koskinen <Aaro.Koskinen@nokia.com>
      Acked-by: NJarkko Nikula  <jarkko.nikula@nokia.com>
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      e9516516
    • A
      ARM: OMAP: sched_clock() corrected · 80ea3bac
      Aaro Koskinen 提交于
      After my OMAP3 board has been running for a while, I'm seeing weird
      latency traces like this:
      
            sh-1574    0d.h2  153us : do_timer (tick_do_update_jiffies64)
            sh-1574    0d.h2  153us : update_wall_time (do_timer)
            sh-1574    0d.h2  153us!: omap_32k_read (update_wall_time)
            sh-1574    0d.h2 1883us : update_xtime_cache (update_wall_time)
            sh-1574    0d.h2 1883us : clocksource_get_next (update_wall_time)
            sh-1574    0d.h2 1883us+: _spin_lock_irqsave (clocksource_get_next)
      
      and after a while:
      
            sh-17818   0d.h3  153us : do_timer (tick_do_update_jiffies64)
            sh-17818   0d.h3  153us : update_wall_time (do_timer)
            sh-17818   0d.h3  153us!: omap_32k_read (update_wall_time)
            sh-17818   0d.h3 1915us : update_xtime_cache (update_wall_time)
            sh-17818   0d.h3 1915us+: clocksource_get_next (update_wall_time)
            sh-17818   0d.h3 1945us : _spin_lock_irqsave (clocksource_get_next)
      
      Turns out that sched_clock() is using cyc2ns(), which returns NTP
      adjusted time. The sched_clock() frequency should not be adjusted. The
      patch deletes omap_32k_ticks_to_nsecs() and rewrites sched_clock()
      to do the conversion using the constant multiplier.
      Signed-off-by: NAaro Koskinen <Aaro.Koskinen@nokia.com>
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      80ea3bac