21 Nov, 2013

1 commit

  • Pull more ACPI and power management updates from Rafael Wysocki:

    - ACPI-based device hotplug fixes for issues introduced recently and a
    fix for an older error code path bug in the ACPI PCI host bridge
    driver

    - Fix for recently broken OMAP cpufreq build from Viresh Kumar

    - Fix for a recent hibernation regression related to s2disk

    - Fix for a locking-related regression in the ACPI EC driver from
    Puneet Kumar

    - System suspend error code path fix related to runtime PM and runtime
    PM documentation update from Ulf Hansson

    - cpufreq's conservative governor fix from Xiaoguang Chen

    - New processor IDs for intel_idle and turbostat and removal of an
    obsolete Kconfig option from Len Brown

    - New device IDs for the ACPI LPSS (Low-Power Subsystem) driver and
    ACPI-based PCI hotplug (ACPIPHP) cleanup from Mika Westerberg

    - Removal of several ACPI video DMI blacklist entries that are not
    necessary any more from Aaron Lu

    - Rework of the ACPI companion representation in struct device and code
    cleanup related to that change from Rafael J Wysocki, Lan Tianyu and
    Jarkko Nikula

    - Fixes for assigning names to ACPI-enumerated I2C and SPI devices from
    Jarkko Nikula

    * tag 'pm+acpi-2-3.13-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm: (24 commits)
    PCI / hotplug / ACPI: Drop unused acpiphp_debug declaration
    ACPI / scan: Set flags.match_driver in acpi_bus_scan_fixed()
    ACPI / PCI root: Clear driver_data before failing enumeration
    ACPI / hotplug: Fix PCI host bridge hot removal
    ACPI / hotplug: Fix acpi_bus_get_device() return value check
    cpufreq: governor: Remove fossil comment in the cpufreq_governor_dbs()
    ACPI / video: clean up DMI table for initial black screen problem
    ACPI / EC: Ensure lock is acquired before accessing ec struct members
    PM / Hibernate: Do not crash kernel in free_basic_memory_bitmaps()
    ACPI / AC: Remove struct acpi_device pointer from struct acpi_ac
    spi: Use stable dev_name for ACPI enumerated SPI slaves
    i2c: Use stable dev_name for ACPI enumerated I2C slaves
    ACPI: Provide acpi_dev_name accessor for struct acpi_device device name
    ACPI / bind: Use (put|get)_device() on ACPI device objects too
    ACPI: Eliminate the DEVICE_ACPI_HANDLE() macro
    ACPI / driver core: Store an ACPI device pointer in struct acpi_dev_node
    cpufreq: OMAP: Fix compilation error 'r & ret undeclared'
    PM / Runtime: Fix error path for prepare
    PM / Runtime: Update documentation around probe|remove|suspend
    cpufreq: conservative: set requested_freq to policy max when it is over policy max
    ...

    Linus Torvalds
     

19 Nov, 2013

1 commit

  • Pull MMC updates from Chris Ball:
    "MMC highlights for 3.13:

    Core:
    - Improve runtime PM support, remove mmc_{suspend,resume}_host().
    - Add MMC_CAP_RUNTIME_RESUME, for delaying MMC resume until we're
    outside of the resume sequence (in runtime_resume) to decrease
    system resume time.

    Drivers:
    - dw_mmc: Support HS200 mode.
    - sdhci-eshdc-imx: Support SD3.0 SDR clock tuning, DDR on IMX6.
    - sdhci-pci: Add support for Intel Clovertrail and Merrifield"

    * tag 'mmc-updates-for-3.13-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/cjb/mmc: (108 commits)
    mmc: wbsd: Silence compiler warning
    mmc: core: Silence compiler warning in __mmc_switch
    mmc: sh_mmcif: Convert to clk_prepare|unprepare
    mmc: sh_mmcif: Convert to PM macros when defining dev_pm_ops
    mmc: dw_mmc: exynos: Revert the sdr_timing assignment
    mmc: sdhci: Avoid needless loop while handling SDIO interrupts in sdhci_irq
    mmc: core: Add MMC_CAP_RUNTIME_RESUME to resume at runtime_resume
    mmc: core: Improve runtime PM support during suspend/resume for sd/mmc
    mmc: core: Remove redundant mmc_power_up|off at runtime callbacks
    mmc: Don't force card to active state when entering suspend/shutdown
    MIPS: db1235: Don't use MMC_CLKGATE
    mmc: core: Remove deprecated mmc_suspend|resume_host APIs
    mmc: mmci: Move away from using deprecated APIs
    mmc: via-sdmmc: Move away from using deprecated APIs
    mmc: tmio: Move away from using deprecated APIs
    mmc: sh_mmcif: Move away from using deprecated APIs
    mmc: sdricoh_cs: Move away from using deprecated APIs
    mmc: rtsx: Remove redundant suspend and resume callbacks
    mmc: wbsd: Move away from using deprecated APIs
    mmc: pxamci: Remove redundant suspend and resume callbacks
    ...

    Linus Torvalds
     

15 Nov, 2013

1 commit

  • Modify struct acpi_dev_node to contain a pointer to struct acpi_device
    associated with the given device object (that is, its ACPI companion
    device) instead of an ACPI handle corresponding to it. Introduce two
    new macros for manipulating that pointer in a CONFIG_ACPI-safe way,
    ACPI_COMPANION() and ACPI_COMPANION_SET(), and rework the
    ACPI_HANDLE() macro to take the above changes into account.
    Drop the ACPI_HANDLE_SET() macro entirely and rework its users to
    use ACPI_COMPANION_SET() instead. For some of them who used to
    pass the result of acpi_get_child() directly to ACPI_HANDLE_SET()
    introduce a helper routine acpi_preset_companion() doing an
    equivalent thing.

    The main motivation for doing this is that there are things
    represented by struct acpi_device objects that don't have valid
    ACPI handles (so called fixed ACPI hardware features, such as
    power and sleep buttons) and we would like to create platform
    device objects for them and "glue" them to their ACPI companions
    in the usual way (which currently is impossible due to the
    lack of valid ACPI handles). However, there are more reasons
    why it may be useful.

    First, struct acpi_device pointers allow of much better type checking
    than void pointers which are ACPI handles, so it should be more
    difficult to write buggy code using modified struct acpi_dev_node
    and the new macros. Second, the change should help to reduce (over
    time) the number of places in which the result of ACPI_HANDLE() is
    passed to acpi_bus_get_device() in order to obtain a pointer to the
    struct acpi_device associated with the given "physical" device,
    because now that pointer is returned by ACPI_COMPANION() directly.
    Finally, the change should make it easier to write generic code that
    will build both for CONFIG_ACPI set and unset without adding explicit
    compiler directives to it.

    Signed-off-by: Rafael J. Wysocki
    Acked-by: Greg Kroah-Hartman
    Tested-by: Mika Westerberg # on Haswell
    Reviewed-by: Mika Westerberg
    Reviewed-by: Aaron Lu # for ATA and SDIO part

    Rafael J. Wysocki
     

14 Nov, 2013

2 commits

  • Pull ARM updates from Russell King:
    "Included in this series are:

    1. BE8 (modern big endian) changes for ARM from Ben Dooks
    2. big.Little support from Nicolas Pitre and Dave Martin
    3. support for LPAE systems with all system memory above 4GB
    4. Perf updates from Will Deacon
    5. Additional prefetching and other performance improvements from Will.
    6. Neon-optimised AES implementation fro Ard.
    7. A number of smaller fixes scattered around the place.

    There is a rather horrid merge conflict in tools/perf - I was never
    notified of the conflict because it originally occurred between Will's
    tree and other stuff. Consequently I have a resolution which Will
    forwarded me, which I'll forward on immediately after sending this
    mail.

    The other notable thing is I'm expecting some build breakage in the
    crypto stuff on ARM only with Ard's AES patches. These were merged
    into a stable git branch which others had already pulled, so there's
    little I can do about this. The problem is caused because these
    patches have a dependency on some code in the crypto git tree - I
    tried requesting a branch I can pull to resolve these, and all I got
    each time from the crypto people was "we'll revert our patches then"
    which would only make things worse since I still don't have the
    dependent patches. I've no idea what's going on there or how to
    resolve that, and since I can't split these patches from the rest of
    this pull request, I'm rather stuck with pushing this as-is or
    reverting Ard's patches.

    Since it should "come out in the wash" I've left them in - the only
    build problems they seem to cause at the moment are with randconfigs,
    and since it's a new feature anyway. However, if by -rc1 the
    dependencies aren't in, I think it'd be best to revert Ard's patches"

    I resolved the perf conflict roughly as per the patch sent by Russell,
    but there may be some differences. Any errors are likely mine. Let's
    see how the crypto issues work out..

    * 'for-linus' of git://git.linaro.org/people/rmk/linux-arm: (110 commits)
    ARM: 7868/1: arm/arm64: remove atomic_clear_mask() in "include/asm/atomic.h"
    ARM: 7867/1: include: asm: use 'int' instead of 'unsigned long' for 'oldval' in atomic_cmpxchg().
    ARM: 7866/1: include: asm: use 'long long' instead of 'u64' within atomic.h
    ARM: 7871/1: amba: Extend number of IRQS
    ARM: 7887/1: Don't smp_cross_call() on UP devices in arch_irq_work_raise()
    ARM: 7872/1: Support arch_irq_work_raise() via self IPIs
    ARM: 7880/1: Clear the IT state independent of the Thumb-2 mode
    ARM: 7878/1: nommu: Implement dummy early_paging_init()
    ARM: 7876/1: clear Thumb-2 IT state on exception handling
    ARM: 7874/2: bL_switcher: Remove cpu_hotplug_driver_{lock,unlock}()
    ARM: footbridge: fix build warnings for netwinder
    ARM: 7873/1: vfp: clear vfp_current_hw_state for dying cpu
    ARM: fix misplaced arch_virt_to_idmap()
    ARM: 7848/1: mcpm: Implement cpu_kill() to synchronise on powerdown
    ARM: 7847/1: mcpm: Factor out logical-to-physical CPU translation
    ARM: 7869/1: remove unused XSCALE_PMU Kconfig param
    ARM: 7864/1: Handle 64-bit memory in case of 32-bit phys_addr_t
    ARM: 7863/1: Let arm_add_memory() always use 64-bit arguments
    ARM: 7862/1: pcpu: replace __get_cpu_var_uses
    ARM: 7861/1: cacheflush: consolidate single-CPU ARMv7 cache disabling code
    ...

    Linus Torvalds
     
  • Pull DMA mask updates from Russell King:
    "This series cleans up the handling of DMA masks in a lot of drivers,
    fixing some bugs as we go.

    Some of the more serious errors include:
    - drivers which only set their coherent DMA mask if the attempt to
    set the streaming mask fails.
    - drivers which test for a NULL dma mask pointer, and then set the
    dma mask pointer to a location in their module .data section -
    which will cause problems if the module is reloaded.

    To counter these, I have introduced two helper functions:
    - dma_set_mask_and_coherent() takes care of setting both the
    streaming and coherent masks at the same time, with the correct
    error handling as specified by the API.
    - dma_coerce_mask_and_coherent() which resolves the problem of
    drivers forcefully setting DMA masks. This is more a marker for
    future work to further clean these locations up - the code which
    creates the devices really should be initialising these, but to fix
    that in one go along with this change could potentially be very
    disruptive.

    The last thing this series does is prise away some of Linux's addition
    to "DMA addresses are physical addresses and RAM always starts at
    zero". We have ARM LPAE systems where all system memory is above 4GB
    physical, hence having DMA masks interpreted by (eg) the block layers
    as describing physical addresses in the range 0..DMAMASK fails on
    these platforms. Santosh Shilimkar addresses this in this series; the
    patches were copied to the appropriate people multiple times but were
    ignored.

    Fixing this also gets rid of some ARM weirdness in the setup of the
    max*pfn variables, and brings ARM into line with every other Linux
    architecture as far as those go"

    * 'for-linus-dma-masks' of git://git.linaro.org/people/rmk/linux-arm: (52 commits)
    ARM: 7805/1: mm: change max*pfn to include the physical offset of memory
    ARM: 7797/1: mmc: Use dma_max_pfn(dev) helper for bounce_limit calculations
    ARM: 7796/1: scsi: Use dma_max_pfn(dev) helper for bounce_limit calculations
    ARM: 7795/1: mm: dma-mapping: Add dma_max_pfn(dev) helper function
    ARM: 7794/1: block: Rename parameter dma_mask to max_addr for blk_queue_bounce_limit()
    ARM: DMA-API: better handing of DMA masks for coherent allocations
    ARM: 7857/1: dma: imx-sdma: setup dma mask
    DMA-API: firmware/google/gsmi.c: avoid direct access to DMA masks
    DMA-API: dcdbas: update DMA mask handing
    DMA-API: dma: edma.c: no need to explicitly initialize DMA masks
    DMA-API: usb: musb: use platform_device_register_full() to avoid directly messing with dma masks
    DMA-API: crypto: remove last references to 'static struct device *dev'
    DMA-API: crypto: fix ixp4xx crypto platform device support
    DMA-API: others: use dma_set_coherent_mask()
    DMA-API: staging: use dma_set_coherent_mask()
    DMA-API: usb: use new dma_coerce_mask_and_coherent()
    DMA-API: usb: use dma_set_coherent_mask()
    DMA-API: parport: parport_pc.c: use dma_coerce_mask_and_coherent()
    DMA-API: net: octeon: use dma_coerce_mask_and_coherent()
    DMA-API: net: nxp/lpc_eth: use dma_coerce_mask_and_coherent()
    ...

    Linus Torvalds
     

12 Nov, 2013

1 commit


09 Nov, 2013

6 commits


31 Oct, 2013

28 commits

  • DMA bounce limit is the maximum direct DMA'able memory beyond which
    bounce buffers has to be used to perform dma operations. MMC queue layr
    relies on dma_mask but its calculation is based on max_*pfn which
    don't have uniform meaning across architectures. So make use of
    dma_max_pfn() which is expected to return the DMAable maximum pfn
    value across architectures.

    Cc: Chris Ball
    Signed-off-by: Santosh Shilimkar
    Signed-off-by: Russell King

    Santosh Shilimkar
     
  • The code sequence:
    dev->dma_mask = &dev->coherent_dma_mask;
    dev->coherent_dma_mask = dma_mask;
    bypasses the architectures check on the DMA mask. It can be replaced
    with dma_coerce_mask_and_coherent(), avoiding the direct initialization
    of this mask.

    Signed-off-by: Russell King

    Russell King
     
  • In some environments it is to prefer to postpone the resume of the card
    device until runtime_resume is being carried out, since it will mean a
    signficant decrease of the total system resume time.

    The reason of the decreased resume time is simply because of the actual
    re-initalization of the card, which typically takes hundreds of
    milliseconds, is performed outside the resume sequence and wont thus
    affect it.

    For removable card, the detect work tries to re-detect the card to make
    sure it is still present, as a part of that sequence the card will also
    be runtime_resumed and thus also fully resumed.

    For a non-removable card, typically a mmc blk request will trigger a
    runtime_resume and thus fully resume the card. This also means the
    first request will likely suffer from an inital latency since the
    re-initialization of the card needs to be performed.

    Signed-off-by: Ulf Hansson
    Signed-off-by: Chris Ball

    Ulf Hansson
     
  • The card device is considered as in-active after it has been suspended.
    To prevent any further runtime PM requests in suspend state, we then
    disable runtime PM.

    After the card device has been resumed, we shall consider it as active,
    like we also do after a probe sequence. When resumed, we can safely
    enable runtime PM again.

    This will make sure the PM core can request the card device to go to
    in-active state after a resume has been completed. Previously we had to
    wait for new pm_runtime_get->pm_runtime_put cycle to be executed.

    Additionally, once a resume has been carried out, update the last busy
    mark. At the moment this will have no effect but if the PM core will
    respect autosuspend enabled devices, when it directly triggers a
    runtime_suspend from a runtime_idle, it will mean the card device will
    be scheduled for a delayed runtime_suspend instead of done immediately.

    Signed-off-by: Ulf Hansson
    Signed-off-by: Chris Ball

    Ulf Hansson
     
  • Commit "mmc: core: Push common suspend|resume code into each bus_ops"
    moved the responsibility for doing mmc_power_up|off into each
    suspend/resume bus_ops. When using MMC_CAP_AGGRESSIVE_PM, through the
    runtime callbacks, calls to mmc_power_up|off became redundant.

    When removing them, we are also able to remove the calls to
    mmc_claim|release_host, thus simplifing code a bit more.

    Signed-off-by: Ulf Hansson
    Signed-off-by: Chris Ball

    Ulf Hansson
     
  • By adding a card state that records if it is suspended or resumed, we
    can accept asyncronus suspend/resume requests for the mmc and sd
    bus_ops.

    MMC_CAP_AGGRESSIVE_PM, will at request inactivity through the runtime
    bus_ops callbacks, execute a suspend of the the card. In the state were
    this has been done, we can receive a suspend request for the mmc bus,
    which for sd and mmc forced the card to active state by a
    pm_runtime_get_sync. In other words, the card was resumed and then
    immediately suspended again, completely unnecessary.

    Since the suspend/resume bus_ops callbacks for sd and mmc are now
    capable of handling asynchronous requests, we no longer need to force
    the card to active state before executing suspend. Evidently preventing
    the above sequence for MMC_CAP_AGGRESSIVE_PM.

    Signed-off-by: Ulf Hansson
    Signed-off-by: Chris Ball

    Ulf Hansson
     
  • The are no more users of the deprecated mmc_suspend|resume_host API,
    so let's remove it.

    Signed-off-by: Ulf Hansson
    Signed-off-by: Chris Ball

    Ulf Hansson
     
  • Suspend and resume of cards are being handled from the protocol layer
    and consequently the mmc_suspend|resume_host APIs are deprecated.

    This means we can simplify the suspend|resume callbacks by removing the
    use of the deprecated APIs.

    Cc: Russell King
    Signed-off-by: Ulf Hansson
    Signed-off-by: Chris Ball

    Ulf Hansson
     
  • Suspend and resume of cards are being handled from the protocol layer
    and consequently the mmc_suspend|resume_host APIs are deprecated.

    This means we can simplify the suspend|resume callbacks by removing the
    use of the deprecated APIs.

    Cc: Bruce Chang
    Cc: Harald Welte
    Signed-off-by: Ulf Hansson
    Signed-off-by: Chris Ball

    Ulf Hansson
     
  • Suspend and resume of cards are being handled from the protocol layer
    and consequently the mmc_suspend|resume_host APIs are deprecated.

    This means we can simplify the suspend|resume callbacks by removing the
    use of the deprecated APIs.

    Cc: Guennadi Liakhovetski
    Cc: Ian Molton
    Signed-off-by: Ulf Hansson
    Signed-off-by: Chris Ball

    Ulf Hansson
     
  • Suspend and resume of cards are being handled from the protocol layer
    and consequently the mmc_suspend|resume_host APIs are deprecated.

    This means we can simplify the suspend|resume callbacks by removing the
    use of the deprecated APIs.

    Cc: Guennadi Liakhovetski
    Signed-off-by: Ulf Hansson
    Signed-off-by: Chris Ball

    Ulf Hansson
     
  • Suspend and resume of cards are being handled from the protocol layer
    and consequently the mmc_suspend|resume_host APIs are deprecated.

    This means we can simplify the suspend|resume callbacks by removing the
    use of the deprecated APIs.

    Cc: Sascha Sommer
    Signed-off-by: Ulf Hansson
    Acked-by: Sascha Sommer
    Signed-off-by: Chris Ball

    Ulf Hansson
     
  • Suspend and resume of cards are handled by the protocol layer and
    consequently the mmc_suspend|resume_host APIs are marked as deprecated.

    While moving away from using the deprecated APIs, there are nothing
    left to be done for the suspend and resume callbacks, so remove them.

    Cc: Wei WANG
    Cc: Samuel Ortiz
    Signed-off-by: Ulf Hansson
    Signed-off-by: Chris Ball

    Ulf Hansson
     
  • Suspend and resume of cards are being handled from the protocol layer
    and consequently the mmc_suspend|resume_host APIs are deprecated.

    This means we can simplify the suspend|resume callbacks by removing the
    use of the deprecated APIs.

    Cc: Pierre Ossman
    Signed-off-by: Ulf Hansson
    Signed-off-by: Chris Ball

    Ulf Hansson
     
  • Suspend and resume of cards are handled by the protocol layer and
    consequently the mmc_suspend|resume_host APIs are marked as deprecated.

    While moving away from using the deprecated APIs, there are nothing
    left to be done for the suspend and resume callbacks, so remove them.

    Signed-off-by: Ulf Hansson
    Signed-off-by: Chris Ball

    Ulf Hansson
     
  • Suspend and resume of cards are handled by the protocol layer and
    consequently the mmc_suspend|resume_host APIs are marked as deprecated.

    While moving away from using the deprecated APIs, there are nothing
    left to be done for the suspend and resume callbacks, so remove them.

    Cc: Ben Dooks
    Cc: linux-arm-kernel@lists.infradead.org
    Signed-off-by: Ulf Hansson
    Signed-off-by: Chris Ball

    Ulf Hansson
     
  • Suspend and resume of cards are being handled from the protocol layer
    and consequently the mmc_suspend|resume_host APIs are deprecated.

    This means we can simplify the suspend|resume callbacks by removing the
    use of the deprecated APIs.

    Cc: Tony Prisk
    Cc: linux-arm-kernel@lists.infradead.org
    Signed-off-by: Ulf Hansson
    Signed-off-by: Chris Ball

    Ulf Hansson
     
  • Suspend and resume of cards are being handled from the protocol layer
    and consequently the mmc_suspend|resume_host APIs are deprecated.

    This means we can simplify the suspend|resume callbacks by removing the
    use of the deprecated APIs.

    Cc: Sascha Hauer
    Cc: Anatolij Gustschin
    Signed-off-by: Ulf Hansson
    Acked-by: Sascha Hauer
    Signed-off-by: Chris Ball

    Ulf Hansson
     
  • Suspend and resume of cards are being handled from the protocol layer
    and consequently the mmc_suspend|resume_host APIs are deprecated.

    This means we can simplify the suspend|resume callbacks by removing the
    use of the deprecated APIs.

    Cc: Shawn Guo
    Cc: Fabio Estevam
    Signed-off-by: Ulf Hansson
    Acked-by: Shawn Guo
    Signed-off-by: Chris Ball

    Ulf Hansson
     
  • Suspend and resume of cards are handled by the protocol layer and
    consequently the mmc_suspend|resume_host APIs are marked as deprecated.

    While moving away from using the deprecated APIs, there are nothing
    left to be done for the suspend and resume callbacks, so remove them.

    Cc: Jarkko Lavinen
    Cc: linux-omap@vger.kernel.org
    Signed-off-by: Ulf Hansson
    Signed-off-by: Chris Ball

    Ulf Hansson
     
  • Suspend and resume of cards are being handled from the protocol layer
    and consequently the mmc_suspend|resume_host APIs are deprecated.

    This means we can simplify the suspend|resume callbacks by removing the
    use of the deprecated APIs.

    Cc: Alex Dubov
    Signed-off-by: Ulf Hansson
    Signed-off-by: Chris Ball

    Ulf Hansson
     
  • Suspend and resume of cards are being handled from the protocol layer
    and consequently the mmc_suspend|resume_host APIs are deprecated.

    This means we can simplify the suspend|resume callbacks by removing the
    use of the deprecated APIs.

    Signed-off-by: Ulf Hansson
    Signed-off-by: Chris Ball

    Ulf Hansson
     
  • Suspend and resume of cards are handled by the protocol layer and
    consequently the mmc_suspend|resume_host APIs are marked as deprecated.

    This means we can simplify the suspend|resume callbacks by removing the
    use of the deprecated APIs.

    Cc: Tony Olech
    Cc: linux-usb@vger.kernel.org
    Signed-off-by: Ulf Hansson
    Cc: Alan Stern
    Signed-off-by: Chris Ball

    Ulf Hansson
     
  • Suspend and resume of cards are handled by the protocol layer and
    consequently the mmc_suspend|resume_host APIs are marked as deprecated.

    While moving away from using the deprecated APIs, there are nothing
    left to be done for the suspend and resume callbacks, so remove them.

    Cc: Nicolas Pitre
    Cc: Thomas Petazzoni
    Cc: Jason Cooper
    Cc: Andrew Lunn
    Signed-off-by: Ulf Hansson
    Signed-off-by: Chris Ball

    Ulf Hansson
     
  • Suspend and resume of cards are being handled from the protocol layer
    and consequently the mmc_suspend|resume_host APIs are deprecated.

    This means we can simplify the suspend|resume callbacks by removing the
    use of the deprecated APIs.

    Additionally, remove dead code which also used the deprecated APIs.

    Cc: David Brown
    Cc: Daniel Walker
    Cc: Bryan Huntsman
    Cc: linux-arm-msm@vger.kernel.org
    Signed-off-by: Ulf Hansson
    Acked-by: David Brown
    Signed-off-by: Chris Ball

    Ulf Hansson
     
  • Suspend and resume of cards are being handled from the protocol layer
    and consequently the mmc_suspend|resume_host APIs are deprecated.

    This means we can simplify the suspend|resume callbacks by removing the
    use of the deprecated APIs.

    Cc: Lars-Peter Clausen
    Signed-off-by: Ulf Hansson
    Signed-off-by: Chris Ball

    Ulf Hansson
     
  • Suspend and resume of cards are being handled from the protocol layer
    and consequently the mmc_suspend|resume_host APIs are deprecated.

    This means we can simplify the suspend|resume callbacks by removing the
    use of the deprecated APIs.

    Cc: Seungwon Jeon
    Cc: Jaehoon Chung
    Signed-off-by: Ulf Hansson
    Signed-off-by: Chris Ball

    Ulf Hansson
     
  • Suspend and resume of cards are being handled from the protocol layer
    and consequently the mmc_suspend|resume_host APIs are deprecated.

    This means we can simplify the suspend|resume callbacks by removing the
    use of the deprecated APIs.

    Cc: Sekhar Nori
    Cc: Manjunathappa, Prakash
    Cc: davinci-linux-open-source@linux.davincidsp.com
    Signed-off-by: Ulf Hansson
    Signed-off-by: Chris Ball

    Ulf Hansson