Skip to content

R
raspberrypi-kernel

openeuler / raspberrypi-kernel

通知 13
Star 1
Fork 0
R
raspberrypi-kernel
切换分支/标签
  1. 29 4月, 2009 1 次提交
  3. 25 4月, 2009 1 次提交
  5. 24 4月, 2009 1 次提交
  7. 19 4月, 2009 2 次提交
    • A
      Input: elantech - make sure touchpad is really in absolute mode · b2546df6
      由 Arjan Opmeer 提交于 
      There exist laptops with Elantech touchpads where switching to absolute mode
does not happen, although writing the configuration register succeeds
without error. Reading back the register afterwards reveils that the
absolute mode bit is not set as if masked out by the touchpad firmware.

Always read back register 0x10, make sure that for hardware version 1 the
absolute mode bit is actually set and fail otherwise. This prevents the case
where the touchpad is claimed by the Elantech driver but is nonetheless not
working.
Signed-off-by: NArjan Opmeer <arjan@opmeer.net>
Signed-off-by: NDmitry Torokhov <dtor@mail.ru>
      b2546df6
    • A
      Input: elantech - provide a workaround for jumpy cursor on firmware 2.34 · 3f8c0df4
      由 Arjan Opmeer 提交于 
      It seems that Elantech touchpad firmware version 2.34 on the Hercules eCAFÉ
suffers from a problem where bogus coordinates get reported at the beginning
of a touch action. This causes the mouse cursor or the scrolled page to
jump.

Included patch provides a workaround that discards mouse packets that are
likely to contain bogus coordinates. The workaround is activated when we
detect touchpad with fimware version 2.34.
Signed-off-by: NArjan Opmeer <arjan@opmeer.net>
Signed-off-by: NDmitry Torokhov <dtor@mail.ru>
      3f8c0df4
  9. 18 4月, 2009 4 次提交
  11. 16 4月, 2009 3 次提交
  13. 15 4月, 2009 8 次提交
  15. 12 4月, 2009 5 次提交
  17. 08 4月, 2009 1 次提交
  19. 03 4月, 2009 1 次提交
  21. 02 4月, 2009 2 次提交
  23. 31 3月, 2009 1 次提交
    • A
      proc 2/2: remove struct proc_dir_entry::owner · 99b76233
      由 Alexey Dobriyan 提交于 
      Setting ->owner as done currently (pde->owner = THIS_MODULE) is racy
as correctly noted at bug #12454. Someone can lookup entry with NULL
->owner, thus not pinning enything, and release it later resulting
in module refcount underflow.

We can keep ->owner and supply it at registration time like ->proc_fops
and ->data.

But this leaves ->owner as easy-manipulative field (just one C assignment)
and somebody will forget to unpin previous/pin current module when
switching ->owner. ->proc_fops is declared as "const" which should give
some thoughts.

->read_proc/->write_proc were just fixed to not require ->owner for
protection.

rmmod'ed directories will be empty and return "." and ".." -- no harm.
And directories with tricky enough readdir and lookup shouldn't be modular.
We definitely don't want such modular code.

Removing ->owner will also make PDE smaller.

So, let's nuke it.

Kudos to Jeff Layton for reminding about this, let's say, oversight.

http://bugzilla.kernel.org/show_bug.cgi?id=12454Signed-off-by: NAlexey Dobriyan <adobriyan@gmail.com>
      99b76233
  25. 30 3月, 2009 3 次提交
  27. 25 3月, 2009 1 次提交
  29. 16 3月, 2009 1 次提交
    • J
      Rationalize fasync return values · 60aa4924
      由 Jonathan Corbet 提交于 
      Most fasync implementations do something like:

     return fasync_helper(...);

But fasync_helper() will return a positive value at times - a feature used
in at least one place.  Thus, a number of other drivers do:

     err = fasync_helper(...);
     if (err < 0)
             return err;
     return 0;

In the interests of consistency and more concise code, it makes sense to
map positive return values onto zero where ->fasync() is called.

Cc: Al Viro <viro@ZenIV.linux.org.uk>
Signed-off-by: NJonathan Corbet <corbet@lwn.net>
      60aa4924
  31. 11 3月, 2009 1 次提交
  33. 10 3月, 2009 4 次提交