Re: [INPUT] simple question on driver initialisation.

[Vojtech Pavlik <vojtech@suse.cz>]

On Tue, Jul 26, 2005 at 02:26:02PM +0200, moreau francis wrote:
> Thanks Vojtech for your answers !
> 
> --- Vojtech Pavlik <vojtech@suse.cz> a écrit :
> 
> > It's also available via an ioctl() and in sysfs. This allows you to
> > specify in an application that you want a device plugged into a specific
> > port of the machine. Not many applications can use it at the moment, but
> > udev can use it to assign a name of the device node.
> > 
> 
> hmm, how can I use ioctl to find the location device since I need the location
> to pass it to ioctl ?
> 
> I can't find "pinpad/input0" in sysfs, does that mean I need to add sysfs
> suppport in my driver, and it's not done in input module when I register 
> my input driver ?

I'm sorry, I thought it's already in mainline, but that bit is still
missing from the sysfs support in input. It'll get there soon.

> > "pinpad/input0" doesn't sound right. What port is your pinpad connected
> > to?
> 
> Actually I'm working on an embedded system which owns a pinpad controller.
> This controller is accessed by using io mem and it talks to the pinpad through
> a dedicated bus. So I accessed it through io space.

In that case, you'll likely want something like io0200/input0, where
0x200 would be the io address of the device. On the other hand, if it's
really embedded and there can't be two pinpads in the system, it's not a
problem to use basically any string there, since it only needs to be
system-unique.

-- 
Vojtech Pavlik
SuSE Labs, SuSE CR
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/