1. 09 10月, 2010 11 次提交
  2. 07 10月, 2010 2 次提交
    • G
      msm: gpio: Remove tlmm routines obsoleted by gpiomux. · 10c4580e
      Gregory Bean 提交于
      Now that all supported gpio_tlmm_config-using boards
      are using gpiomux, remove the deprecated code.
      Signed-off-by: NGregory Bean <gbean@codeaurora.org>
      Signed-off-by: NDaniel Walker <dwalker@codeaurora.org>
      10c4580e
    • G
      msm: add gpiomux api for gpio multiplex & configuration. · 1963a2af
      Gregory Bean 提交于
      Add the 'gpiomux' api, which addresses the following shortcomings
      of existing tlmm api:
      
      - gpio power-collapse, which is managed by a peripheral processor on
        other targets, must be managed by the application processor on the 8x60.
      - The enable/disable flag of the legacy gpio_tlmm_config api
        is not applicable on the 8x60, and causes confusion.
      - The gpio 'direction' bits are meaningless for all func_sel
        configurations except for generic-gpio mode (func_sel 0), in which
        case the gpio_direction_* functions should be used.  Having these
        bits in the tlmm api leads to confusion and misuse of the gpiolib
        api, and they have been removed in gpiomux.
      - The functional api of the legacy system ran contrary to the typical
        use-case, which is a single massive configuration at boot.  Rather
        than forcing hundreds of 'config' function calls, the new api
        allows data to be configured with a single table.
      
      gpiomux_get and gpiomux_put are meant to be called automatically
      when gpio_request and gpio_free are called, giving automatic
      gpiomux/tlmm control to those drivers/lines with simple
      power profiles - in the simplest cases, an entry in the gpiomux table
      and the correct usage of gpiolib is all that is required to get proper
      gpio power control.
      Signed-off-by: NGregory Bean <gbean@codeaurora.org>
      Signed-off-by: NDaniel Walker <dwalker@codeaurora.org>
      1963a2af
  3. 02 10月, 2010 1 次提交
    • N
      ARM: do not define VMALLOC_END relative to PAGE_OFFSET · 7c63984b
      Nicolas Pitre 提交于
      VMALLOC_END is supposed to be an absolute value, while PAGE_OFFSET may
      vary depending on the selected user:kernel memory split mode through
      CONFIG_VMSPLIT_*.  In fact, the goal of moving PAGE_OFFSET down is to
      accommodate more directly addressed RAM by the kernel below the vmalloc
      area, and having VMALLOC_END move along PAGE_OFFSET is rather against
      the very reason why PAGE_OFFSET can be moved in the first place.
      Signed-off-by: NNicolas Pitre <nicolas.pitre@linaro.org>
      7c63984b
  4. 10 8月, 2010 2 次提交
  5. 16 6月, 2010 1 次提交
  6. 14 5月, 2010 14 次提交
  7. 13 5月, 2010 7 次提交
  8. 19 3月, 2010 1 次提交
    • S
      msm: Add 'execute' datamover callback · 5b00f40f
      San Mehat 提交于
      Based on a patch from Brent DeGraaf:
      
      "The datamover supports channels which can be shared amongst devices.
      As a result, the actual data transfer may occur some time after the
      request is queued up. Some devices such as mmc host controllers
      will timeout if a command is issued too far in advance of the actual
      transfer, so if dma to other devices on the same channel is already
      in progress or queued up, the added delay can cause pending transfers
      to fail before they start. This change extends the api to allow a
      user callback to be invoked just before the actual transfer takes
      place, thus allowing actions directly associated with the dma
      transfer, such as device commands, to be invoked with precise timing.
      Without this mechanism, there is no way for a driver to realize
      this timing. Also adds a user pointer to the command structure for use
      by the caller to reference information that may be needed by the
      callback routine for proper identification and processing associated
      with that specific request. This change is necessary to fix problems
      associated with excessive command timeouts and race conditions in the
      mmc driver."
      
      This patch also fixes all the callers of msm_dmov_enqueue_cmd() to
      ensure their callback function is NULL.
      Signed-off-by: NSan Mehat <san@google.com>
      Cc: Brent DeGraaf <bdegraaf@quicinc.com>
      Cc: Brian Swetland <swetland@google.com>
      Signed-off-by: NDaniel Walker <dwalker@codeaurora.org>
      5b00f40f
  9. 13 2月, 2010 1 次提交