Thank you for your comments, I'm just getting started with IIO so it's all good stuff... >> +++++++++++++++++++++++++++++++++++++++++++++++++ > Hmm. This driver is already a substantial mash up of a number of different > types of driver (as far as linux is concerned), with input, battery and > led > drivers. Might be worth considering a more formal MFD approach as it'll > break the driver up into a number of sub components that will then sit > in the various subsystems in a cleaner fashion. > Just a thought! Might be, but that sounds like more work ;-) If pushing some ideas around prompts that, it can't be a bad thing.... right? >> + case IIO_CHAN_INFO_SCALE: >> + switch (chan->type) { > If the scale really is 1 then don't export it. Note the units would > have to be in m/s^2 which seems unlikely though. I'm guessing this > is a placeholder.. Yes place holder, different controllers (SixAxis, DS4 and PSMove) have different values. In the far future I'd hope to use the per-device calibration stored on the PSMove. https://github.com/nitsch/moveonpc/wiki/Calibration-data >> +static const struct iio_chan_spec sony_sixaxis_channels[] = { >> + SONY_ACC_CHANNEL(X), >> + SONY_ACC_CHANNEL(Y), >> + SONY_ACC_CHANNEL(Z), > No gyro channels yet? > Just to note, if the gyro frequency etc is different from the > accelerometer > (pretty common) then you'll want to register two IIO devices rather than > just the one so that the control and buffers are separate. I have a vague memory that the SixAxis has a 1-ch gyro but this is not showing on hidraw (might be 'hidden' behind MultiTouch ID/Bug). The DS4 has Accel/Gyros, and the PSMove has Accel/Gyro/Mag. I didn't expose the mags over input/joystick axis as I didn't want to corrupt stream the PSMoveAPI (it needs to be re-ordered) and it's unlikely anyone would actually use via joystick. The PSMove's report actually contains 2 frames assumed to be 1/2 sample rate apart for the Accel/Gyro, but only one Mag reading. I have further advanced the patch to include reading via buffer, but I'm having trigger 'conceptual' problems getting my head around the HID device issuing an interrupt when a input report is received. Looking at iio_dummy_event and iios_sysfs for inspiration.... On the assumption that there will be multiple devices (either same type or with different HID drivers) all trying to issue triggers, we'd need to be a little careful. Is there a 'short-cut' we can use if a HID device is only required to trigger itself (and not other iio devices)? ie. not need true interrupt system. Simon. -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html