- 14 Sep, 2014 16 commits
-
-
Peter Meerwald authored
the BMA250 has only 10-bit resolution; while the data readout registers have identical layout, the configuration is completely different compared to the BMA180 datasheet: http://ae-bst.resource.bosch.com/media/products/dokumente/bma250/BST-BMA250-DS002-05.pdfSigned-off-by:
Peter Meerwald <pmeerw@pmeerw.net> Cc: Oleksandr Kravchenko <o.v.kravchenko@globallogic.com> Signed-off-by:
Jonathan Cameron <jic23@kernel.org>
-
Peter Meerwald authored
makes it easier to add more chip variants and removes redundancy: scales and frequencies are now stated just once Signed-off-by:
-
Peter Meerwald authored
allow to specify channels resolution and compute shift assuming 16-bit registers and MSB allocation Signed-off-by:
-
Peter Meerwald authored
move part of bma180_init() to bma180_config() (split initialization and configuration code); configuration is heavily chip-specific Signed-off-by:
-
Peter Meerwald authored
Signed-off-by:
-
Peter Meerwald authored
statically allocate maximum size Signed-off-by:
-
Peter Meerwald authored
8-bit signed; 0 LSB @ 24 °C, 0.5 °C per LSB Signed-off-by:
-
Peter Meerwald authored
Signed-off-by:
-
Peter Meerwald authored
Signed-off-by:
-
Peter Meerwald authored
and minor cleanups Signed-off-by:
-
Peter Meerwald authored
Signed-off-by:
-
Irina Tirdea authored
Add support for the BMI055 gyroscope sensor. BMI055 is a package consisting of an acceleration sensor and a gyroscope. This patch adds support for the gyroscope only. Spec downloaded from: http://ae-bst.resource.bosch.com/media/products/dokumente/bmi055/BST-BMI055-DS000-06.pdf The BMI055 gyroscope uses the same register definition as BMG160, but does not specify a temp register. However, the temp register seems to be working in the same way as for BMG160, so this patch does not remove the temp channel for BMI055. Signed-off-by:
Irina Tirdea <irina.tirdea@intel.com> Reviewed-by:
Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com> Signed-off-by:
-
Daniel Baluta authored
Noticed when compiling with CONFIG_PM_RUNTIME not set: kxcjk-1013.c: warning: ‘kxcjk1013_get_startup_times’ defined but not used [-Wunused-function] Introduced by commit 124e1b1d (iio: accel: kxcjk-1013: support runtime pm). Signed-off-by:
Daniel Baluta <daniel.baluta@intel.com> Reviewed-by:
-
Irina Tirdea authored
Use const char* instead of casting const char* to char*. Signed-off-by:
-
Irina Tirdea authored
When CONFIG_PM_RUNTIME is not defined and bmg160 tries to power off the device, bmg160_set_power_state will call pm_runtime_put_autosuspend, which is not implemented (wil return -ENOSYS). Only call bmg160_set_power_state when CONFIG_PM_RUNTIME is defined. Signed-off-by:
Hartmut Knaack <knaack.h@gmx.de> Signed-off-by:
-
Daniel Baluta authored
This patch adds support for KXTJ2-1009 3-axis acceleromenter sensor. KXTJ2-1009 uses the same register definitions as KXCJK-1013. The specification for KXTJ2-1009 can be downloaded from: http://www.kionix.com/sites/default/files/KXTJ2-1009%20Specifications%20Rev%204.pdfReviewed-by:
-
- 13 Sep, 2014 2 commits
-
-
Laurentiu Palcu authored
The following chips are either similar or have only the resolution different. Hence, change this driver to support these chips too: BMI055 - combo chip (accelerometer part is identical to BMC150's) BMA255 - identical to BMC150's accelerometer BMA222E - 8 bit resolution BMA250E - 10 bit resolution BMA280 - 14 bit resolution Additionally: * add bmc150_accel_match_acpi_device() function to check that the device has been enumerated through ACPI; * rename bmc150_accel_acpi_gpio_probe() to bmc150_accel_gpio_probe() since the ACPI matching has been moved to the new function. Also, this will allow for the GPIO matching to be done against a device tree too, not only ACPI tree; * rename bmc150_scale_info struct member 'range' to 'reg_range' to be consistent with the naming convention used elsewhere in the driver and declare it u8, instead of int; * change CONFIG description to list all supported chips; Signed-off-by:
Laurentiu Palcu <laurentiu.palcu@intel.com> Acked-by:
-
Laurentiu Palcu authored
Add support for enumerating the device through ACPI. Signed-off-by:
-
- 10 Sep, 2014 1 commit
-
-
Daniel Baluta authored
Minimal implementation. This driver provides raw illuminance readings. This is based on drivers/hwmon/al3320.c (*) driver from msm tree written by Tsechih Lin <Tsechih_Lin@asus.com> * https://android.googlesource.com/kernel/msm.gitSigned-off-by:
-
- 31 Aug, 2014 1 commit
-
-
Sören Brinkmann authored
Fix the checkpatch complaint regarding unnecessary line continuation. WARNING: Avoid unnecessary line continuations #143: FILE: ad7606_core.c:143: Signed-off-by:
Sören Brinkmann <soeren.brinkmann@gmail.com> Signed-off-by:
-
- 30 Aug, 2014 10 commits
-
-
Daniel Baluta authored
This patch adds support for KXCJ9-1008 3-axis acceleromenter sensor. KXCJ9-1008 uses the same register definitions as KXCJK-1013. The specification for KXCJ9-1008 can be downloaded from: http://www.kionix.com/sites/default/files/KXCJ9-1008%20Specifications%20Rev%205.pdfSigned-off-by:
-
Heiko Stübner authored
This add the necessary binding documentation for the saradc found in all recent processors from Rockchip. Signed-off-by:
Heiko Stuebner <heiko@sntech.de> Signed-off-by:
-
Laurentiu Palcu authored
When CONFIG_PM_RUNTIME is not set, the following issues are seen: * warning message at compilation time: warning: 'bmc150_accel_get_startup_times' defined but not used [-Wunused-function] * bmc150_accel_set_power_state() will always fail and reading the accelerometer data is impossible; This occurs because of the call to pm_runtime_put_autosuspend calls __pm_runtime_suspend which returns -ENOSYS. This commit fixes these. Signed-off-by: -
Laurentiu Palcu authored
According to documentation ([1] - page 27), the range for 16G is 7.81mg/LSB. Converted to SI, this is: 7.81 * 10^-3 * 9.80665 m/s^2 / LSB = 0.0765899365 m/s^2 / LSB [1] http://ae-bst.resource.bosch.com/media/products/dokumente/bmc150/BST-BMC150-DS000-04.pdfSigned-off-by: -
Laurentiu Palcu authored
Intersil chips ISL29018, ISL29023 and ISL29035 are very similar. They're all ambience light sensors. The ISL29018, however, is also a proximity sensor. The registers are similar too: -------------+----------+---------- AVAILABLE IN | ADDR REG | NAME 290xx | | -------------+----------+---------- 18/23/35| 00h| COMMANDI 18/23/35| 01h| COMMANDII (B4-7 are used only in 29018 for proximity) 18/23/35| 02h| DATALSB 18/23/35| 03h| DATAMSB 18/23/35| 04h| INT_LT_LSB 18/23/35| 05h| INT_LT_MSB 18/23/35| 06h| INT_HT_LSB 18/23/35| 07h| INT_HT_MSB 18/23| 08h| TEST 35| 0Fh| ID -------------+----------+----------- So, this patch will add support for ISL29023 and ISL29035 to the existing isl29018 driver. Since these 2 chips don't have proximity detection, the proximity sysfs attribute is not needed. Also, for ISL29035, since it has an ID register, make use of it in order to properly detect the chip and clear the brownout bit. Signed-off-by: -
Laurentiu Palcu authored
isl29108 was used, instead of isl29018. Signed-off-by:
-
Lee Jones authored
Value from st_sensors_set_drdy_int_pin() is assigned to err here, but that stored value is not used before it is overwritten. To fix this we're enforcing a check on st_sensors_set_drdy_int_pin()'s return value and if it's an error, we're returning right away. Cc: jic23@kernel.org Cc: linux-iio@vger.kernel.org Signed-off-by:
Lee Jones <lee.jones@linaro.org> Signed-off-by:
-
Josh Wu authored
The handle_adc_eoc_trigger() in only used in at91_adc.c. So make it static. Signed-off-by:
Josh Wu <josh.wu@atmel.com> Acked-by:
Nicolas Ferre <nicolas.ferre@atmel.com> Signed-off-by:
-
Heiko Stübner authored
The rate variable in the probe function of the saradc is a remnant of a previous patch iteration. It is unused and thus produces a compile time warning. Therefore remove it. Signed-off-by:
-
Jingoo Han authored
Casting the return value which is a void pointer is redundant. The conversion from void pointer to any other pointer type is guaranteed by the C programming language. Signed-off-by:
Jingoo Han <jg1.han@samsung.com> Signed-off-by:
-
- 26 Aug, 2014 10 commits
-
-
Sanjeev Sharma authored
This patch removes the .owner field for drivers which use the platform_driver_register api because this is overriden in _platform_driver_register. Signed-off-by:
Sanjeev Sharma <Sanjeev_Sharma@mentor.com> Signed-off-by:
-
Srinivas Pandruvada authored
This chip has a motion detect capability. Using IIO events to specify thresholds and pushing events. In addition a new trigger of type any-motion is added, which pushes data to buffer only when there is any movement. Change list: Comments addressed for Re: [PATCH 5/6] iio: accel: kxcjk-1013: Support thresholds Date: 07/20/2014 - Both motion detect and data ready can be enabled together - Sending RISING/FALLING events based on int status - Separate interrupt configuration for data ready and motion detect Signed-off-by:
-
Daniel Baluta authored
data->range is already set by kxcjk1013_set_range. Signed-off-by:
-
Srinivas Pandruvada authored
Added any-motion trigger documentation. Signed-off-by:
-
Srinivas Pandruvada authored
This change implements support for BMG160 Gyro sensor. Although chip has several advanced features, this change implements minimum set required for using gyro sensor. Signed-off-by:
-
Benjamin Romer authored
The function uisutil_copy_fragsinfo_from_skb() in uisutils.c is messy and over-indented. This patch fixes the function's indentation so it is cleaner. Signed-off-by:
Benjamin Romer <benjamin.romer@unisys.com> Signed-off-by:
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
-
Benjamin Romer authored
Fix the missing blank line between code and declarations in uisthread.c. Signed-off-by:
-
Benjamin Romer authored
Remove the extraneous return from the uislib module exit function. Signed-off-by:
-
Benjamin Romer authored
The destroy_bus() function is heavily indented and many lines extend past the right margin. This patch simplifies the function without changing its effects. Signed-off-by:
-
Benjamin Romer authored
Fix the line spacing between code and local variables in uislib.c. Signed-off-by:
-
