Searched refs:db9 (Results 1 – 7 of 7) sorted by relevance
| /linux/drivers/input/joystick/ |
| A D | db9.c | 87 struct db9 { struct
357 struct db9 *db9 = from_timer(db9, t, timer); in db9_timer() local
479 db9_saturn(db9->mode, port, db9->dev); in db9_timer()
509 struct db9 *db9 = input_get_drvdata(dev); in db9_open() local
533 struct db9 *db9 = input_get_drvdata(dev); in db9_close() local
548 struct db9 *db9; in db9_attach() local
593 db9 = kzalloc(sizeof(struct db9), GFP_KERNEL); in db9_attach()
594 if (!db9) in db9_attach()
611 snprintf(db9->phys[i], sizeof(db9->phys[i]), in db9_attach()
648 kfree(db9); in db9_attach()
[all …]
|
| A D | Makefile | 15 obj-$(CONFIG_JOYSTICK_DB9) += db9.o
|
| A D | Kconfig | 233 module will be called db9.
|
| /linux/Documentation/input/devices/ |
| A D | joystick-parport.rst | 233 Multisystem joysticks using db9.c
236 For the Multisystem joysticks, and their derivatives, the db9.c driver
290 the same as for db9, however with the diodes between::
360 logic, the only driver usable with them is the db9.c driver.
411 The rest is the same as for Multi2 joysticks using db9.c
418 handled by the db9.c driver. Its pinout is very different from anything
444 Multi joysticks using db9.c
533 db9.c
537 db9.c driver. It uses the following kernel/module command line::
539 db9.dev=port,type
[all …]
|
| /linux/arch/arm64/boot/dts/ti/ |
| A D | k3-am65-iot2050-common.dtsi | 188 db9_com_mode_pins_default: db9-com-mode-pins-default {
|
| /linux/Documentation/admin-guide/ |
| A D | spkguide.txt | 77 dectlk -- DecTalk Express (old and new, db9 serial only)
81 ltlk -- DoubleTalk LT, LiteTalk, or external Tripletalk (db9 serial only)
|
| A D | kernel-parameters.txt | 839 db9.dev[2|3]= [HW,JOY] Multisystem joystick support via parallel port
|
Completed in 20 milliseconds