Re: Hotplugging for the input subsystem

[Vojtech Pavlik <vojtech@suse.cz>]

On Fri, Sep 28, 2001 at 09:29:36AM -0700, David Brownell wrote:
> > For a long time there was the problem that while upon inserting an USB
> > keyboard the HID driver was auto-loaded OK, the mousedev, joydev, etc
> > drivers were not.
> > 
> > This patch implements (among other things) hotplugging for the input
> > subsystem.
> 
> Great to see this patch!  Did you submit this to Linus, or are you
> waiting for feedback first? 

I'd like feedback first, yes.

> And what version of modutils knows
> how to emit records for "struct input_device_id" (or is there one?)
> via MODULE_DEVICE_TABLE?

None at all yet. I just started with the kernelside part of the whole
puzzle. This has to be implemented.

> > I can provide some docs if it isn't obvious how it works.
> 
> I provided skeletal docs on the website, mostly just grubbed from
> the invocation of the hotplug agent.
> 
>     http://linux-hotplug.sourceforge.net/?selected=input
> 
> Real explanations of all those bit parameters would be good to have,
> from anyone who knows the input subsystem.  There's too much
> "see the kernel source" there for my taste ... :)

Ok.:

ACTION: "add" or "remove", adding or removing the device

PRODUCT: idbus/idvendor/idproduct/idversion. Idbus is defined in
	 input.h, the rest is in bus specific includes, ie for PCI
	 idvendor and idproduct are from pci_ids.h.

NAME: The name of the device, as a string. Can be anything.

PHYS: Physical path of the device. This is defined to be constant if the
	device is plugged to the same port in the system and unique for all
	connected devices. It has the form: busX.X/busX.X/busX.X ...,
	where bus is bus type, X.X is bus address, typically slot or
	port, entries are slash delimited. Examples:

	pci00:07.2/usb0:2.3/input0
		USB device (mouse, keyboard ...) connected to port #3 of
		an USB hub connected to port #2, USB bus 0 of USB controller
		located in PCI slot 7 function 2.

	isa0201/gameport0/input0
		Joystick connected to a gameport on an ISA card at
		i/o address 0x201

	amimouse/input0
		Mouse of the Amiga

UNIQ: Unique device ID. If non-empty, and present, then this is a string that
	is unique for each device with the idbus/idvendor/idproduct/idversion
	combination. Typically a serial number. Not all devices have
	this.

EV, KEY, REL, ABS, MSC, LED, FF: Bitfields describing the device
	features, buttons, axes, etc. Encoded as arrays of hex longs
	without any leading zeros.

> > It'd be nice if someone could add support for this to the hotplug tools.
> 
> Yes indeed ... volunteers?

I can do it myself, if noone will take it, but I'd prefer on working on
hotplug support for gameport and serio ...

-- 
Vojtech Pavlik
SuSE Labs

_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel