- 20 Sep, 2013 1 commit
-
-
Thomas Meyer authored
sizeof when applied to a pointer typed expression gives the size of the pointer. Found by coccinelle spatch "misc/noderef.cocci" Signed-off-by:
Thomas Meyer <thomas@m3y3r.de> Signed-off-by:
Jonathan Cameron <jic23@kernel.org>
-
- 18 Sep, 2013 2 commits
-
-
Peter Meerwald authored
Signed-off-by:
Peter Meerwald <pmeerw@pmeerw.net> Acked-by:
Lars-Peter Clausen <lars@metafoo.de> Signed-off-by:
-
Peter Meerwald authored
adding one return value check fix one kerneldoc Signed-off-by:
-
- 16 Sep, 2013 1 commit
-
-
Lars-Peter Clausen authored
The max1361 driver uses the same callbacks as the triggered buffer default buffer setup ops, so just remove the max1361 specific ops and let it use the default ops. Signed-off-by:
-
- 15 Sep, 2013 15 commits
-
-
Lars-Peter Clausen authored
Now that iio_push_to_buffers() takes a void pointer for the data parameter we can remove those casts to u8*. Signed-off-by:
-
Lars-Peter Clausen authored
Now that iio_push_to_buffers() takes a void pointer for the data parameter we can remove those casts to u8*. Signed-off-by:
-
Lars-Peter Clausen authored
Change the type of the 'data' parameter for iio_push_to_buffers() from 'u8 *' to 'const void *'. Drivers typically use the correct type (e.g. __be16 *) for their data buffer. When passing the buffer to iio_push_to_buffers() it needs to be cast to 'u8 *' for the compiler to not complain (and also having to add __force if we want to keep sparse happy as well). Since the buffer implementation should not care about the data layout (except the size of one sample) using a void pointer is the correct thing to do. Also make it const as the buffer implementations are not supposed to modify it. Signed-off-by:
-
Lars-Peter Clausen authored
The iio_cb_access struct is never modified so we can mark it as const. Signed-off-by:
-
Peter Meerwald authored
and drop obsolete #define Signed-off-by:
-
Jonathan Cameron authored
Doing this makes it possible to access this control from within the kernel. Signed-off-by:
-
Jonathan Cameron authored
Note that as this driver has output as well as output channels an example of info_mask_shared_by_all that makes any sense does not exist. Signed-off-by:
-
Jonathan Cameron authored
These two additional info_mask bitmaps should allow all 'standard' numeric attributes to be handled using the read_raw and write_raw callbacks. Whilst this should reduce code, the more important element is that this makes these values easily accessible to in kernel users of IIO devices. Signed-off-by:
-
Jonathan Cameron authored
Introduce an enum to specify whether the attribute is separate or shared. Factor out the bitmap handling for loop into a separate function. Tidy up error handling and add a NULL assignment to squish a false positive warning from GCC. Change ext_info shared type from boolean to enum and update in all drivers. Signed-off-by:
-
Jonathan Cameron authored
Somehow this got missed when dropping all the code that used it prior to the split. Remove it now, there are no users. Signed-off-by:
-
Lars-Peter Clausen authored
Use wake_up_interruptible_poll() instead of wake_up_interruptible() to only wake up those threads that listen for input poll notifications. Signed-off-by:
-
Lars-Peter Clausen authored
We can skip having to loop through all the device's buffers to see if a certain buffer is active, if we let the buffer's list head point to itself when the buffer is inactive. Signed-off-by:
-
Yann Droneaud authored
IIO uses anon_inode_get() to allocate file descriptors as part of its ioctls. But those ioctls are lacking a flag argument allowing userspace to choose options for the newly opened file descriptor. In such case it's advised to use O_CLOEXEC by default so that userspace is allowed to choose, without race, if the file descriptor is going to be inherited across exec(). KVM usage of anon_inode_getfd() was fixed in a previous patchset [1], so IIO is the only subsystem using anon_inode_getfd() with a fixed set of flags not including O_CLOEXEC. This patch set O_CLOEXEC flag on the event file descriptor created with anon_inode_getfd() to not leak file descriptors across exec(). Links: - Secure File Descriptor Handling (Ulrich Drepper, 2008) http://udrepper.livejournal.com/20407.html - Excuse me son, but your code is leaking !!! (Dan Walsh, March 2012) http://danwalsh.livejournal.com/53603.html - [1] kvm: use anon_inode_getfd() with O_CLOEXEC flag http://lkml.kernel.org/r/cover.1377372576.git.ydroneaud@opteya.comSigned-off-by:
Yann Droneaud <ydroneaud@opteya.com> Signed-off-by:
-
Jacek Anaszewski authored
Add a new driver for the ambient light/proximity sensor device. The driver exposes three channels: light_clear light_ir and proximity. It also supports triggered buffer, high and low ambient light threshold event and proximity detection events. Signed-off-by:
Jacek Anaszewski <j.anaszewski@samsung.com> Signed-off-by:
Kyungmin Park <kyungmin.park@samsung.com> Signed-off-by:
-
Jacek Anaszewski authored
This patch adds device tree binding documentation for the gp2ap020a00f proximity/als sensor. Signed-off-by:
Stephen Warren <swarren@nvidia.com> Signed-off-by:
-
- 14 Sep, 2013 21 commits
-
-
Peter Meerwald authored
chip has four 16-bit channels for red, green, blue, clear color intensity; driver supports the TCS3x7x family of devices and was tested with a TCS34725 chip; further information here: http://www.ams.com/eng/Products/Light-Sensors/Color-Sensor/TCS34725 v2 (thanks to Jonathan Cameron): * drop dynamic buffer allocation, buffer is in tcs3472_data * limit sysfs output to PAGE_SIZE * check val2 == 0 when writing CALIBSCALE Signed-off-by:
-
Lee Jones authored
At the moment the number of channels specified is dictated by the first sensor supported by the driver. As we add support for more sensors this is likely to vary. Instead of using the ARRAY_SIZE() of the LPS331AP's channel specifier we'll use a new adaptable 'struct st_sensors' element instead. Signed-off-by:
Lee Jones <lee.jones@linaro.org> Acked-by:
Denis Ciocca <denis.ciocca@st.com> Signed-off-by:
-
Lee Jones authored
Due to the MACRO used, the task of reading, understanding and maintaining the LPS331AP's channel descriptor is substantially difficult. This patch is based on the view that it's better to have easy to read, maintainable code than to save a few lines here and there. For that reason we're expanding the array so initialisation is completed in full. Signed-off-by:
-
Lee Jones authored
They're currently named *_1_*, for 'Sensor 1', but the code will be much more readable if we use the naming convention *_LPS331AP_* instead. Signed-off-by:
-
Lee Jones authored
Saving a few lines of code. Signed-off-by:
-
Lee Jones authored
Some chips either don't support it or fail to provide adequate documentation, so sometimes it's impossible to enable the feature even if it is supported. Signed-off-by:
-
Peter Meerwald authored
driver for the TSL4531 family of 16-bit I2C ambient light sensors; information is here: http://www.ams.com/eng/Products/Light-Sensors/Ambient-Light-Sensor-ALS/TSL45315 the chip offers simple lux output v3 (thanks Lars-Peter Clausen): * add mutex to when updating integration time * fix chip ID checking * code cleanups v2: * rename to tsl4351 * use INT_TIME Signed-off-by:
-
Peter Meerwald authored
Signed-off-by:
-
Peter Meerwald authored
Integration time is in seconds; it controls the measurement time and influences the gain of a sensor. There are two typical ways that scaling is implemented in a device: 1) input amplifier, 2) reference to the ADC is changed. These both result in the accuracy of the ADC varying (by applying its sampling over a more relevant range). Integration time is a way of dealing with noise inherent in the analog sensor itself. In the case of a light sensor, a mixture of photon noise and device specific noise. Photon noise is dealt with by either improving the efficiency of the sensor, (more photons actually captured) which is not easily varied dynamically, or by integrating the measurement over a longer time period. Note that this can also be thought of as an averaging of a number of individual samples and is infact sometimes implemented this way. Altering integration time implies that the duration of a measurement changes, a fact the device's user may be interested in. Hence it makes sense to distinguish between integration time and simple scale. In some devices both types of control are present and whilst they will have similar effects on the amplitude of the reading, their effect on the noise of the measurements will differ considerably. Used by adjd_s311, tsl4531, tcs3472 The following drivers have similar controls (and could be adapted): * tsl2563 (integration time is controlled via CALIBSCALE among other things) * tsl2583 (has integration_time device_attr, but driver doesn't use channels yet) * tsl2x7x (has integration_time attr) Signed-off-by:
-
Sachin Kamat authored
devm_iio_device_alloc makes code simpler. Signed-off-by:
Sachin Kamat <sachin.kamat@linaro.org> Cc: Barry Song <21cnbao@gmail.com> Signed-off-by:
-
Sachin Kamat authored
devm_iio_device_alloc makes code simpler. Signed-off-by:
-
Sachin Kamat authored
devm_iio_device_alloc makes code simpler. Signed-off-by:
-
Sachin Kamat authored
devm_iio_device_alloc makes code simpler. Signed-off-by:
-
Sachin Kamat authored
devm_iio_device_alloc makes code simpler. Signed-off-by:
-
Sachin Kamat authored
devm_iio_device_alloc makes code simpler. Signed-off-by:
-
Sachin Kamat authored
devm_iio_device_alloc makes code simpler. Signed-off-by:
-
Sachin Kamat authored
dev_err is preferred over pr_err. Signed-off-by:
-
Sachin Kamat authored
devm_* APIs are device managed and make code simpler. This patch also fixes the missing gpio_free call in remove. Signed-off-by:
-
Sachin Kamat authored
'break' after return is redundant. Remove it. Signed-off-by:
-
Sachin Kamat authored
'break' after return is redundant. Remove it. Signed-off-by:
-
Sachin Kamat authored
'break' after return is redundant. Remove it. Signed-off-by:
-
