BH1770GLC / SFH7770 combined ambient light / proximity sensor
in [Kernel]
|
Prev: [PATCH 0/1] BH1770GLC / SFH7770 combined ambient light / proximity sensor
Next: Security: fix cap_file_mmap() off-by-one error to avoid kernel null pointer exploit
From: Jonathan Cameron on 15 Apr 2010 07:40 Hi Samu, > This patch introduces driver for Rohm BH1770GLC and Osram SFH7770 > combined ambient light and proximity sensor. > > Driver is divided to 3 parts. Core-part contains common functionality for > both parts of the chips. ALS and PS specific functionalities are > in separate files. > > ALS part is fully based on threshold interrupts. Driver doesn't provide > direct control for threshold levels. Instead, based on sensitivity setting, > threshold levels are updated after every interrupt. This method keeps sensor > to follow changes in the lightning. > > PS part uses interrupt for high threshold events and delayed work to simulate > missing low threshold interrupts. This way driver is able to react proximity > on / off events using only high threshold interrupt. Proximity sensing can > utilize up to 3 IR leds for movement detection. Driver supports 1-3 leds > configurations. > > Platform data is used to provide IR led configuration: number of channels and > absolute maximum operating currents for the leds. > > Chip is kept running only when someone keeps device handles open. > Otherwise chip is powered down and optionally power supplies are turned off. > > Interfaces: > Both parts of the driver provides results via separate misc char device. > > sysfs interface: > als_calib - (RW) calibration coeffient (default is neutral value) > als_mode - (R) returns current chip operational state for ALS > als_rate - (RW) ALS side measurement rate in ms > als_sens - (RW) sensitivity for changes in lightning level This ALS stuff feeds in pretty directly to the discussion just started in response to Alan Cox's post of the isl20920 driver. Basically we need to try and match as much of the sysfs interface across these chips as possible. Obviously this one is different to the ALS sensors already in kernel in that it doesn't allow direct reading of the value. For his driver I suggested illuminance0_input (not matched here) illuminance0_calib (these also happen to match the new IIO spec by amazing coincidence :) I'll put some related comments in a review of the patch. > ps_calib - (RW) calibration coeffient > ps_leds - (RW) IR led currents in mA > ps_mode - (R) returns current chip operational state for PS > ps_rate - (RW) PS side measurement rates (separate rates for below / > above threshold condition) > ps_threshold - (RW) threshold level Likewise with the proximity sensing. If nothing else, please allow for a chip with multiple proximity sensors with separate parameters. > chip_id - (R) chip version and revision information > > Tested in top of 2.6.32 kernel. Applies to 2.6.34-RC3. > > Samu Onkalo (1): > misc: bh1770glc: Driver for bh1770glc combined als and ps sensor > > drivers/misc/Kconfig | 12 + > drivers/misc/Makefile | 3 + > drivers/misc/bh1770glc.h | 169 ++++++++++++ > drivers/misc/bh1770glc_als.c | 424 +++++++++++++++++++++++++++++ > drivers/misc/bh1770glc_core.c | 301 +++++++++++++++++++++ > drivers/misc/bh1770glc_ps.c | 585 +++++++++++++++++++++++++++++++++++++++++ > include/linux/bh1770glc.h | 39 +++ > 7 files changed, 1533 insertions(+), 0 deletions(-) > create mode 100644 drivers/misc/bh1770glc.h > create mode 100644 drivers/misc/bh1770glc_als.c > create mode 100644 drivers/misc/bh1770glc_core.c > create mode 100644 drivers/misc/bh1770glc_ps.c > create mode 100644 include/linux/bh1770glc.h > > -- > To unsubscribe from this list: send the line "unsubscribe linux-i2c" in > the body of a message to majordomo(a)vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ |