- 15 Sep, 2009 40 commits
-
-
Alan Cox authored
We don't need it, we have a perfectly good set of debug tools. For this pass keep a few debug printks around which are "should not happen" items Signed-off-by:
Alan Cox <alan@linux.intel.com> Signed-off-by:
Greg Kroah-Hartman <gregkh@suse.de>
-
Alan Cox authored
Kill off the loopback type in the driver Signed-off-by:
-
Alan Cox authored
Kill off the MSI structure Signed-off-by:
-
Alan Cox authored
We have two trivial IRQ routines, a single statement and a real function - relocate them. While we are at it kill the trivial to sort out soft reset and slv bits in the same areas of code. Signed-off-by:
-
Alan Cox authored
Signed-off-by:
-
Alan Cox authored
Signed-off-by:
-
Alan Cox authored
Signed-off-by:
-
Alan Cox authored
Signed-off-by:
-
Alan Cox authored
Signed-off-by:
-
Alan Cox authored
Signed-off-by:
-
Alan Cox authored
Signed-off-by:
-
Alan Cox authored
Signed-off-by:
-
Alan Cox authored
We only read eeprom id 0, in byte mode - so the rest can go away Signed-off-by:
-
Alan Cox authored
Signed-off-by:
-
Alan Cox authored
Signed-off-by:
-
Alan Cox authored
bOverrideAddress is write only so kill it rather than fix it Signed-off-by:
-
Alan Cox authored
No point having a file just for that Signed-off-by:
-
Alan Cox authored
Adapter was cleared by netdev allocation so any zero defaults do not need writing. Signed-off-by:
-
Alan Cox authored
Prune this back as most of it isn't relevant or used Signed-off-by:
-
Alan Cox authored
Signed-off-by:
-
Alan Cox authored
Signed-off-by:
-
Alan Cox authored
One writer, of a constant, one user .. it can go. Signed-off-by:
-
Alan Cox authored
Switch this to a Linux like naming as it occurs all over. Signed-off-by:
-
Alan Cox authored
Signed-off-by:
-
Alan Cox authored
They are all in the pcidev anyway plus are not used by the code Signed-off-by:
-
Alan Cox authored
Most are unused, one is used and can be replaced with the definition Signed-off-by:
-
Alan Cox authored
The RefCount field is accessed only by a macro and the only use of it in the tree is to read it, so it can go Signed-off-by:
-
Alan Cox authored
Signed-off-by:
-
Alan Cox authored
This is assigned once to ndis d0, and then never changes so it is a constant and we can zap it Signed-off-by:
-
Alan Cox authored
Switch to the more normal "flags" naming. Also fix up the nested use of spin_lock_irqsave Signed-off-by:
-
Alan Cox authored
Signed-off-by:
-
Alan Cox authored
Signed-off-by:
-
Alan Cox authored
atomic_long != atomic Signed-off-by:
-
Alan Cox authored
Signed-off-by:
-
Randy Dunlap authored
device attr's should be static, otherwise duplicate identifiers are created: drivers/staging/iio/trigger/iio-trig-gpio.o:(.data+0x1c): multiple definition of `dev_attr_name' Signed-off-by:
Randy Dunlap <randy.dunlap@oracle.com> Signed-off-by:
Andrew Morton <akpm@linux-foundation.org> Cc: Jonathan Cameron <jic23@cam.ac.uk> Signed-off-by:
-
Alan Cox authored
Signed-off-by:
-
Jonathan Cameron authored
Signed-off-by:
Jonathan Cameron <jic23@cam.ac.uk> Signed-off-by:
-
Jonathan Cameron authored
This needs considerably more work, all comments / suggestions welcomed. Signed-off-by:
-
Jonathan Cameron authored
Simple example of how a gpio trigger driver would work. Things to be added include interupt type control (high, low). Signed-off-by:
-
Jonathan Cameron authored
The original posting of this driver led to a discussion in which it was commented that a better system was needed for dealing with the many possible periodic interrupt sources available on some SoCs. Unfortunately that is a big task and as far as I know, no-one has taken it on as yet. So in the meantime this driver is still in here. Signed-off-by:
-
