1. 09 1月, 2010 2 次提交
    • P
      OMAP2420 IO mapping: move IVA mapping virtual address out of vmalloc space · 51e888d7
      Paul Walmsley 提交于
      Commit 10db25fe causes the following
      kernel messages during N800 boot (and presumably all other 2420
      boards):
      
      [    0.000000] BUG: mapping for 0x58000000 at 0xe0000000 overlaps vmalloc space
      [    0.000000] BUG: mapping for 0x59000000 at 0xe1000000 overlaps vmalloc space
      [    0.000000] BUG: mapping for 0x5a000000 at 0xe2000000 overlaps vmalloc space
      
      Fix by remapping the IVA memory areas somewhere outside vmalloc space.
      Signed-off-by: NPaul Walmsley <paul@pwsan.com>
      Cc: Santosh Shilimkar <santosh.shilimkar@ti.com>
      Cc: Tony Lindgren <tony@atomide.com>
      51e888d7
    • P
      OMAP2xxx IO mapping: mark DSP mappings as being 2420-only · 7adb9987
      Paul Walmsley 提交于
      Out of the three major OMAP2 chip types, OMAP2420, OMAP2430, and OMAP3430,
      we only map the IVA on OMAP2420.  The memory mapping is not shared between
      OMAP2420 and OMAP2430, so it is inappropriate to label those macros as
      '24XX'; this patch changes them to '2420'.
      Signed-off-by: NPaul Walmsley <paul@pwsan.com>
      7adb9987
  2. 20 10月, 2009 4 次提交
  3. 29 8月, 2009 2 次提交
  4. 25 7月, 2009 1 次提交
    • J
      OMAP3 SDRC: add support for 2 SDRAM chip selects · 58cda884
      Jean Pihet 提交于
      Some OMAP3 boards (Beagle Cx, Overo, RX51, Pandora) have 2
      SDRAM parts connected to the SDRC.
      
      This patch adds the following:
      - add a new argument of type omap_sdrc_params struct*
      to omap2_init_common_hw and omap2_sdrc_init for the 2nd CS params
      - adapted the OMAP boards files to the new prototype of
      omap2_init_common_hw
      - add the SDRC 2nd CS registers offsets defines
      - adapt the sram sleep code to configure the SDRC for the 2nd CS
      
      Note: If the 2nd param to omap2_init_common_hw is NULL, then the
      parameters are not programmed into the SDRC CS1 registers
      
      Tested on 3430 SDP and Beagleboard rev C2 and B5, with
      suspend/resume and frequency changes (cpufreq).
      Signed-off-by: NJean Pihet <jpihet@mvista.com>
      Signed-off-by: NPaul Walmsley <paul@pwsan.com>
      58cda884
  5. 23 6月, 2009 1 次提交
  6. 29 5月, 2009 1 次提交
  7. 09 2月, 2009 1 次提交
    • P
      [ARM] OMAP2 SDRC: add SDRAM timing parameter infrastructure · 87246b75
      Paul Walmsley 提交于
      For a given SDRAM clock rate, SDRAM chips require memory controllers
      to use a specific set of timing minimums and maximums to transfer data
      reliably.  These parameters can be different for different memory chips
      and can also potentially vary by board.
      
      This patch adds the infrastructure for board-*.c files to pass this
      timing data to the SDRAM controller init function.  The timing data is
      specified in an 'omap_sdrc_params' structure, in terms of SDRC
      controller register values.  An array of these structs, one per SDRC
      target clock rate, is passed by the board-*.c file to
      omap2_init_common_hw().
      
      This patch does not define the values for different memory chips, nor
      does it use the values for anything; those will come in subsequent patches.
      
      linux-omap source commit is bc84ecfc795c2d1c5cda8da4127cf972f488a696.
      Signed-off-by: NPaul Walmsley <paul@pwsan.com>
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      Signed-off-by: NRussell King <rmk+kernel@arm.linux.org.uk>
      87246b75
  8. 30 11月, 2008 1 次提交
  9. 09 10月, 2008 1 次提交
    • S
      ARM: OMAP3: Add minimal omap3430 support · cc26b3b0
      Syed Mohammed, Khasim 提交于
      Add minimal omap3430 support based on earlier patches from
      Syed Mohammed Khasim. Also merge in omap34xx SRAM support
      from Karthik Dasu and use consistent naming for sram init
      functions.
      
      Also do following changes that make 34xx support usable:
      
      - Remove unused sram.c functions for 34xx
      
      - Rename IRQ_SIR_IRQ to INTCPS_SIR_IRQ and define it locally
        in entry-macro.S
      
      - Update mach-omap2/io.c to support 2420, 2430, and 34xx
      
      - Also merge in 34xx GPMC changes to add fields wr_access and
        wr_data_mux_bus from Adrian Hunter
      
      - Remove memory initialization call omap2_init_memory() until
        until more generic memory initialization patches are posted.
        It's OK to rely on bootloader initialization until then.
      Signed-off-by: NSyed Mohammed, Khasim <khasim@ti.com>
      Signed-off-by: Karthik Dasu<karthik-dp@ti.com>
      Signed-off-by: NAdrian Hunter <ext-adrian.hunter@nokia.com>
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      
      
      
      cc26b3b0
  10. 06 9月, 2008 2 次提交
  11. 07 8月, 2008 2 次提交
  12. 03 7月, 2008 2 次提交
  13. 15 4月, 2008 1 次提交
    • P
      ARM: OMAP2: Change 24xx to use new register access · 44595982
      Paul Walmsley 提交于
      This patch changes 24xx to use new register access, except for clock
      framework. Clock framework register access will get updates in the
      next patch.
      
      Note that board-*.c files change GPMC (General Purpose Memory Controller)
      access to use gpmc_cs_write_reg() instead of accessing the registers
      directly. The code also uses gpmc_fck instead of it's parent clock
      core_l3_ck for GPMC clock.
      
      The H4 board file also adds h4_init_flash() function, which specify the
      flash start and end addresses.
      
      Also note that sleep.S removes some unused registers addresses.
      Signed-off-by: NPaul Walmsley <paul@pwsan.com>
      Signed-off-by: NTony Lindgren <tony@atomide.com>
      44595982
  14. 21 9月, 2007 1 次提交
  15. 09 5月, 2007 1 次提交
  16. 24 6月, 2006 1 次提交
  17. 09 2月, 2006 1 次提交
  18. 10 11月, 2005 1 次提交
  19. 28 10月, 2005 1 次提交
  20. 08 9月, 2005 1 次提交
  21. 17 4月, 2005 1 次提交
    • L
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds 提交于
      Initial git repository build. I'm not bothering with the full history,
      even though we have it. We can create a separate "historical" git
      archive of that later if we want to, and in the meantime it's about
      3.2GB when imported into git - space that would just make the early
      git days unnecessarily complicated, when we don't have a lot of good
      infrastructure for it.
      
      Let it rip!
      1da177e4