22 Sep, 2014

1 commit


30 Aug, 2014

1 commit


26 Aug, 2014

1 commit


07 Jul, 2014

2 commits


04 Jul, 2014

1 commit


22 May, 2014

1 commit


26 Apr, 2014

1 commit


29 Mar, 2014

1 commit

  • Adding MPU6500 in target list for this driver.

    Description:
    Source
    Document: MPU-6500 Register Map and Descriptions Revision 2.1
    Section 3: Register Map

    This section describes difference in terms device programmability
    between MPU6050 and MPU6500.
    These are different registers, which differs between MPU6050 and
    MPU6500.

    Addr Name
    ---------------------
    1E LP_ACCEL_ODR
    6C PWR_MGMT_2
    77 XA_OFFSET_H
    78 XA_OFFSET_L
    7A YA_OFFSET_H
    7B YA_OFFSET_L
    7D ZA_OFFSET_H
    7E ZA_OFFSET_L

    But the current MPU6050 driver doesn't use registers which are different
    except PWR_MGMT_2. The difference is support of "LP_WAKE_CTRL" at bit6-7
    in MPU6050 mode. In MPU6500 they are not defined.
    In current mpu6050 driver, only values used for this register are for
    standby mode for gyro and accelerometer.
    In both case frequency of wakeups is set to default and not using
    bit 6-7.

    So this driver van as well support MPU6500. In addition MPU6500 can
    run MPU6050 mode by changing device trim settings.

    So changing config comments to allow MPU6500 to use this driver.
    When the driver is enhanced to support more functions, i2c driver
    data INV_MPU6500 or "WHO_AM_I" register can be used to add additional
    functionality.

    Signed-off-by: Srinivas Pandruvada
    Signed-off-by: Jonathan Cameron

    Srinivas Pandruvada
     

12 Feb, 2014

1 commit

  • …/iio into staging-next

    Jonathan writes:

    First set of new drivers and cleanups for IIO in the 3.15 cycle.

    New drivers:
    * si7005 relative humidity and temperature sensor
    * Lite-on ltr501 ambient light and proximity sensor

    Cleanups
    * Clean up some dead comments in max1363
    * Drop some obsolete variables in adjd_s311 and tcs3472 left over from
    the introduction of iio_push_to_buffers_with_timestamp.
    * Drop some unneeded linux/init.h includes
    * Squish a sparse warning in mpl3115 by correctly specifying a be32 variable.
    * A number of cleanups and fixes for sca3000
    * Drop an unneed checks in mxs-lradc, ad7303 and adis16400.
    * Drop a platform_set_drvdata in viperboard after the only use of it was
    removed during a devm conversion.
    * Add a missing device name for ak8975 to comply with the ABI.
    * Put mpu6050 into the IMU menu as it slipped out into the main menu.
    * Fix a typo and some comment formatting in mpu6050.
    * Document at91 ADC clock properties.

    Greg Kroah-Hartman
     

08 Feb, 2014

3 commits


04 Feb, 2014

1 commit


11 Jan, 2014

1 commit


18 Dec, 2013

1 commit

  • A single channel in this driver was using the IIO_ST macro.
    This does not provide a parameter for setting the endianness of
    the channel. Thus this channel will have been reported as whatever
    is the native endianness of the cpu rather than big endian. This
    means it would be incorrect on little endian platforms.

    Signed-off-by: Jonathan Cameron
    Acked-by: Lars-Peter Clausen
    Cc: stable@vger.kernel.org

    Jonathan Cameron
     

22 Sep, 2013

3 commits


04 Aug, 2013

5 commits


26 Mar, 2013

2 commits

  • Introduce iio_tigger_{set,get}_drvdata which allows to attach driver specific
    data to a trigger. The functions wrap access to the triggers private_data field
    and all current users are updated to use iio_tigger_{set,get}_drvdata instead of
    directly accessing the private_data field. This is the first step towards
    removing the private_data field from the iio_trigger struct.

    The following coccinelle script has been used to update the drivers:

    @@
    struct iio_trigger *trigger;
    expression priv;
    @@
    -trigger->private_data = priv
    +iio_trigger_set_drv_data(trigger, priv)

    @@
    struct iio_trigger *trigger;
    @@
    -trigger->private_data
    +iio_trigger_get_drv_data(trigger)

    Signed-off-by: Lars-Peter Clausen
    Signed-off-by: Jonathan Cameron

    Lars-Peter Clausen
     
  • …/iio into staging-next

    Jonathan writes:

    First set of IIO new drivers and cleanup for the 3.10 cycle.

    New stuff

    1) Add OF support for specifying mappings between iio devices and their
    in kernel consumers.
    2) Driver for AD7923 (extra functionality and support for ad7904, ad7914 and
    ad7924 added later in series)
    3) Driver for Exynos adc (dt suppor for phy added later in series).
    4) Make iio_push_event save IRQ context - necessary if it is to be used
    within an interrupt handler. Users of this functionality to follow.
    5) For iio use the device tree node name to provide the hwmon name attribute
    if available.

    Removal and moves out of staging

    1) Drop the adt7410 driver from IIO now that there is a hmwon driver with
    equivalent support. This device is very much targeted at hardware
    monitoring so hwmon is a more appropriate host for the driver.
    2) Move iio_hwmon driver to drivers/hwmon.

    Cleanups

    1) Minor cleanup in ST common library.
    2) Large set of patches to break the info_mask element which previously used
    odd and even bits to specify if a channel attribute was either shared across
    similar channels or specific to only one. Now we have two bitmaps, one for
    those parameters that are specific to this channel and one for those shared
    by all channels with the same type as this one. This has no effect on the
    userspace abi. It simplifies the core code and provides more space for new
    channel parameters. It has been on the todo list for a long time!

    Conflicts:
    drivers/iio/dac/ad5064.c

    Greg Kroah-Hartman
     

18 Mar, 2013

4 commits


03 Mar, 2013

1 commit

  • Fix:

    drivers/iio/imu/inv_mpu6050/inv_mpu_ring.c: In function ‘inv_mpu6050_read_fifo’:
    drivers/iio/imu/inv_mpu6050/inv_mpu_ring.c:176:3: error: implicit declaration of
    function ‘iio_push_to_buffers’ [-Werror=implicit-function-declaration]

    Signed-off-by: Guenter Roeck
    Signed-off-by: Jonathan Cameron

    Guenter Roeck
     

11 Feb, 2013

1 commit


26 Jan, 2013

5 commits

  • The adis16448 is more or less from the same family of devices as supported by
    this driver. It features three acceleration channels, three angular velocity
    channels, three magnetometer channels, one temperature channels and one
    barometric pressure channel.

    Signed-off-by: Lars-Peter Clausen
    Signed-off-by: Jonathan Cameron

    Lars-Peter Clausen
     
  • Expose some information useful for debugging a device in debugfs. This includes
    for now the flash count, the product id and the serial number and raw register
    access.

    Signed-off-by: Lars-Peter Clausen
    Signed-off-by: Jonathan Cameron

    Lars-Peter Clausen
     
  • The adis16400 and similar have two different base sampling rate available, from
    which the actual sampling rate is derived. 1638 Hz and 52.85 Hz, switching to
    the lower base sampling rate allows to support lower sampling rates.

    This patch adds support for switching to the lower base sampling rate if the
    requested sampling frequency is outside of the range which can be supported by
    the higher base sampling rate.

    The function which is used to read the current sampling rate already has support
    for the lower sampling rate, so no changes are required there.

    Signed-off-by: Lars-Peter Clausen
    Signed-off-by: Jonathan Cameron

    Lars-Peter Clausen
     
  • The devices supported by this drivers support sample rates with less than one
    sample per second. To support this increase the samplerate precession to allow
    setting (and reading) the samplerate with a milli-HZ precession.

    Signed-off-by: Lars-Peter Clausen
    Signed-off-by: Jonathan Cameron

    Lars-Peter Clausen
     
  • This adis16400 driver is in pretty good shape now, so move it out of staging.

    Signed-off-by: Lars-Peter Clausen
    Signed-off-by: Jonathan Cameron

    Lars-Peter Clausen
     

30 Nov, 2012

2 commits

  • Remove duplicated include.

    Signed-off-by: Wei Yongjun
    Signed-off-by: Jonathan Cameron

    Wei Yongjun
     
  • Smatch complains that snprintf() returns the number of characters,
    not counting the NUL terminator, which *would* have been printed if
    there were enough space. In other words the return value could be more
    than sizeof(buf).

    In this case, we are printing something like "ff.ff\n" which is at most
    6 characters and a NUL so that's not an issue. I changed snprintf() to
    scnprintf() to silence the warning.

    But since the buffer doesn't include space for the NUL terminator, we
    need to make it bigger or the "\n" will be truncated off.

    Signed-off-by: Dan Carpenter
    Acked-By: Lars-Peter Clausen
    Signed-off-by: Jonathan Cameron

    Dan Carpenter
     

21 Nov, 2012

1 commit