04 Aug, 2008
2 commits
-
We can simply wrap in to the dev_set/get_drvdata(), there's no reason
to track an extra level of private data on top of the struct device.Signed-off-by: Paul Mundt
-
These were completely inconsistent. Clean these up to take a maple_driver
pointer directly for consistency.Signed-off-by: Paul Mundt
29 Jul, 2008
1 commit
-
This patch cleans up the handling of the maple bus queue to remove
the risk of races when adding packets. It also removes references to the
redundant connect and disconnect functions.Signed-off-by: Adrian McMenamin
Signed-off-by: Paul Mundt
28 Jul, 2008
1 commit
-
The connect and disconnect functions are unnecessary - everything they do can be
accomplished in the initial probe - so remove them.Signed-off-by: Adrian McMenamin
Signed-off-by: Paul Mundt
26 Feb, 2008
1 commit
-
Remove an unused variable from the definition of struct maple_device
Signed-off-by: Adrian McMenamin
Signed-off-by: Paul Mundt
14 Feb, 2008
3 commits
-
maple_devinfo->connector_direction had a typo, fix it up..
Signed-off-by: Paul Mundt
-
This patch removes the now unneeded registration check variable from
struct maple_device. (This patch assumes the include/linux/maple.h file
has already been patched for whitespace errors by
http://lkml.org/lkml/2008/2/6/327)Signed-off-by: Adrian McMenamin
Signed-off-by: Paul Mundt -
This patch is fundamentally about fixing up the whitespace problems
introduced by my previous patch (that brought the code into mainline). A
second patch will follow that will fix memory leaks. The two need to be
applied sequentially.Signed-off-by: Adrian McMenamin
Signed-off-by: Paul Mundt
21 Sep, 2007
1 commit
-
The Maple bus is SEGA's proprietary serial bus for peripherals
(keyboard, mouse, controller etc). The bus is capable of some
(limited) hotplugging and operates at up to 2 M/bits.Drivers of one sort or another existed/exist for 2.4 and a rudimentary
port, which didn't support the 2.6 device driver model was also in
existence.This driver - for the bus logic itself and for the keyboard (other
drivers will follow) are based on the code and concepts of those old
drivers but have lots of completely rewritten parts.I have the maple bus code as a built in now as that seems the sane and
rational way to handle something like that - you either want the bus
or you don't.Signed-off-by: Adrian McMenamin
Signed-off-by: Paul Mundt