- May 07, 2015
-
-
Linus Walleij authored
Not all sensors support BDU (block data update) and in fact a bunch of the in-kernel sensor settings do not specify the BDU address field. Make this optional. Signed-off-by:
Linus Walleij <linus.walleij@linaro.org> Signed-off-by:
Jonathan Cameron <jic23@kernel.org>
-
Linus Walleij authored
Some sensors such as magnetometers and pressure sensors doesn't have interrupts at all, and thus no DRDY setting applies. Make the assignment of an interrupt optional, and do not call st_sensors_set_drdy_int_pin() if there is no drdy (data ready) pin specified. Signed-off-by:
-
Linus Walleij authored
Print a proper error message if we're missing the trigger IRQ. Signed-off-by:
-
Antonio Ospite authored
Some extra blank lines between if checks don't hurt and improve readability. Signed-off-by:
Antonio Ospite <ao2@ao2.it> Cc: Bastien Nocera <hadess@hadess.net> Reviewed-by:
Daniel Baluta <daniel.baluta@intel.com> Signed-off-by:
-
Antonio Ospite authored
This id has been seen in the DSDT of the Teclast X98 Air 3G tablet based on Intel Bay Trail. Signed-off-by:
-
Jonathan Cameron authored
Signed-off-by:
kbuild test robot <fengguang.wu@intel.com> Cc: Vlad Dogaru <vlad.dogaru@intel.com>
-
Jonathan Cameron authored
Note this is not a bug due to the fact the region cannot be reached without the sanity check passing. The autobuilder reported it as missaligned code which is kind of true as well. Signed-off-by:
-
- May 04, 2015
-
-
Jonathan Cameron authored
Clearly the intent was to error if the value was not 0 or 1. As implemented we have (A != 0 || A != 1) which is always true as A is never both 0 and 1 at the same time. As the autobuilder suggested, && makes more sense for this error check. Reported-by:
Kuppuswamy Sathyanarayanan <sathyanarayanan.kuppuswamy@linux.intel.com> Cc: Daniel Baluta <daniel.baluta@intel.com> Signed-off-by:
-
- May 01, 2015
-
-
Roberta Dobrescu authored
This patch refactors the isl29018 driver code in order to use standard sysfs attributes for scale and integration time. ISL29018 light sensor uses four ranges and four ADC's resolutions which influence the calculated lux. Adc resolution is strongly connected to integration time and range should be controlled by scale. This patch introduces the usage of integration time and scale instead of adc resolution and range. Signed-off-by:
Roberta Dobrescu <roberta.dobrescu@gmail.com> Signed-off-by:
-
- Apr 27, 2015
-
-
Roberta Dobrescu authored
This patch renames lux_scale to calibscale and lux_uscale to ucalibscale. This is done in order to avoid confusion since these parameters are used for hardware applied calibration. Signed-off-by:
-
Roberta Dobrescu authored
This patch removes non-standard sysfs attributes range, range_available, adc_resolution and adc_resolution_available. It also removes the corresponding show and store functions. This is in preparation for using standard IIO attributes in order to move the code out of staging. Signed-off-by:
-
Irina Tirdea authored
Initial value of gpio bitnum is set to -1, but the variable is declared as unsigned. Use a positive invalid value for initial gpio bitnum. Signed-off-by:
Irina Tirdea <irina.tirdea@intel.com> Suggested-by:
Hartmut Knaack <knaack.h@gmx.de> Signed-off-by:
-
Irina Tirdea authored
Refactor code for simplicity and clarity. Signed-off-by:
-
Irina Tirdea authored
Add mma9553_ prefix to all local functions/declarations. Signed-off-by:
-
Irina Tirdea authored
Use GENMASK instead of BIT or direct value to define a mask. Signed-off-by:
-
Irina Tirdea authored
Use "GPIO" instead of "gpio" and "ACPI" instead of "acpi". Includes a couple of small style fixes in comments (missing full stop, whitespace, paranthesis). Signed-off-by:
-
Irina Tirdea authored
Use return 0 instead of return ret to mark clearly the success return path. Signed-off-by:
-
Irina Tirdea authored
When configuring gpio, we need to read initial values for activity and step count. This function may fail due to i2c read errors. Check the error code returned by mma9553_read_activity_stepcnt and return the appropriate error in gpio config function. Signed-off-by:
-
Irina Tirdea authored
Fix typo in Reset/Suspend/Clear Application ID definition. Signed-off-by:
-
Irina Tirdea authored
Fix docummentation for mma9553_read_* functions. Signed-off-by:
-
- Apr 26, 2015
-
-
Daniel Baluta authored
Added support for Liteon 301 Ambient light sensor. Since LTR-301 and LTR-501 are register compatible(and even have same part id), LTR-501 driver has been extended to support both devices. LTR-501 is similar to LTR-301 in ALS sensing, But the only difference is, LTR-501 also supports proximity sensing. LTR-501 - ALS + Proximity combo LTR-301 - ALS sensor. Signed-off-by:
-
Daniel Baluta authored
This device is register compatible with LTR501, with a minor difference for ALS control register as showed below: ALS Control register for LTR501: 7 6 5 4 3 2 1 0 +------+------+------+------+------+------+------+------+ | | | | | | Reserved | Gain | SW | ALS Mode | | | | Reset| | +------+------+------+------+------+------+------+------+ ALS Control register for LTR559: 7 6 5 4 3 2 1 0 +------+------+------+------+------+------+------+------+ | | | | | | Reserved | Gain | SW | ALS | | | | Reset| Mode | +------+------+------+------+------+------+------+------+ We handle this difference by introducing ltr501_chip_info. Datasheet for LTR559 is at: http://optoelectronics.liteon.com/upload/download/DS86-2013-0003/S_110_LTR-559ALS-01_DS_V1.pdf Signed-off-by:
-
- Apr 19, 2015
-
-
Kuppuswamy Sathyanarayanan authored
Added ACPI enumeration support for LTR501 chip. Signed-off-by:
-
Kuppuswamy Sathyanarayanan authored
Added rate control support for ALS and proximity threshold interrupts.Also, Added support to modify and read ALS & proximity sensor sampling frequency. LTR-501 supports interrupt rate control using persistence register settings. Writing <n> to persistence register would generate interrupt only if there are <n> consecutive data values outside the threshold range. Since we don't have any existing ABI's to directly control the persistence register count, we have implemented the rate control using IIO_EV_INFO_PERIOD. _period event attribute represents the amount of time in seconds an event should be true for the device to generate the interrupt. So using _period value and device frequency, persistence count is calculated in driver using following logic. count = period / measurement_rate If the given period is not a multiple of measurement rate then we round up the value to next multiple. This patch also handles change to persistence count whenever there is change in frequency. Signed-off-by:
-
Kuppuswamy Sathyanarayanan authored
This patch adds interrupt support for Liteon 501 chip. Interrupt will be generated whenever ALS or proximity data exceeds values given in upper and lower threshold register settings. Signed-off-by:
-
Kuppuswamy Sathyanarayanan authored
Added support to modify and read ALS integration time. Signed-off-by:
-
Peter Meerwald authored
just cleanup, no functional change Signed-off-by:
Peter Meerwald <pmeerw@pmeerw.net> Signed-off-by:
-
Peter Meerwald authored
just cleanup, no functional change Signed-off-by:
-
Peter Meerwald authored
just cleanup, no functional change Signed-off-by:
-
Vlad Dogaru authored
If a GPIO reset pin is listed in ACPI or Device Tree, use it to reset the device on initialization. Signed-off-by:
Vlad Dogaru <vlad.dogaru@intel.com> Signed-off-by:
-
Vlad Dogaru authored
Signed-off-by:
-
Vlad Dogaru authored
In the interest of lowering power usage, we only activate the proximity channels and interrupts that we are currently using. For raw reads, we activate the corresponding channel and the data ready interrupt and wait for the interrupt to trigger. If no interrupt is available, we wait for the documented scan period, as specified in the datasheet. The following types of usage patterns may overlap: * raw proximity reads (need a single data ready interrupt) * trigger usage (needs data ready interrupts as long as active) * proximity events (need near/far interrupts) * triggered buffer reads (don't need any interrupts, but are usually coupled with our own trigger. To mitigate all possible patterns, we implement usage counting for all the resources used: data ready interrupts, near/far interrupts and individual channels. The device enters sleep mode as documented in the data sheet when its buffer, trigger and events are disabled, and no raw reads are currently running. Because of this new usage pattern, it is important that we give the device a chance to perform an initial compensation for all its channels at probe time. Signed-off-by:
-
Vianney le Clément de Saint-Marcq authored
Fix a typo triggering a duplicate const warning on some compilers. Signed-off-by:
Vianney le Clément de Saint-Marcq <vianney.leclement@essensium.com> Cc: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Signed-off-by:
-
Kuppuswamy Sathyanarayanan authored
Added regmap support. It will be useful to handle bitwise updates to als & ps control registers. Signed-off-by:
-
Vlad Dogaru authored
Signed-off-by:
-
Vlad Dogaru authored
Signed-off-by:
-
- Apr 10, 2015
-
-
Vlad Dogaru authored
Signed-off-by:
-
Daniel Baluta authored
This makes ltr501 code consistent with the coding style adopted for the new drivers added to IIO. We prepare the path for adding support for LTR559 chip. Reported by checkpatch.pl Signed-off-by:
-
- Apr 09, 2015
-
-
Vignesh R authored
Refactor DT parsing into a separate function from probe() to help addition of more DT parameters later. No functional changes. Signed-off-by:
Vignesh R <vigneshr@ti.com> Signed-off-by:
-
Vianney le Clément de Saint-Marcq authored
The device uses the MSB of the returned temperature value as an error flag. Return a read error when this bit is set. Signed-off-by:
-
