Skip to content
  1. Feb 13, 2012
  3. Jan 26, 2012
  5. Jan 05, 2012
  7. Dec 14, 2011
    • Govindraj.R's avatar
      ARM: OMAP2+: UART: Add default mux for all uarts. · 7496ba30
      Govindraj.R authored 
      

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: default avatarGovindraj.R <govindraj.raja@ti.com>
Signed-off-by: default avatarKevin Hilman <khilman@ti.com>
      7496ba30
  9. Dec 13, 2011
  11. Dec 09, 2011
  13. Nov 17, 2011
  15. Nov 15, 2011
  17. Oct 03, 2011
  19. Sep 30, 2011
  21. Sep 27, 2011
  23. Aug 24, 2011
    • Tony Lindgren's avatar
      ARM: OMAP: Introduce SoC specific early_init · 8f5b5a41
      Tony Lindgren authored 
      

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: default avatarTony Lindgren <tony@atomide.com>
      8f5b5a41
    • Tony Lindgren's avatar
      ARM: OMAP: Move omap2_init_common_devices out of init_early · a4ca9dbe
      Tony Lindgren authored 
      

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: default avatarTony Lindgren <tony@atomide.com>
      a4ca9dbe
  25. Aug 21, 2011
  27. Jul 05, 2011
  29. Jul 04, 2011
  31. Jun 27, 2011
  33. Jun 20, 2011
    • Tony Lindgren's avatar
      omap: Set separate timer init functions to avoid cpu_is_omap tests · e74984e4
      Tony Lindgren authored 
      

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: default avatarTony Lindgren <tony@atomide.com>
Reviewed-by: default avatarKevin Hilman <khilman@ti.com>
      e74984e4
  35. Jun 14, 2011
  37. Jun 01, 2011
  39. May 31, 2011
  41. May 12, 2011
  43. May 11, 2011