1. 24 9月, 2010 4 次提交
  2. 06 8月, 2010 4 次提交
  3. 20 7月, 2010 1 次提交
    • S
      ASoC: davinci: let platform data define edma queue numbers · 48519f0a
      Sekhar Nori 提交于
      Currently the EDMA queue to be used by for servicing ASP through
      internal RAM is fixed to EDMAQ_0 and that to service internal RAM
      from external RAM is fixed to EDMAQ_1.
      
      This may not be the desirable configuration on all platforms. For
      example, on DM365, queue 0 has large fifo size and is more suitable
      for video transfers. Having audio and video transfers on the same
      queue may lead to starvation on audio side.
      
      platform data as defined currently passes a queue number to the driver
      but that remains unused inside the driver.
      
      Fix this by defining one queue each for ASP and RAM transfers in the
      platform data and using it inside the driver.
      
      Since EDMAQ_0 maps to 0, thats the queue that will be used if
      the asp queue number is not initialized. None of the platforms
      currently utilize ping-pong transfers through internal RAM so that
      functionality remains unchanged too.
      
      This patch has been tested on DM644x and OMAP-L138 EVMs.
      Signed-off-by: NSekhar Nori <nsekhar@ti.com>
      Acked-by: NLiam Girdwood <lrg@slimlogic.co.uk>
      Signed-off-by: NMark Brown <broonie@opensource.wolfsonmicro.com>
      48519f0a
  4. 16 7月, 2010 1 次提交
  5. 06 7月, 2010 2 次提交
  6. 22 6月, 2010 4 次提交
    • C
      Davinci: tnetv107x initial gpio support · d92c7962
      Cyril Chemparathy 提交于
      This patch adds support for the tnetv107x gpio controller.
      
      Key differences between davinci and tnetv107x controllers:
       - register map - davinci's controller is organized into banks of 32 gpios,
         tnetv107x has a single space with arrays of registers for in, out,
         direction, etc.
       - davinci's controller has separate set/clear registers for output, tnetv107x
         has a single direct mapped register.
      
      This patch does not yet add gpio irq support on this controller.
      Signed-off-by: NCyril Chemparathy <cyril@ti.com>
      Signed-off-by: NKevin Hilman <khilman@deeprootsystems.com>
      d92c7962
    • C
      Davinci: tnetv107x soc support · 4d1e7848
      Cyril Chemparathy 提交于
      TNETV107X is a Texas Instruments SOC that shares a number of common features
      with the Davinci architecture.  Some of the key differences between
      traditional Davincis and this new SOC are as follow:
      
      1. The SOCs clock architecture includes a new spread-spectrum PLL.  Some
      elements of the clock architecture are reused from Davinci (e.g. LPSC), but
      the PLL related code is overridden using existing interfaces in "struct clk".
      
      2. The MMR layout on this SOC is substantially different from Davinci.
      Consequently, the fixed I/O map is a whole lot more convoluted (more so than
      DA8xx).  The net impact here is that IO_ADDRESS() will not work on this SoC,
      and therefore all mappings have to be through ioremap().
      Signed-off-by: NCyril Chemparathy <cyril@ti.com>
      Signed-off-by: NKevin Hilman <khilman@deeprootsystems.com>
      4d1e7848
    • C
      Davinci: tnetv107x decompresser uart definitions · 38db050e
      Cyril Chemparathy 提交于
      Added definitions for tnetv107x uart base addresses, and modified base address
      selection for kernel decompressor to check for tnetv107x machine type.
      Signed-off-by: NCyril Chemparathy <cyril@ti.com>
      Signed-off-by: NKevin Hilman <khilman@deeprootsystems.com>
      38db050e
    • C
      Davinci: generalized debug macros · dc2eb76c
      Cyril Chemparathy 提交于
      This patch adopts a debug uart selection similar to the OMAP model.  During
      the boot process, the uncompress code determines the physical and virtual base
      addresses of the board-specific debug uart.  These addresses are then passed
      on to the in-kernel debug macros through a small chunk of memory placed just
      below the page tables (@0x80003ff8).
      Signed-off-by: NCyril Chemparathy <cyril@ti.com>
      Signed-off-by: NKevin Hilman <khilman@deeprootsystems.com>
      dc2eb76c
  7. 28 5月, 2010 1 次提交
    • S
      davinci: mmc: pass number of SG segments as platform data · ca2afb6d
      Sudhakar Rajashekhara 提交于
      On some platforms like DM355, the number of EDMA parameter slots available
      for EDMA_SLOT_ANY usage are few.  In such cases, if MMC/SD uses 16 slots
      for each instance of MMC controller, then the number of slots available
      for other modules will be very few.
      
      By passing the number of EDMA slots to be used in MMC driver from platform
      data, EDMA slots available for other purposes can be controlled.
      
      Most of the platforms will not use this platform data variable.  But on
      DM355, as the number of EDMA resources available is limited, the number of
      scatter- gather segments used inside the MMC driver can be 8 (passed as
      platform data) instead of 16.  On DM355, when the number of scatter-gather
      segments was reduced to 8, I saw a performance difference of about
      0.25-0.4 Mbytes/sec during write.  Read performance variations were
      negligible.
      Signed-off-by: NSudhakar Rajashekhara <sudhakar.raj@ti.com>
      Acked-by: NKevin Hilman <khilman@deeprootsystems.com>
      Cc: <linux-mmc@vger.kernel.org>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      ca2afb6d
  8. 14 5月, 2010 10 次提交
  9. 07 5月, 2010 13 次提交