Re: private ioctls in input driver

[Dmitry Torokhov <dmitry.torokhov@gmail.com>]

On Fri, Sep 25, 2009 at 02:21:40PM +0530, Trilok Soni wrote:
> Hi Dmitry,
> 
> On Fri, Sep 25, 2009 at 9:32 AM, Dmitry Torokhov
> <dmitry.torokhov@gmail.com> wrote:
> > Hi Trilok,
> >
> > On Thu, Sep 24, 2009 at 05:21:09PM +0530, Trilok Soni wrote:
> >> Hi Dmitry,
> >>
> >> Is there any way of creating private ioctls in the input driver? I see
> >> that all the input framework handled
> >> by the framework itself and there is no way to call private ioctls if
> >> it doesn't match the standard ones.
> >>
> >
> > You are right, event devices only allow standard ioctl. What kind of
> > ictl are you considering? Normally device-specific controls are done via
> > sysfs attached to the parent device (see atkbd, psmouse, etc).
> 
> sysfs might good for purpose when you can associate one file per
> value, so for more data we can't simply create one file per the data.
> Say five fingers touch data (I know we have MT_* support but here it
> is just for example) , say id, x, y, z etc., per finger, then we can't
> create one file for each of them.

Maybe use configfs if sysfs is not suitable? I am not sure.

I would like to not-have driver-specific ioctls in evdev/input core but
rather keep them with device/driver itself. Input core should only have
stuff that makes sense for multiple devices.

-- 
Dmitry