Skip to content


Subversion checkout URL

You can clone with
Download ZIP
Commits on May 27, 2011
  1. Update legend defconfig

  2. @ladios
  3. @cyanogen
  4. @cyanogen
  5. @cyanogen

    cm: Add cyanogen_msm7227_defconfig

    cyanogen committed with
  6. @cyanogen

    msm: cpufreq: Add missing cpufreq_attr

    cyanogen committed with
    (via BuzzBumbleBee)
  7. @zinx

    ganeth: better gannet device

    zinx committed with
  8. @paolo-github

    Switch from BFQ-v2 to BFQ-v2-r1.

    paolo-github committed with
    When the first new request for the active queue arrives during disk idling,
    the device is not immediately unplugged if this request is small. This prevents
    the disk to be immediately committed to serve a small request. In fact, further
    requests are likely to be merged to this one quickly, after which the device is
    unplugged by some block layer function and larger requests are dispatched.
    The idling timeout and the weight-raising max time have been tuned a little bit
    too, as detailed below.
    Reduced a little bit the disk idling timeout for weight-raised
    queues. This helps reduce latencies for applications made of several
    processes that do something and then pass the token to the next
    process. By reducing the timeout we reduce the time that may be wasted
    to wait for the next request of a process that has just passed the token,
    and hence that will not issue any new request.
    Reduced the weight-raising max time from 8 to 7.5 seconds: this
    reduces a little bit the time interval during which a just-started
    disk-bound process may unproperly be weight-raised.
  9. @thalamus

    Updated BFQ to v2.

    thalamus committed with
  10. @paolo-github

    block: introduce the BFQ I/O scheduler

    paolo-github committed with
    Add the BFQ-v1-r1 I/O scheduler to 2.6.35.
    The general structure is borrowed from CFQ, as much of the code. A (bfq_)queue
    is associated to each task doing I/O on a device, and each time a scheduling
    decision has to be taken a queue is selected and it is served until it expires.
    The main differences are:
         - slices are given in the service domain: tasks are assigned budgets,
           measured in number of sectors. Once got the disk, a task must
           however consume its assigned budget within a configurable maximum time
           (by default, the maximum possible value of the budgets is automaticall
           computed to comply with this timeout). This allows the desired latency
           vs "throughput boosting" tradeoff to be set.
        - Budgets are scheduled according to a variant of WF2Q+, implemented
          using an augmented rb-tree to take eligibility into account while
          preserving an O(log N) overall complexity.
        - BFQ supports full hierarchical scheduling, exporting a cgroups
          interface.  Each node has a full scheduler, so each group can
          be assigned its own ioprio and an ioprio_class.
        - If the cgroups interface is used, weights can be explictly assigned,
          otherwise ioprio values are mapped to weights using the relation
          weight = IOPRIO_BE_NR - ioprio.
        - ioprio classes are served in strict priority order, i.e., lower
          priority queues are not served as long as there are higher priority
          queues.  Among queues in the same classes the bandwidth is distributed
          in proportion to the weights of each queue.
    Regarding what has not changed it is worth noting:
        - the handling of cfq_io_contexts to associate queues to tasks.
          of the code has been reused just renaming it.  (There is room for
          code sharing with CFQ but we wanted to minimize the impact of this
        - The handling of async queues.
        - The handling of idle windows.
        - The handling of merging.
        - The heuristics to assert that a task is worth an idle window (with
          minor modifications to hw_tag/CIC_SEEKY detection).
    Signed-off-by: Fabio Checconi <>
    Signed-off-by: Paolo Valente <>
    Ported the following commits to bfq:
        - cfq-iosched: compact io_context radix_tree (80b15c7389caa)
        - cfq-iosched: remove dead_key from cfq_io_context (bca4b914b5da3d8e)
  11. @paolo-github

    block: add cgroups, kconfig and build bits for BFQ

    paolo-github committed with
    Add a Kconfig option and do the related Makefile changes to compile
    the BFQ I/O scheduler.  Also let the cgroups subsystem know about the
    BFQ I/O controller.
    Signed-off-by: Fabio Checconi <>
    Signed-off-by: Paolo Valente <>
  12. @paolo-github

    block: prepare I/O context code for BFQ

    paolo-github committed with
    BFQ uses struct cfq_io_context to store its per-process per-device data,
    reusing the same code for cic handling of CFQ.  The code is not shared
    ATM to minimize the impact of these patches.
    This patch introduces a new hlist to each io_context to store all the
    cic's allocated by BFQ to allow calling the right destructor on module
    unload; the radix tree used for cic lookup needs to be duplicated
    because it can contain dead keys inserted by a scheduler and later
    retrieved by the other one.
    Update the io_context exit and free paths to take care also of
    the BFQ cic's.
    Change the type of cfqq inside struct cfq_io_context to void *
    to use it also for BFQ per-queue data.
    A new bfq-specific ioprio_changed field is necessary, too, to avoid
    clobbering cfq's one, so switch ioprio_changed to a bitmap, with one
    element per scheduler.
    Signed-off-by: Fabio Checconi <>
    Signed-off-by: Paolo Valente <>
    Signed-off-by: Francesco Allertsen <>
  13. Update bcm wifi module to

    James Zdziebkowski committed with
  14. @cyanogen
  15. @cyanogen

    msm: latte: Add latte board files

    cyanogen committed with
  16. @cyanogen
  17. @toddpoynor
Commits on May 23, 2011
  1. [ARM] msm_fb: Fix framebuffer console

    Arve Hjønnevåg committed with
    Don't allow non panning updates to bypass the wait for the panel to turn on.
    Change-Id: I32eedf37dd1b0d34cdcad782027b635e5c65f691
  2. mmc: msm_sdcc: Enable SDCC clocks before starting SDIO requests

    Sahitya Tummala committed with
    The SDCC clocks can be turned off either by SDIO client driver or by SDCC
    driver. The SDIO clients will turn off clocks as part of their low-power
    management and SDCC driver will turn off clocks if they are not already
    off during system suspend. The clocks will be turned on by SDIO client
    driver if it needs to send some commands to the card. But for any commands
    that are sent by MMC core or SDIO core layer, host driver should enable
    clocks. This patch ensures that clocks are enabled by host driver before
    sending any SDIO requests.
    Change-Id: I777323abd786be71800ad49464d93c1c79b0eabd
    CRs-fixed: 276420
    Signed-off-by: Sahitya Tummala <>
  3. mmc: Attribute the IO wait time properly in mmc_wait_for_req().

    Murali Palnati committed with
    In mmc_wait_for_req() function, change the call wait_for_completion()
    to wait_for_completion_io(). This change makes the kernel account for
    wait time as I/O wait and through another configuration this I/O wait
    is treated as busy which makes the acpu clock to scale up.
    CRs-Fixed: 283420
    Signed-off-by: Murali Palnati <>
    (cherry picked from commit 107b16434aaaa2ac67f6221b317d6556c138ba3a)
    Change-Id: I4fd15ed63b817af615b74b892d725d160f56551d
    Signed-off-by: Shruthi Krishna <>
Commits on May 21, 2011
  1. ashmem: Fix flush routine of ashmem

    Shubhraprakash Das committed with
    The ashmem flush function ashmem_flush_cache_range was calling
    dmac_clean_range and dmac_flush_range with a user virtual address
    which is not allowed. Instead of calling dmac_clean_range or
    dmac_flush_range use flush_cache_user_range which can be called
    with a user vitual address.
    Change-Id: I5dd137fb248b45ef2c7ea5f7bdb4b540b8310af9
    Signed-off-by: Shubhraprakash Das <>
  2. time: Compensate for rounding on odd-frequency clocksources

    Kasper Pedersen committed with
    When the clocksource is not a multiple of HZ, the clock will be off.  For
    acpi_pm, HZ=1000 the error is 127.111 ppm:
    The rounding of cycle_interval ends up generating a false error term in
    ntp_error accumulation since xtime_interval is not exactly 1/HZ.  So, we
    subtract out the error caused by the rounding.
    This has been visible since 2.6.32-rc2
    	commit a092ff0f90cae22b2ac8028ecd2c6f6c1a9e4601
    	time: Implement logarithmic time accumulation
    That commit raised NTP_INTERVAL_FREQ and exposed the rounding error.
    testing tool:
    Also tested with ntpd and a frequency counter.
    Change-Id: Iae33aab0d606414628adddd9a84bf40a6997cb2f
    Signed-off-by: Kasper Pedersen <>
    Acked-by: john stultz <>
    Cc: John Kacur <>
    Cc: Clark Williams <>
    Cc: Martin Schwidefsky <>
    Signed-off-by: Andrew Morton <>
    Signed-off-by: Thomas Gleixner <>
    Signed-off-by: Jeff Ohlstein <>
  3. arm: Allow CPU-supported unaligned accesses

    Brent DeGraaf committed with
    This change reconfigures the CPU to allow CPU-supported unaligned
    accesses, which are generally faster than software-only fixups,
    resulting in fewer alignment exceptions.
    Signed-off-by: Brent DeGraaf <>
Commits on May 19, 2011
  1. Update legend defconfig

  2. Squashed commits for

  3. Squashed commits for

  4. Squashed commits for

  5. [CPUFREQ] ondemand: Refactor frequency increase code

    Mike Chan committed with
    Make simpler to read and call.
    *** v3 - Always call when powersave_bias is enabled.
    Acked-by: Venkatesh Pallipadi <>
    Signed-off-by: Mike Chan <>
    Signed-off-by: Dave Jones <>
  6. msm7227: Overclocking support to 864MHz

    jp committed with
    fix stepping from 400 to 768
    added all frequencies although them commented out.
    fix so all frequencies should work together
Commits on May 18, 2011
  1. Export alarm functions

    These symbols are needed to load the out of tree tiwlan_drv module.
  2. Fix init of curcial optical joystick

    Checking for my_oj->device_id didn't seem to work properly.
Commits on May 17, 2011
  1. Add default config for Legend

Something went wrong with that request. Please try again.