1. 20 11月, 2010 1 次提交
    • O
      mmc: sdio: fix runtime PM anomalies by introducing MMC_CAP_POWER_OFF_CARD · ed919b01
      Ohad Ben-Cohen 提交于
      Some board/card/host configurations are not capable of powering off the
      card after boot.
      
      To support such configurations, and to allow smoother transition to
      runtime PM behavior, MMC_CAP_POWER_OFF_CARD is added, so hosts need to
      explicitly indicate whether it's OK to power off their cards after boot.
      
      SDIO core will enable runtime PM for a card only if that cap is set.
      As a result, the card will be powered down after boot, and will only
      be powered up again when a driver is loaded (and then it's up to the
      driver to decide whether power will be kept or not).
      
      This will prevent sdio_bus_probe() failures with setups that do not
      support powering off the card.
      Reported-and-tested-by: NDaniel Drake <dsd@laptop.org>
      Reported-and-tested-by: NArnd Hannemann <arnd@arndnet.de>
      Signed-off-by: NOhad Ben-Cohen <ohad@wizery.com>
      Signed-off-by: NChris Ball <cjb@laptop.org>
      ed919b01
  2. 23 10月, 2010 3 次提交
    • O
      mmc: sdio: support suspend/resume while runtime suspended · ed2a9785
      Ohad Ben-Cohen 提交于
      Bring SDIO devices back to full power before their suspend
      handler is invoked.
      
      Doing so ensures that SDIO suspend/resume semantics are
      maintained (drivers still get to decide whether their
      card should be removed or kept during system suspend,
      and at what power state), and that SDIO suspend/resume
      execution paths are unchanged.
      
      This is achieved by resuming a runtime-suspended SDIO device
      in its ->prepare() PM callback (similary to the PCI subsystem).
      
      Since the PM core always increments the run-time usage
      counter before calling the ->prepare() callback and decrements
      it after calling the ->complete() callback, it is guaranteed
      that when the system will come out of suspend, our device's
      power state will reflect its runtime PM usage counter.
      Signed-off-by: NOhad Ben-Cohen <ohad@wizery.com>
      Tested-by: NLuciano Coelho <luciano.coelho@nokia.com>
      Signed-off-by: NChris Ball <cjb@laptop.org>
      ed2a9785
    • O
      mmc: sdio: enable runtime PM for SDIO functions · 40bba0c1
      Ohad Ben-Cohen 提交于
      Enable runtime PM for SDIO functions.
      
      SDIO functions are initialized with a disabled runtime PM state,
      and are set active (and their usage count is incremented)
      only before potential drivers are probed.
      
      SDIO function drivers that support runtime PM should call
      pm_runtime_put_noidle() in their probe routine, and
      pm_runtime_get_noresume() in their remove routine (very
      similarly to PCI drivers).
      
      In case a matching driver does not support runtime PM, power will
      always be kept high (since the usage count is positive).
      Signed-off-by: NOhad Ben-Cohen <ohad@wizery.com>
      Tested-by: NLuciano Coelho <luciano.coelho@nokia.com>
      Signed-off-by: NChris Ball <cjb@laptop.org>
      40bba0c1
    • O
      mmc: sdio: use the generic runtime PM handlers · 80fd933c
      Ohad Ben-Cohen 提交于
      Assign the generic runtime PM handlers for SDIO.
      
      These handlers invoke the relevant SDIO function drivers'
      handlers, if exist, otherwise they just return success
      (so SDIO drivers don't have to define any runtime PM handlers
      unless they need to).
      
      Runtime PM is still disabled by default, so this patch alone
      has no immediate effect.
      Signed-off-by: NOhad Ben-Cohen <ohad@wizery.com>
      Tested-by: NLuciano Coelho <luciano.coelho@nokia.com>
      Signed-off-by: NChris Ball <cjb@laptop.org>
      80fd933c
  3. 30 3月, 2010 1 次提交
    • T
      include cleanup: Update gfp.h and slab.h includes to prepare for breaking... · 5a0e3ad6
      Tejun Heo 提交于
      include cleanup: Update gfp.h and slab.h includes to prepare for breaking implicit slab.h inclusion from percpu.h
      
      percpu.h is included by sched.h and module.h and thus ends up being
      included when building most .c files.  percpu.h includes slab.h which
      in turn includes gfp.h making everything defined by the two files
      universally available and complicating inclusion dependencies.
      
      percpu.h -> slab.h dependency is about to be removed.  Prepare for
      this change by updating users of gfp and slab facilities include those
      headers directly instead of assuming availability.  As this conversion
      needs to touch large number of source files, the following script is
      used as the basis of conversion.
      
        http://userweb.kernel.org/~tj/misc/slabh-sweep.py
      
      The script does the followings.
      
      * Scan files for gfp and slab usages and update includes such that
        only the necessary includes are there.  ie. if only gfp is used,
        gfp.h, if slab is used, slab.h.
      
      * When the script inserts a new include, it looks at the include
        blocks and try to put the new include such that its order conforms
        to its surrounding.  It's put in the include block which contains
        core kernel includes, in the same order that the rest are ordered -
        alphabetical, Christmas tree, rev-Xmas-tree or at the end if there
        doesn't seem to be any matching order.
      
      * If the script can't find a place to put a new include (mostly
        because the file doesn't have fitting include block), it prints out
        an error message indicating which .h file needs to be added to the
        file.
      
      The conversion was done in the following steps.
      
      1. The initial automatic conversion of all .c files updated slightly
         over 4000 files, deleting around 700 includes and adding ~480 gfp.h
         and ~3000 slab.h inclusions.  The script emitted errors for ~400
         files.
      
      2. Each error was manually checked.  Some didn't need the inclusion,
         some needed manual addition while adding it to implementation .h or
         embedding .c file was more appropriate for others.  This step added
         inclusions to around 150 files.
      
      3. The script was run again and the output was compared to the edits
         from #2 to make sure no file was left behind.
      
      4. Several build tests were done and a couple of problems were fixed.
         e.g. lib/decompress_*.c used malloc/free() wrappers around slab
         APIs requiring slab.h to be added manually.
      
      5. The script was run on all .h files but without automatically
         editing them as sprinkling gfp.h and slab.h inclusions around .h
         files could easily lead to inclusion dependency hell.  Most gfp.h
         inclusion directives were ignored as stuff from gfp.h was usually
         wildly available and often used in preprocessor macros.  Each
         slab.h inclusion directive was examined and added manually as
         necessary.
      
      6. percpu.h was updated not to include slab.h.
      
      7. Build test were done on the following configurations and failures
         were fixed.  CONFIG_GCOV_KERNEL was turned off for all tests (as my
         distributed build env didn't work with gcov compiles) and a few
         more options had to be turned off depending on archs to make things
         build (like ipr on powerpc/64 which failed due to missing writeq).
      
         * x86 and x86_64 UP and SMP allmodconfig and a custom test config.
         * powerpc and powerpc64 SMP allmodconfig
         * sparc and sparc64 SMP allmodconfig
         * ia64 SMP allmodconfig
         * s390 SMP allmodconfig
         * alpha SMP allmodconfig
         * um on x86_64 SMP allmodconfig
      
      8. percpu.h modifications were reverted so that it could be applied as
         a separate patch and serve as bisection point.
      
      Given the fact that I had only a couple of failures from tests on step
      6, I'm fairly confident about the coverage of this conversion patch.
      If there is a breakage, it's likely to be something in one of the arch
      headers which should be easily discoverable easily on most builds of
      the specific arch.
      Signed-off-by: NTejun Heo <tj@kernel.org>
      Guess-its-ok-by: NChristoph Lameter <cl@linux-foundation.org>
      Cc: Ingo Molnar <mingo@redhat.com>
      Cc: Lee Schermerhorn <Lee.Schermerhorn@hp.com>
      5a0e3ad6
  4. 18 12月, 2009 1 次提交
  5. 23 9月, 2009 1 次提交
  6. 09 11月, 2008 1 次提交
  7. 14 10月, 2007 1 次提交
  8. 24 9月, 2007 12 次提交