Skip to content

cloud-kernel
cloud-kernel

openanolis / cloud-kernel
1 年多 前同步成功

通知 161
Star 36
Fork 7
cloud-kernel
cloud-kernel
切换分支/标签
  1. 14 4月, 2010 4 次提交
    • D
      Input: wacom - fix some formatting issues · 73a97f4f
      由 Dmitry Torokhov 提交于 
      Fix identation of switch/case statements so they follow style used by the
rest of the kernel.
Signed-off-by: NDmitry Torokhov <dtor@mail.ru>
      73a97f4f
    • D
      Input: wacom - do not allocate wacom_wac separately · 51269fe8
      由 Dmitry Torokhov 提交于 
      There is no reason for allocating struct wacom_wac separately from
struct wacom since both have the same lifetime rules and are not
shared. Also make 'open' field a boolean.
Signed-off-by: NDmitry Torokhov <dtor@mail.ru>
      51269fe8
    • P
      Input: wacom - share pen info with touch of the same ID · 4492efff
      由 Ping Cheng 提交于 
      Touch enbaled devices share the same product ID with pen. However,
we do not want to post touch events while pen is in prox. To do so,
we used to keep a local static variable to keep track of if pen is
in prox or not. This works fine for Tablet PC devices since there
is only one device attached. With the newer touch enabled regular
tablets, we can not make this assumption any more, i.e, one system
may have more than one identical tablet plugged in.

This patch adds an new entry, shared, into the struct wacom_wac so
touch data can access pen data to locally. This solution assumes
the two tools (touch and pen) of the same ID will be probed one
after the other without interruption in between by another Wacom
device of the same ID.
      4492efff
    • P
      Input: wacom - switch mode upon system resume · 38101475
      由 Ping Cheng 提交于 
      When Wacom devices wake up from a sleep, the switch mode command
(wacom_query_tablet_data) is needed before wacom_open is called.
wacom_query_tablet_data should not be executed inside wacom_open
since wacom_open is called more than once during probe.

wacom_retrieve_hid_descriptor is removed from wacom_resume due
to the fact that the required descriptors are stored properly
upon system resume.
Signed-off-by: NPing Cheng <pingc@wacom.com>
Reported-and-tested-by: NAnton Anikin <Anton@Anikin.name>
Signed-off-by: NDmitry Torokhov <dtor@mail.ru>
      38101475
  3. 02 3月, 2010 1 次提交
  5. 20 2月, 2010 1 次提交
  7. 19 2月, 2010 1 次提交
  9. 11 2月, 2010 1 次提交
  11. 15 12月, 2009 2 次提交
  13. 21 8月, 2009 1 次提交
  15. 09 5月, 2009 1 次提交
  17. 29 4月, 2009 1 次提交
  19. 26 11月, 2008 1 次提交
  21. 18 10月, 2008 1 次提交
  23. 17 5月, 2008 1 次提交
  25. 15 4月, 2008 1 次提交
  27. 14 3月, 2008 1 次提交
  29. 20 10月, 2007 1 次提交
  31. 10 7月, 2007 1 次提交
  33. 08 5月, 2007 1 次提交
  35. 12 4月, 2007 3 次提交
  37. 21 12月, 2006 1 次提交
  39. 02 12月, 2006 1 次提交
  41. 18 10月, 2006 3 次提交
  43. 05 10月, 2006 1 次提交
    • D
      IRQ: Maintain regs pointer globally rather than passing to IRQ handlers · 7d12e780
      由 David Howells 提交于 
      Maintain a per-CPU global "struct pt_regs *" variable which can be used instead
of passing regs around manually through all ~1800 interrupt handlers in the
Linux kernel.

The regs pointer is used in few places, but it potentially costs both stack
space and code to pass it around.  On the FRV arch, removing the regs parameter
from all the genirq function results in a 20% speed up of the IRQ exit path
(ie: from leaving timer_interrupt() to leaving do_IRQ()).

Where appropriate, an arch may override the generic storage facility and do
something different with the variable.  On FRV, for instance, the address is
maintained in GR28 at all times inside the kernel as part of general exception
handling.

Having looked over the code, it appears that the parameter may be handed down
through up to twenty or so layers of functions.  Consider a USB character
device attached to a USB hub, attached to a USB controller that posts its
interrupts through a cascaded auxiliary interrupt controller.  A character
device driver may want to pass regs to the sysrq handler through the input
layer which adds another few layers of parameter passing.

I've build this code with allyesconfig for x86_64 and i386.  I've runtested the
main part of the code on FRV and i386, though I can't test most of the drivers.
I've also done partial conversion for powerpc and MIPS - these at least compile
with minimal configurations.

This will affect all archs.  Mostly the changes should be relatively easy.
Take do_IRQ(), store the regs pointer at the beginning, saving the old one:

	struct pt_regs *old_regs = set_irq_regs(regs);

And put the old one back at the end:

	set_irq_regs(old_regs);

Don't pass regs through to generic_handle_irq() or __do_IRQ().

In timer_interrupt(), this sort of change will be necessary:

	-	update_process_times(user_mode(regs));
	-	profile_tick(CPU_PROFILING, regs);
	+	update_process_times(user_mode(get_irq_regs()));
	+	profile_tick(CPU_PROFILING);

I'd like to move update_process_times()'s use of get_irq_regs() into itself,
except that i386, alone of the archs, uses something other than user_mode().

Some notes on the interrupt handling in the drivers:

 (*) input_dev() is now gone entirely.  The regs pointer is no longer stored in
     the input_dev struct.

 (*) finish_unlinks() in drivers/usb/host/ohci-q.c needs checking.  It does
     something different depending on whether it's been supplied with a regs
     pointer or not.

 (*) Various IRQ handler function pointers have been moved to type
     irq_handler_t.
Signed-Off-By: NDavid Howells <dhowells@redhat.com>
(cherry picked from 1b16e7ac850969f38b375e511e3fa2f474a33867 commit)
      7d12e780
  45. 28 9月, 2006 1 次提交