Commits on Jun 10, 2011
  1. @ladios
Commits on May 28, 2011
  1. @ladios

    input: misc: gpio_matrix: Don't suspend if not detect_phone_status

    Make gpio matrix func behaves the old way in which it doesn't set
    irq wake status if board's keypad matrix has detect_phone_status
    disabled, so trackpad/vol-buttons wake can fully function.
    (via arco)
    ladios committed May 28, 2011
Commits on May 26, 2011
  1. @ladios
  2. @cyanogen
  3. @cyanogen
  4. @cyanogen
  5. @cyanogen

    msm: cpufreq: Add missing cpufreq_attr

    (via BuzzBumbleBee)
    cyanogen committed May 16, 2011
Commits on May 25, 2011
  1. @cyanogen

    ashmem: Fix flush routine of ashmem

    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 <>
    Shubhraprakash Das committed with cyanogen Mar 21, 2011
  2. @cyanogen

    time: Compensate for rounding on odd-frequency clocksources

    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 <>
    Kasper Pedersen committed with cyanogen Oct 20, 2010
  3. @zinx @cyanogen

    ganeth: better gannet device

    zinx committed with cyanogen May 16, 2011
  4. @paolo-github @cyanogen

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

    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.
    paolo-github committed with cyanogen Mar 22, 2011
  5. @thalamus @cyanogen

    Updated BFQ to v2.

    thalamus committed with cyanogen Mar 21, 2011
  6. @paolo-github @cyanogen

    block: introduce the BFQ I/O scheduler

    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)
    paolo-github committed with cyanogen Jul 2, 2010
  7. @paolo-github @cyanogen

    block: add cgroups, kconfig and build bits for BFQ

    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 <>
    paolo-github committed with cyanogen Feb 26, 2010
  8. @paolo-github @cyanogen

    block: prepare I/O context code for BFQ

    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 <>
    paolo-github committed with cyanogen Feb 26, 2010
  9. @cyanogen

    Update bcm wifi module to

    James Zdziebkowski committed with cyanogen May 25, 2011
  10. @cyanogen
  11. @cyanogen
  12. @cyanogen
  13. @toddpoynor @cyanogen
Commits on May 19, 2011
  1. @aleho

    Update legend defconfig

    aleho committed May 19, 2011
  2. @aleho
  3. @aleho

    Squashed commits for

    aleho committed Jan 13, 2011
  4. @aleho

    Squashed commits for

    aleho committed Aug 2, 2010
  5. @aleho

    Squashed commits for

    aleho committed Dec 10, 2010
  6. @aleho

    [CPUFREQ] ondemand: Refactor frequency increase code

    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 <>
    Mike Chan committed with aleho Jan 26, 2010
  7. @aleho

    msm7227: Overclocking support to 864MHz

    fix stepping from 400 to 768
    added all frequencies although them commented out.
    fix so all frequencies should work together
    jp committed with aleho Aug 17, 2010
Commits on May 18, 2011
  1. @aleho
  2. @aleho

    Export alarm functions

    These symbols are needed to load the out of tree tiwlan_drv module.
    aleho committed May 18, 2011
  3. @aleho

    Fix init of curcial optical joystick

    Checking for my_oj->device_id didn't seem to work properly.
    aleho committed May 18, 2011
  4. @aleho
Commits on May 17, 2011
  1. @aleho

    Add default config for Legend

    aleho committed May 17, 2011
  2. @aleho

    net: Reorder incoming packets in PPPoLAC and PPPoPNS.

    PPP handles packet loss but does not work with out of order packets.
    This change performs reordering of incoming data packets within a
    sliding window of one second. Since sequence number is optional,
    receiving a packet without it will drop all queued packets.
    Currently the logic is triggered by incoming packets, so queued
    packets have to wait till another packet is arrived. It is done for
    simplicity since no additional locks or threads are required. For
    reliable protocols, a retransmission will kick it. For unreliable
    protocols, queued packets just seem like packet loss. Time-critical
    protocols might be broken, but they never work with queueing anyway.
    Signed-off-by: Chia-chi Yeh <>
    Chia-chi Yeh committed with aleho Apr 15, 2011
  3. @aleho
  4. @aleho

    USB: f_mass_storage: Disable write cache support

    As part of mode sense CBW command, communicate to the
    host that write cache support is enabled and due to this
    during the write commnd, the host is asking for FUA and
    because of this write performance is degrading. Hence during
    mode sense command, intimate the host that write cache is not
    Chiranjeevi Velempati committed with aleho May 13, 2011