Skip to content

R
raspberrypi-kernel

openeuler / raspberrypi-kernel

通知 13
Star 1
Fork 0
R
raspberrypi-kernel
切换分支/标签
  1. 13 2月, 2012 1 次提交
  3. 26 1月, 2012 5 次提交
  5. 05 1月, 2012 3 次提交
  7. 15 12月, 2011 1 次提交
    • G
      ARM: OMAP2+: UART: Add default mux for all uarts. · 7496ba30
      由 Govindraj.R 提交于 
      Padconf wakeup is used to wakeup uart after uart fclks/iclks are gated.
Rx-Pad wakeup was done by writing to rx-pad offset value populated in
serial.c idle_init. Remove the direct reading and writing into rx pad.
Remove the padconf field part of omap_uart_state struct and pad offsets
populated.

Now with mux framework support we can use mux_utilities
along with hmwod framework to handle io-pad configuration and enable rx-pad
wake-up mechanism.

To avoid breaking any board support add default mux data for all uart's
if mux info is not passed from board file.
With the default pads populated in serial.c wakeup capability for
rx pads is set, this can be used to enable uart_rx io-pad wakeup from
hwmod framework. The pad values in 3430sdp/4430sdp/omap4panda board file
are same as the default pad values populated in serial.c. Remove pad values
from 3430sdp/4430sdp/omap4panda board file and use the default pads
from serial.c file.
Signed-off-by: NGovindraj.R <govindraj.raja@ti.com>
Signed-off-by: NKevin Hilman <khilman@ti.com>
      7496ba30
  9. 14 12月, 2011 1 次提交
  11. 10 12月, 2011 1 次提交
  13. 18 11月, 2011 1 次提交
  15. 16 11月, 2011 1 次提交
  17. 04 10月, 2011 1 次提交
  19. 30 9月, 2011 4 次提交
  21. 27 9月, 2011 1 次提交
  23. 24 8月, 2011 2 次提交
    • T
      ARM: OMAP: Introduce SoC specific early_init · 8f5b5a41
      由 Tony Lindgren 提交于 
      Introduce them for each omap variant and just make them all call
omap2_init_common_infrastructure for now. Do this for each board-*.c
file except for board-generic and board-omap3beagle as they use
the same machine ID for multiple SoCs.

No functional changes.
Signed-off-by: NTony Lindgren <tony@atomide.com>
      8f5b5a41
    • T
      ARM: OMAP: Move omap2_init_common_devices out of init_early · a4ca9dbe
      由 Tony Lindgren 提交于 
      There's no need to call omap2_init_common_devices from init_early.

It no longer does anything else except reprogram the memory timings
for some boards, so it's better to do it later so we have a chance
to get console messages if something goes wrong.

Move it to happen after omap_serial_init gets called. And while
patching it anyways, rename it to omap_sdrc_init as suggested by
Benoit Cousson <b-cousson@ti.com>.
Signed-off-by: NTony Lindgren <tony@atomide.com>
      a4ca9dbe
  25. 22 8月, 2011 1 次提交
  27. 05 7月, 2011 5 次提交
  29. 04 7月, 2011 1 次提交
  31. 28 6月, 2011 1 次提交
  33. 20 6月, 2011 1 次提交
    • T
      omap: Set separate timer init functions to avoid cpu_is_omap tests · e74984e4
      由 Tony Lindgren 提交于 
      This is needed for the following patches so we can initialize the
rest of the hardware timers later on.

As with the init_irq calls, there's no need to do cpu_is_omap calls
during the timer init as we only care about the major omap generation.
This means that we can initialize the sys_timer with the .timer
entries alone.

Note that for now we just set stubs for the various sys_timer entries
that will get populated in a later patch. The following patches will
also remove the omap_dm_timer_init calls and change the init for the
rest of the hardware timers to happen with an arch_initcall.
Signed-off-by: NTony Lindgren <tony@atomide.com>
Reviewed-by: NKevin Hilman <khilman@ti.com>
      e74984e4
  35. 14 6月, 2011 1 次提交
  37. 01 6月, 2011 2 次提交
  39. 31 5月, 2011 1 次提交
  41. 12 5月, 2011 1 次提交
  43. 11 5月, 2011 2 次提交
  45. 03 5月, 2011 1 次提交
  47. 23 3月, 2011 1 次提交