1. 20 1月, 2012 1 次提交
  2. 18 1月, 2012 3 次提交
  3. 17 1月, 2012 10 次提交
  4. 16 1月, 2012 6 次提交
  5. 15 1月, 2012 1 次提交
  6. 14 1月, 2012 1 次提交
  7. 13 1月, 2012 8 次提交
  8. 12 1月, 2012 4 次提交
    • D
      lguest: move the lguest tool to the tools directory · 07fe9977
      Davidlohr Bueso 提交于
      This is a better location instead of having it in Documentation.
      Signed-off-by: NDavidlohr Bueso <dave@gnu.org>
      Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> (fixed compile)
      07fe9977
    • S
      mmc: core: Fixup delayed work clock gating patch · 4137e504
      Stephen Boyd 提交于
      c31b50e (mmc: core: Use delayed work in clock gating framework,
      2011-11-14) missed a few things during review:
      
       o A useless pr_info()
      
       o milliseconds was written as two words
      
       o The sysfs file had units in its output
      
      Fix all three problems.
      Signed-off-by: NStephen Boyd <sboyd@codeaurora.org>
      Cc: Sujit Reddy Thumma <sthumma@codeaurora.org>
      Signed-off-by: NChris Ball <cjb@laptop.org>
      4137e504
    • J
      mmc: boot partition ro lock support · add710ea
      Johan Rudholm 提交于
      Enable boot partitions to be read-only locked until next power on via
      a sysfs entry. There will be one sysfs entry for each boot partition:
      
      /sys/block/mmcblkXbootY/ro_lock_until_next_power_on
      
      Each boot partition is locked by writing 1 to its file.
      Signed-off-by: NJohan Rudholm <johan.rudholm@stericsson.com>
      Signed-off-by: NJohn Beckett <john.beckett@stericsson.com>
      Signed-off-by: NChris Ball <cjb@laptop.org>
      add710ea
    • S
      mmc: core: Use delayed work in clock gating framework · 597dd9d7
      Sujit Reddy Thumma 提交于
      Current clock gating framework disables the MCI clock as soon as the
      request is completed and enables it when a request arrives. This aggressive
      clock gating framework, when enabled, cause following issues:
      
      When there are back-to-back requests from the Queue layer, we unnecessarily
      end up disabling and enabling the clocks between these requests since 8MCLK
      clock cycles is a very short duration compared to the time delay between
      back to back requests reaching the MMC layer. This overhead can effect the
      overall performance depending on how long the clock enable and disable
      calls take which is platform dependent. For example on some platforms we
      can have clock control not on the local processor, but on a different
      subsystem and the time taken to perform the clock enable/disable can add
      significant overhead.
      
      Also if the host controller driver decides to disable the host clock too
      when mmc_set_ios function is called with ios.clock=0, it adds additional
      delay and it is highly possible that the next request had already arrived
      and unnecessarily blocked in enabling the clocks. This is seen frequently
      when the processor is executing at high speeds and in multi-core platforms
      thus reduces the overall throughput compared to if clock gating is
      disabled.
      
      Fix this by delaying turning off the clocks by posting request on
      delayed workqueue. Also cancel the unscheduled pending work, if any,
      when there is access to card.
      
      sysfs entry is provided to tune the delay as needed, default
      value set to 200ms.
      Signed-off-by: NSujit Reddy Thumma <sthumma@codeaurora.org>
      Acked-by: NLinus Walleij <linus.walleij@linaro.org>
      Signed-off-by: NChris Ball <cjb@laptop.org>
      597dd9d7
  9. 11 1月, 2012 6 次提交