An error occurred fetching the project authors.
  1. 17 Nov, 2010 3 commits
  2. 08 Oct, 2010 2 commits
    • Paul Walmsley's avatar
      OMAP2+: Kconfig: disallow builds for boards that don't use the currently-selected SoC · 6515e489
      Paul Walmsley authored
      Currently, if, for example, CONFIG_ARCH_OMAP2420 is not selected, OMAP2420
      board files can still be included in the build.  This results in link errors:
      
      arch/arm/mach-omap2/built-in.o: In function `omap_generic_map_io':
      .../arch/arm/mach-omap2/board-generic.c:51: undefined reference to `omap2_set_globals_242x'
      arch/arm/mach-omap2/built-in.o: In function `omap_h4_init':
      .../arch/arm/mach-omap2/board-h4.c:330: undefined reference to `omap2420_mux_init'
      arch/arm/mach-omap2/built-in.o: In function `omap_h4_map_io':
      .../arch/arm/mach-omap2/board-h4.c:373: undefined reference to `omap2_set_globals_242x'
      arch/arm/mach-omap2/built-in.o: In function `omap_apollon_init':
      .../arch/arm/mach-omap2/board-apollon.c:325: undefined reference to `omap2420_mux_init'
      arch/arm/mach-omap2/built-in.o: In function `omap_apollon_map_io':
      .../arch/arm/mach-omap2/board-apollon.c:353: undefined reference to `omap2_set_globals_242x'
      make: *** [.tmp_vmlinux1] Error 1
      
      Fix this by making the boards depend on the Kconfig option for the
      specific SoC that they use.
      
      Also, while here, fix the mach-omap2/board-generic.c file to remove the
      dependency on OMAP2420.
      
      Charulatha Varadarajan <charu@ti.com> caught a typo - thanks Charu.
      Signed-off-by: default avatarPaul Walmsley <paul@pwsan.com>
      Cc: Tony Lindgren <tony@atomide.com>
      Cc: Charulatha Varadarajan <charu@ti.com>
      6515e489
    • Enric Balletbo i Serra's avatar
      omap3: Add minimal OMAP3 IGEP module support · e844b1da
      Enric Balletbo i Serra authored
      The OMAP3 IGEP module is a low-power, high performance production-ready
      system-on-module (SOM) based on TI's OMAP3 family. More about this
      board at www.igep.es.
      Signed-off-by: default avatarEnric Balletbo i Serra <eballetbo@gmail.com>
      [tony@atomide.com: updated for the mmc changes and to be selected by default]
      Signed-off-by: default avatarTony Lindgren <tony@atomide.com>
      e844b1da
  3. 29 Sep, 2010 1 commit
    • Govindraj.R's avatar
      OMAP: SERIAL: Enable omap-serial driver in Kconfig · 12a75da2
      Govindraj.R authored
      Enable omap-serial driver in /mach-omap2/Kconfig and
      move 8250 driver selection for zoom boards. With omap-serial
      driver addition all omap-uarts can be handled with
      omap-serial driver.
      
      With addition of omap-serial driver console parameter
      needs be changed in bootargs from ttyS* should be
      replaced with ttyO* [O --> OMAP not ZERO]
      
      For example: ttyS0[UART1 on 3430SDP] changes to ttyO0.
      
      But with some boards that do not use omap-uart as console uart.
      we need to handle them with 8250 driver. Ex: ZOOM2/3.
      For zoom2/3 board we need to use 8250 serial driver and
      console parameter will remain ttyS0 which basically uses
      a Quad uart placed on the debug board connected through a
      gpio line.
      Signed-off-by: default avatarGovindraj.R <govindraj.raja@ti.com>
      Signed-off-by: default avatarKevin Hilman <khilman@deeprootsystems.com>
      12a75da2
  4. 28 Sep, 2010 1 commit
  5. 27 Sep, 2010 1 commit
  6. 20 Sep, 2010 1 commit
    • Santosh Shilimkar's avatar
      omap: Update and rename common defconfig for omap2plus devices · 455d4d2d
      Santosh Shilimkar authored
      This patch addresses below things
      
      - Renaming existing omap3_defconfig which has OMAP2, OMAP3 and OMAP4 builds
        enabled to more appropriate name 'omap2plus_defconfig'
      - L1 cache shift is suppose to be 5 on OMAP4 where as it is 6 on previous
        OMAPs. Keeping it to 5 is safer option for OMAP4 and previous OMAPs. For
        OMAP3 only build the shift would be still 6
      - Enable needed Errata's for OMAP4 to work with DMA based device drivers
      	CONFIG_PL310_ERRATA_588369=y
      	CONFIG_ARM_ERRATA_720789=y
      - Enable the Micrel ethernet controller
      	CONFIG_KS8851=y
      	CONFIG_KS8851_MLL=y
      
      With above three changes, OMAP4 ethernet, mmc etc works reliably.
      Signed-off-by: default avatarSantosh Shilimkar <santosh.shilimkar@ti.com>
      Signed-off-by: default avatarTony Lindgren <tony@atomide.com>
      455d4d2d
  7. 02 Aug, 2010 1 commit
  8. 05 Jul, 2010 9 commits
  9. 20 May, 2010 2 commits
  10. 23 Apr, 2010 1 commit
  11. 19 Feb, 2010 1 commit
  12. 18 Feb, 2010 1 commit
  13. 15 Feb, 2010 3 commits
  14. 08 Jan, 2010 1 commit
  15. 15 Dec, 2009 1 commit
  16. 12 Dec, 2009 6 commits
    • Mike Rapoport's avatar
      omap3: cm-t35: add mux initialization · edc961a2
      Mike Rapoport authored
      CM-T35 can be assembled with different set of peripherals thus making
      certain interfaces available to user as GPIOs or dedicated pins. Because
      of it CM-T35 bootloader sets up mux configuration only for pins
      necessary to boot the system and the rest of the mux configuration is
      done by the kernel. Besides, having mux configuration in the kernel
      allows to minimize dependancy on bootloader.
      Signed-off-by: default avatarMike Rapoport <mike@compulab.co.il>
      Signed-off-by: default avatarTony Lindgren <tony@atomide.com>
      edc961a2
    • Gregoire Gentil's avatar
      omap3: Board file of Always Innovating OMAP3-based Touch Book · 7a079cab
      Gregoire Gentil authored
      Board file of Always Innovating OMAP3-based Touch Book
      Signed-off-by: default avatarGregoire Gentil <gregoire@gentil.com>
      Signed-off-by: default avatarTony Lindgren <tony@atomide.com>
      7a079cab
    • Tony Lindgren's avatar
      omap: mux: Add 36xx CBP package support · 662c8b55
      Tony Lindgren authored
      Add 36xx CBP package support
      
      Cc: Benoit Cousson <b-cousson@ti.com>
      Signed-off-by: default avatarPaul Walmsley <paul@pwsan.com>
      Signed-off-by: default avatarTony Lindgren <tony@atomide.com>
      662c8b55
    • Tony Lindgren's avatar
      omap: mux: Add new style init functions to omap3 board-*.c files · ca5742bd
      Tony Lindgren authored
      Add new style mux init functions to omap3 board-*.c files
      
      So far Beagle has been confirmed to be a CBB package,
      and CM-T35 a CUS package.
      Signed-off-by: default avatarTony Lindgren <tony@atomide.com>
      ca5742bd
    • Tony Lindgren's avatar
      omap: mux: Add new style pin multiplexing data for 34xx · ddaa912a
      Tony Lindgren authored
      Add new style mux data for 34xx. This should also
      work with 3630 easily by adding the processor subset
      and ball data.
      
      Note that this data is __initdata, and gets optimized
      out except for the GPIO pins if CONFIG_OMAP_MUX
      is not set.
      
      Also note that this data uses omap3630 naming for
      the SDMMC registers instead of 34xx naming with just
      MMC.
      
      Cc: Benoit Cousson <b-cousson@ti.com>
      Signed-off-by: default avatarPaul Walmsley <paul@pwsan.com>
      Signed-off-by: default avatarTony Lindgren <tony@atomide.com>
      ddaa912a
    • Paul Walmsley's avatar
      OMAP3: SDRC: Place SDRC AC timing and MR changes in CORE DVFS SRAM code behind Kconfig · 18862cbe
      Paul Walmsley authored
      The code that reprograms the SDRC memory controller during CORE DVFS,
      mach-omap2/sram34xx.S:omap3_sram_configure_core_dpll(), does not
      ensure that all L3 initiators are prevented from accessing the SDRAM
      before modifying the SDRC AC timing and MR registers.  This can cause
      memory to be corrupted or cause the SDRC to enter an unpredictable
      state.  This patch places that code behind a Kconfig option,
      CONFIG_OMAP3_SDRC_AC_TIMING for now, and adds a note explaining what
      is going on.  Ideally the code can be added back in once supporting
      code is present to ensure that other initiators aren't touching the
      SDRAM.  At the very least, these registers should be reprogrammable
      during kernel init to deal with buggy bootloaders.  Users who know
      that all other system initiators will not be touching the SDRAM can
      also re-enable this Kconfig option.
      
      This is a modification of a patch originally written by Rajendra Nayak
      <rnayak@ti.com> (the original is at http://patchwork.kernel.org/patch/51927/).
      Rather than removing the code completely, this patch just comments it out.
      
      Thanks to Benoît Cousson <b-cousson@ti.com> and Christophe Sucur
      <c-sucur@ti.com> for explaining the technical basis for this and for
      explaining what can be done to make this path work in future code.
      Thanks to Richard Woodruff <r-woodruff2@ti.com>, Nishanth Menon
      <nm@ti.com>, and Olof Johansson <olof@lixom.net> for their comments.
      Signed-off-by: default avatarPaul Walmsley <paul@pwsan.com>
      Cc: Rajendra Nayak <rnayak@ti.com>
      Cc: Christophe Sucur <c-sucur@ti.com>
      Cc: Benoît Cousson <b-cousson@ti.com>
      Cc: Richard Woodruff <r-woodruff2@ti.com>
      Cc: Nishanth Menon <nm@ti.com>
      Cc: Olof Johansson <olof@lixom.net>
      18862cbe
  17. 02 Dec, 2009 1 commit
  18. 25 Nov, 2009 4 commits