22 Mar, 2014

1 commit

  • During probe the driver allocates dummy I2C devices (i2c_new_dummy())
    but they aren't unregistered during driver remove or probe failure.

    Additionally driver does not check the return value of i2c_new_dummy().
    In case of error (i2c_new_device(): memory allocation failure or I2C
    address cannot be used) this function returns NULL which is later
    dereferenced by i2c_smbus_{read,write}_data() functions.

    Fix issues by properly checking for i2c_new_dummy() return value and
    unregistering I2C devices on driver remove or probe failure.

    Signed-off-by: Krzysztof Kozlowski
    Acked-by: Beomho Seo
    Cc: stable@vger.kernel.org
    Signed-off-by: Jonathan Cameron

    Krzysztof Kozlowski
     

18 Feb, 2014

1 commit

  • This patch is fixed [read/write] integration time function.
    cm36651 have integration time from 1 to 640 milliseconds.
    But, print more then the thousand second. when call *_integration_time attribute.
    Because read_integration_time function return IIO_VAL_INT.
    read integration time function is changed return IIO_VAL_INT_PLUS_MICRO;
    And then .write_raw_get_fmt callback function for parse a fixed-point number from a string.
    Some description is revised milliseconds unit.

    v2: cm36651_write_int_time function fixed as it was.

    Signed-off-by: Beomho Seo
    Signed-off-by: Jonathan Cameron

    Beomho Seo
     

25 Dec, 2013

1 commit

  • …/iio into staging-next

    Jonathan writes:

    2nd round of new IIO drivers, features and cleanups for the 3.14 cycle.

    New drivers

    * HID inclinometer driver.

    * DHT11 humidity driver. Note that previous humidity drivers have been in
    hwmon, but no one was ever entirely happy with that, and they should find
    a more comfortable home in IIO (their original placement in hwmon was my
    fault - oops). As this is our first humidity driver, core support is also
    added.

    New features

    * Two of mxs-lradc channels are internally wired to a temperature sensor,
    make this explicit in the driver by providing the relevant temperature
    channel.

    * Add support for blocking IO on buffers.

    * Add a data_available call back to the interface between buffer implementations
    and the core. This is much cleaner than the old, 'stufftoread' flag.
    Implemented in the kfifo buffer.

    Cleanups

    * Last user of the old event configuration interface is converted and the
    old interface dropped. Nice to be rid of this thanks to Lars-Peter's hard
    work!

    * Replace all remaining instances of the IIO_ST macro with explicit filling
    of the scan_type structure within struct iio_chan_spec. This macro was a
    bad idea, that rapidly ceased to cover all elements of the structure.
    Miss reading of the macro arguements has led to a number of bugs so lets
    just get rid of it. The final removal patch is awaiting for some fixes
    to make their way into mainline.
    In a couple of drivers, no elements of scan_type were even being used so
    in those case, it has been dropped entirely.

    * Drop a couple of of_match_ptr helper uses in drivers where devicetree is
    not optional and hence the structures being protected by this always exist.

    * Fix up some cases where data was read from a device in a particular
    byte order, but he code placed it into a s16 or similar. These were
    highlighted by Sparse.

    * Use the new ATTRIBUTE_GROUPS macro to drop some boiler plate in the triggers
    core code.

    * ad7746 and ad7280a - stop storing buffers on the stack, giving cleaner code
    and possibly avoiding issues with i2c bus drivers that assume they can dma
    directly into the buffer. Note that this cannot currently happen as the the
    i2c_smbus_read_i2c_block_data function has a memcpy from the buffer actually
    passed to the bus driver. I missed this element of the commit message
    and don't think it is major enough to rebase the iio tree.

    * ad5791 and ad5504 stop storing buffers on the stack for an SPI driver.
    Unlike the i2c drivers, this is a real issue for SPI drivers which can dma
    directly into the buffer supplied.

    Greg Kroah-Hartman
     

23 Dec, 2013

1 commit


16 Dec, 2013

1 commit


08 Dec, 2013

2 commits


18 Oct, 2013

1 commit