1. 11 5月, 2010 1 次提交
    • R
      HID: ntrig: add sensitivity and responsiveness support · 369db2a6
      Rafi Rubin 提交于
      The old rejection size thresholds were too high for the 12" devices.
      Larger surfaces like the Dell Studio17 exacerbated the problem since
      contact size is reported on the same logical scale, making a contact
      look smaller to the larger screen.
      
      Since we have observed erroneous ghost events from these devices we
      still need to filter the incoming stream.
      
      The prior size threshold filter is still in place, though with
      defaults set to leave it off.
      
      This patch adds the two new classes of filters, those that reject
      live frames before activation, and those that reject empty frames
      until deactivation.  These filters are expressed in terms of a
      simple state machine for clarity (I hope).
      
      The activation filter has two components, slack and size, events
      are discarded until either is satisfied.  Slack is defined as
      the number of seemingly good contacts to read before accepting the
      stream as valid (if the threshold is reached in the middle of a frame
      the remainder of that frame is still discarded).
      
      The deactivation filter discards empty frames until hitting a
      deactivate slack.  This time measured in frames.  N-Trig devices
      emit 5-8 (observed so far) empty frames at the end of multitouch
      activity.  Ignoring the first few enables us to safely and gracefully
      handle erroneous empty frames, thus preventing a change in the tool
      state which would otherwise result in things like broken lines or
      dragged objects being dropped in bad places.
      
      Also, now that devices with different logical densities have
      been observed, the aforementioned sizes are scaled from physical
      to logical scales once those scales are identified.  Hopefully this
      should mean that a given threshold value means the same thing across
      differing devices.
      Signed-off-by: NRafi Rubin <rafi@seas.upenn.edu>
      Signed-off-by: NJiri Kosina <jkosina@suse.cz>
      369db2a6
  2. 10 5月, 2010 1 次提交
    • A
      cpuidle: Fix incorrect optimization · 1c6fe036
      Arjan van de Ven 提交于
      commit 672917dc ("cpuidle: menu governor: reduce latency on exit")
      added an optimization, where the analysis on the past idle period moved
      from the end of idle, to the beginning of the new idle.
      
      Unfortunately, this optimization had a bug where it zeroed one key
      variable for new use, that is needed for the analysis.  The fix is
      simple, zero the variable after doing the work from the previous idle.
      
      During the audit of the code that found this issue, another issue was
      also found; the ->measured_us data structure member is never set, a
      local variable is always used instead.
      Signed-off-by: NArjan van de Ven <arjan@linux.intel.com>
      Cc: Corrado Zoccolo <czoccolo@gmail.com>
      Cc: stable@kernel.org
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      1c6fe036
  3. 08 5月, 2010 2 次提交
  4. 07 5月, 2010 21 次提交
  5. 06 5月, 2010 11 次提交
  6. 05 5月, 2010 4 次提交
新手
引导
客服 返回
顶部