[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20110706115430.3745592c@bob.linux.org.uk>
Date: Wed, 6 Jul 2011 11:54:30 +0100
From: Alan Cox <alan@...ux.intel.com>
To: Nathan Royer <nroyer@...ensense.com>
Cc: Jonathan Cameron <jic23@....ac.uk>,
Andrew Morton <akpm@...ux-foundation.org>,
Greg Kroah-Hartman <gregkh@...e.de>,
Jiri Kosina <jkosina@...e.cz>,
Jean Delvare <khali@...ux-fr.org>,
linux-kernel@...r.kernel.org, linux-input@...r.kernel.org,
Chris Hudson <chudson@...nix.com>, eric.andersson@...xphere.com
Subject: Re: [PATCH 01/11] misc: inv_mpu primary header file and README
file.
> It seems that some sensors are in input and but that most are in iio.
> Obviously I don't want to dissent with both and put ours in misc, so
> how do we make this better? Should we work on cleaning this up. If
> so should we start moving the drivers that are in input to iio.
IIO provides a lot more flexibility and is rather newer, input provides
a more focussed interface. In some cases it may make sense to provide
different interfaces to each (eg atomspheric pressure doesn't fit well
into input, but 3 axis accelerometers fit perfectly)
> We still need a way to read and write registers and DMP memory during
> runtime from user space.
You probably want a driver for the MPU itself whih provides the
needed glue and also control interfaces (firmware load etc). That may
well be a drivers/misc item as I imagine that part is quite unique and
specialised.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists