Allow the current for both RED and IR LEDs to be set via an device tree
property setting.
This is an optional setting that is useful for applications that have a
known glass attenuation factor.
Signed-off-by: Matt Ranostay
---
Changes from v2:
* change to use microamp property name from LED
On Tue, Dec 29, 2015 at 10:34 AM, Rob Herring wrote:
> On Sat, Dec 26, 2015 at 08:38:24PM -0800, Matt Ranostay wrote:
>> Allow the current for both RED and IR LEDs to be set via an device tree
>> property setting.
>>
>> This is an optional setting that is useful f
Allow the current for both RED and IR LEDs to be set via an device tree
property setting.
This is an optional setting that is useful for applications that have a
known glass attenuation factor.
Signed-off-by: Matt Ranostay
---
.../devicetree/bindings/iio/health/max30100.txt | 7
use case.
Modifiers for IIO_MOD_CO2 and IIO_MOD_VOC gas types are defined.
Signed-off-by: Matt Ranostay
---
Documentation/ABI/testing/sysfs-bus-iio | 11 +++
drivers/iio/industrialio-core.c | 3 +++
include/uapi/linux/iio/types.h | 3 +++
3 files changed, 17 insertions
Signed-off-by: Matt Ranostay
---
Documentation/ABI/testing/sysfs-bus-iio | 8
drivers/iio/industrialio-core.c | 1 +
include/uapi/linux/iio/types.h | 1 +
3 files changed, 10 insertions(+)
diff --git a/Documentation/ABI/testing/sysfs-bus-iio
b/Documentation/ABI
Changes from v4:
* Add IIO_MOD_CO2 and IIO_MOD_VOC modifiers
* Updated IIO_RESISTANCE and IIO_CONCENTRATION documentation
* Moved the decimal point shifting to the scale value versus the reading
Matt Ranostay (4):
iio: chemical: Add IIO_CONCENTRATION channel type
iio: resistance: add
Add support for VZ89X sensors VOC and CO2 reporting channels in
percentage which can be converted to part per million.
Signed-off-by: Matt Ranostay
---
.../ABI/testing/sysfs-bus-iio-chemical-vz89x | 7 +
.../devicetree/bindings/i2c/trivial-devices.txt| 1 +
drivers/iio/Kconfig
Signed-off-by: Matt Ranostay
---
Documentation/devicetree/bindings/vendor-prefixes.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/vendor-prefixes.txt
b/Documentation/devicetree/bindings/vendor-prefixes.txt
index ac5f0c3..281e8f0 100644
--- a
Add support for VZ89X sensors VOC and CO2 reporting channels in
percentage which can be converted to part per million.
Signed-off-by: Matt Ranostay
---
.../ABI/testing/sysfs-bus-iio-chemical-vz89x | 30 +++
.../devicetree/bindings/i2c/trivial-devices.txt| 1 +
drivers/iio/Kconfig
Signed-off-by: Matt Ranostay
---
Documentation/devicetree/bindings/vendor-prefixes.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/vendor-prefixes.txt
b/Documentation/devicetree/bindings/vendor-prefixes.txt
index ac5f0c3..281e8f0 100644
--- a
Changes from RFC v2:
* Proper usage of IIO_CHAN_INFO_OFFSET values for VOC and CO2 channels
* Return CO2 offset that combines the 400 ppm offset and -13 value correction
Matt Ranostay (4):
iio: chemical: Add IIO_CONCENTRATION channel type
iio: resistance: add IIO_RESISTANCE channel type
Signed-off-by: Matt Ranostay
---
Documentation/ABI/testing/sysfs-bus-iio | 7 +++
drivers/iio/industrialio-core.c | 1 +
include/uapi/linux/iio/types.h | 1 +
3 files changed, 9 insertions(+)
diff --git a/Documentation/ABI/testing/sysfs-bus-iio
b/Documentation/ABI/testing
use case.
Signed-off-by: Matt Ranostay
---
Documentation/ABI/testing/sysfs-bus-iio | 7 +++
drivers/iio/industrialio-core.c | 1 +
include/uapi/linux/iio/types.h | 1 +
3 files changed, 9 insertions(+)
diff --git a/Documentation/ABI/testing/sysfs-bus-iio
b/Documentation
Thinking this over do we needed a IIO_CHAN_INFO_PROCESSED_OFFSET to
signal that it needs to be after the (value - offset) * scale
calculation?
Thanks,
Matt
On Sun, Sep 6, 2015 at 9:20 PM, Matt Ranostay wrote:
> Also one thing to note here is calculation is ((value - 13) * scale))
> +
PM, Matt Ranostay wrote:
>>
>> Add support for VZ89X sensors VOC and CO2 reporting channels in
>> percentage which can be converted to part per million.
>>
>> Signed-off-by: Matt Ranostay
>> ---
>> .../ABI/testing/sysfs-bus-iio-chemical-vz89x
Signed-off-by: Matt Ranostay
---
Documentation/ABI/testing/sysfs-bus-iio | 7 +++
drivers/iio/industrialio-core.c | 1 +
include/uapi/linux/iio/types.h | 1 +
3 files changed, 9 insertions(+)
diff --git a/Documentation/ABI/testing/sysfs-bus-iio
b/Documentation/ABI/testing
use case.
Signed-off-by: Matt Ranostay
---
Documentation/ABI/testing/sysfs-bus-iio | 7 +++
drivers/iio/industrialio-core.c | 1 +
include/uapi/linux/iio/types.h | 1 +
3 files changed, 9 insertions(+)
diff --git a/Documentation/ABI/testing/sysfs-bus-iio
b/Documentation
Add support for VZ89X sensors VOC and CO2 reporting channels in
percentage which can be converted to part per million.
Signed-off-by: Matt Ranostay
---
.../ABI/testing/sysfs-bus-iio-chemical-vz89x | 30 +++
.../devicetree/bindings/i2c/trivial-devices.txt| 1 +
drivers/iio/Kconfig
Signed-off-by: Matt Ranostay
---
Documentation/devicetree/bindings/vendor-prefixes.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/vendor-prefixes.txt
b/Documentation/devicetree/bindings/vendor-prefixes.txt
index ac5f0c3..281e8f0 100644
--- a
-vz89x documentation
Matt Ranostay (4):
iio: chemical: Add IIO_CONCENTRATION channel type
iio: resistance: add IIO_RESISTANCE channel type
devicetree: add SGX Sensortech vendor id
iio: chemical: add SGX VZ89x VOC sensor support
Documentation/ABI/testing/sysfs-bus-iio| 14
On Sun, Aug 16, 2015 at 1:24 AM, Jonathan Cameron wrote:
> On 12/08/15 07:01, Matt Ranostay wrote:
>> Add support for the PulsedLight LIDAR rangefinder sensor which allows
>> high speed (over 300Hz) distance measurements using Barker Coding within
>> 40 meter range.
>>
pulsedlight-lidar-lite-v2 to resolve
confusion that v1 will likely not work with this driver
Matt Ranostay (2):
devicetree: add PulsedLight vendor + device docs
iio: proximity: add support for PulsedLight LIDAR
.../devicetree/bindings/i2c/trivial-devices.txt| 1 +
.../devicetree
lidar-lite-v2.c
b/drivers/iio/proximity/pulsedlight-lidar-lite-v2.c
new file mode 100644
index 000..ff0681b
--- /dev/null
+++ b/drivers/iio/proximity/pulsedlight-lidar-lite-v2.c
@@ -0,0 +1,292 @@
+/*
+ * pulsedlight-lidar-lite-v2.c - Support for PulsedLight LIDAR sensor
+ *
+ * Copyright (C) 2015 Mat
Add pulsedlight vendor to vendor-prefixes.txt, and LIDAR device
documentation to trivial-devices.txt
Signed-off-by: Matt Ranostay
---
Documentation/devicetree/bindings/i2c/trivial-devices.txt | 1 +
Documentation/devicetree/bindings/vendor-prefixes.txt | 1 +
2 files changed, 2 insertions
On Sat, Aug 8, 2015 at 8:05 AM, Jonathan Cameron wrote:
> On 05/08/15 05:41, Matt Ranostay wrote:
>> Add support for the PulsedLight LIDAR rangefinder sensor which allows
>> high speed (over 300Hz) distance measurements using Barker Coding within
>> 40 meter range.
>>
Document compatible string, and required DT properties for APDS9960
chipset driver.
Reviewed-by: Marek Vasut
Signed-off-by: Matt Ranostay
---
.../devicetree/bindings/iio/light/apds9960.txt | 22 ++
1 file changed, 22 insertions(+)
create mode 100644 Documentation
APDS9960 is a combination of ALS, proximity, and gesture sensors.
This patch adds support for these functions along with gain control,
integration time, and event thresholds.
Signed-off-by: Matt Ranostay
---
.../ABI/testing/sysfs-bus-iio-light-apds9960 |7 +
drivers/iio/light/Kconfig
is un-needed
* Using KFIFO buffers to send gesture data
Matt Ranostay (2):
iio: light: DT binding docs for APDS9960 driver
iio: light: add APDS9960 ALS + promixity driver
.../ABI/testing/sysfs-bus-iio-light-apds9960 |7 +
.../devicetree/bindings/iio/light/apds9960.txt | 22
Document compatible string, and required DT properties for APDS9960
chipset driver.
Reviewed-by: Marek Vasut
Signed-off-by: Matt Ranostay
---
.../devicetree/bindings/iio/light/apds9960.txt | 22 ++
1 file changed, 22 insertions(+)
create mode 100644 Documentation
APDS9960 is a combination of ALS, proximity, and gesture sensors.
This patch adds support for these functions along with gain control,
integration time, and event thresholds.
Signed-off-by: Matt Ranostay
---
.../ABI/testing/sysfs-bus-iio-light-apds9960 |7 +
drivers/iio/light/Kconfig
interupt handler for the triggered
buffer
* Push data directly to buffers avoiding needing use a irq_work queue
* Switch to apds9960_buffer_*disable in buffer setup ops
* Minor comment changes
Matt Ranostay (2):
iio: light: DT binding docs for APDS9960 driver
iio: light: add APDS9960 ALS
On Sun, Aug 2, 2015 at 9:15 AM, Jonathan Cameron wrote:
> On 20/07/15 05:00, Matt Ranostay wrote:
>> APDS9960 is a combination of ALS, proximity, and gesture sensors.
>>
>> This patch adds support for these functions along with gain control,
>> integration time, and eve
null
+++ b/drivers/iio/proximity/lidar.c
@@ -0,0 +1,294 @@
+/*
+ * lidar.c - Support for PulsedLight LIDAR range finding sensor
+ *
+ * Copyright (C) 2015 Matt Ranostay
+ *
+ * This program is free software; you can redistribute it and/or modify
+ * it under the terms of the GNU General Public Licen
This patchset adds support for this range finding LIDAR module, and reports
distance back in meters to centimeter resolution with +/- 2.5 CM of accuracy
at ~40 meters.
Changes from v3:
* removed rogue stray newline
* made buffer parameter 16 bytes to fit alignment
Matt Ranostay (2):
devicetree
Add pulsedlight vendor to vendor-prefixes.txt, and LIDAR device
documentation to trivial-devices.txt
Signed-off-by: Matt Ranostay
---
Documentation/devicetree/bindings/i2c/trivial-devices.txt | 1 +
Documentation/devicetree/bindings/vendor-prefixes.txt | 1 +
2 files changed, 2 insertions
Signed-off-by: Matt Ranostay
---
Documentation/devicetree/bindings/input/cap11xx.txt | 19 +++
1 file changed, 19 insertions(+)
diff --git a/Documentation/devicetree/bindings/input/cap11xx.txt
b/Documentation/devicetree/bindings/input/cap11xx.txt
index 7d0a300..8c67a0b 100644
Several cap11xx variants have LEDs that be can be controlled, and this
patchset implements this functionality
Matt Ranostay (2):
dt: add cap11xx LED documentation
cap11xx: add LED support
.../devicetree/bindings/input/cap11xx.txt | 19 +++
drivers/input/keyboard/cap11xx.c
Several cap11xx variants have LEDs that be can be controlled, this
patchset implements this functionality.
Signed-off-by: Matt Ranostay
---
drivers/input/keyboard/cap11xx.c | 140 ++-
1 file changed, 137 insertions(+), 3 deletions(-)
diff --git a/drivers
nly tested on the "blue label" rev 2, but may work using low
>> sample frequencies on the original version.
>>
>> Signed-off-by: Matt Ranostay
>> ---
>> drivers/iio/proximity/Kconfig | 12 ++
>> drivers/iio/proximity/Makefile | 1 +
>> driver
Add pulsedlight vendor to vendor-prefixes.txt, and LIDAR device
documentation to trivial-devices.txt
Signed-off-by: Matt Ranostay
---
Documentation/devicetree/bindings/i2c/trivial-devices.txt | 1 +
Documentation/devicetree/bindings/vendor-prefixes.txt | 1 +
2 files changed, 2 insertions
acy
at ~40 meters.
Changes from v2:
* Add of_match_table for dt lookup
* Return error if timeout happens in reading measurement
* Document why i2c_smbus_read_byte_data can't be used
* Add pulsedlight,lidar to trivial-devices.txt
Matt Ranostay (2):
devicetree: add PulsedLight vendor + de
null
+++ b/drivers/iio/proximity/lidar.c
@@ -0,0 +1,295 @@
+/*
+ * lidar.c - Support for PulsedLight LIDAR range finding sensor
+ *
+ * Copyright (C) 2015 Matt Ranostay
+ *
+ * This program is free software; you can redistribute it and/or modify
+ * it under the terms of the GNU General Public Licen
On Mon, Aug 3, 2015 at 1:56 PM, Matt Porter wrote:
> Add a driver for the MAX6675 thermocouple converter. This
> device interfaces with K-type thermocouples and provides
> cold-junction compensated temperature readings via a
> SPI interface.
>
> Signed-off-by: Matt Porter
> ---
> drivers/iio/tem
On Mon, Aug 3, 2015 at 1:00 AM, Lars-Peter Clausen wrote:
> On 08/02/2015 11:28 PM, Matt Ranostay wrote:
>> On Sun, Aug 2, 2015 at 2:42 AM, Lars-Peter Clausen wrote:
>>> On 08/01/2015 05:58 AM, Matt Ranostay wrote:
>>> [...]
>>>> +
>>>>
null
+++ b/drivers/iio/proximity/lidar.c
@@ -0,0 +1,284 @@
+/*
+ * lidar.c - Support for PulsedLight LIDAR range finding sensor
+ *
+ * Copyright (C) 2015 Matt Ranostay
+ *
+ * This program is free software; you can redistribute it and/or modify
+ * it under the terms of the GNU General Public Licen
acy
at ~40 meters.
Changesfrom v1:
* Add check for invalid signal return
* Removed un-nedded IIO_CHAN_INFO_CALIBBIAS software biasing
* Mark i2c buffer cacheline aligned
* Added IIO_CHAN_INFO_SCALE for centimeter scale
* Minor tab alignment changes
Matt Ranostay (2):
devicetree: add PulsedLi
Signed-off-by: Matt Ranostay
---
Documentation/devicetree/bindings/vendor-prefixes.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/vendor-prefixes.txt
b/Documentation/devicetree/bindings/vendor-prefixes.txt
index 6284568..0f318c3 100644
--- a
On Sun, Aug 2, 2015 at 2:42 AM, Lars-Peter Clausen wrote:
> On 08/01/2015 05:58 AM, Matt Ranostay wrote:
> [...]
>> +
>> +struct lidar_data {
>> + struct mutex lock;
>> + struct iio_dev *indio_dev;
>> + struct i2c_client *client;
>> +
>
On Sat, Aug 1, 2015 at 2:17 PM, Jonathan Cameron
wrote:
>
>
>
> On 1 August 2015 09:39:11 BST, Vladimir Barinov
> wrote:
>>Hi Matt,
>>
>>Find minor comments.
>>
>>On 01.08.2015 06:58, Matt Ranostay wrote:
>>> Add support for the PulsedLigh
2.5 CM of accuracy
at ~40 meters.
Matt Ranostay (2):
devicetree: add PulsedLight vendor prefix
iio: proximity: add support for PulsedLight LIDAR
.../devicetree/bindings/vendor-prefixes.txt| 1 +
drivers/iio/proximity/Kconfig | 13 +
drivers/iio/proximit
Signed-off-by: Matt Ranostay
---
drivers/iio/proximity/Kconfig | 13 ++
drivers/iio/proximity/Makefile | 1 +
drivers/iio/proximity/lidar.c | 309 +
3 files changed, 323 insertions(+)
create mode 100644 drivers/iio/proximity/lidar.c
diff --git a/d
Signed-off-by: Matt Ranostay
---
Documentation/devicetree/bindings/vendor-prefixes.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/vendor-prefixes.txt
b/Documentation/devicetree/bindings/vendor-prefixes.txt
index 181b53e..e466902 100644
--- a
Jonathan,
Does this solve the issues in v3 minus the apds9960_regfield_init() cleanup?
Thanks,
Matt
On Sun, Jul 19, 2015 at 8:57 PM, Matt Ranostay wrote:
> This patchset adds support for the APDS9960 ALS + proximity + gesture
> sensor.
>
> Included support for the various adjusta
APDS9960 is a combination of ALS, proximity, and gesture sensors.
This patch adds support for these functions along with gain control,
integration time, and event thresholds.
Signed-off-by: Matt Ranostay
---
.../ABI/testing/sysfs-bus-iio-light-apds9960 |7 +
drivers/iio/light/Kconfig
APDS9960 is a combination of ALS, proximity, and gesture sensors.
This patch adds support for these functions along with gain control,
integration time, and event thresholds.
Signed-off-by: Matt Ranostay
---
.../ABI/testing/sysfs-bus-iio-light-apds9960 |7 +
drivers/iio/light/Kconfig
Document compatible string, and required DT properties for APDS9960
chipset driver.
Signed-off-by: Matt Ranostay
---
.../devicetree/bindings/iio/light/apds9960.txt | 22 ++
1 file changed, 22 insertions(+)
create mode 100644 Documentation/devicetree/bindings/iio/light
efine, and prevent values
less than 0
* Avoid needlessly checking the APDS9960_REG_GFLVL value until we read
all the FIFO from the count value. Note this can save up to 32
superfluous i2c reads per gesture engine entry
Matt Ranostay (2):
iio: light: DT binding docs for APDS9960 driver
On Sun, Jul 19, 2015 at 3:45 AM, Jonathan Cameron wrote:
> On 13/07/15 03:20, Matt Ranostay wrote:
>> APDS9960 is a combination of ALS, proximity, and gesture sensors.
>>
>> This patch adds support for these functions along with gain control,
>> integration
On Sun, Jul 19, 2015 at 3:45 AM, Jonathan Cameron wrote:
> On 13/07/15 03:20, Matt Ranostay wrote:
>> APDS9960 is a combination of ALS, proximity, and gesture sensors.
>>
>> This patch adds support for these functions along with gain control,
>> integration
This changeset adds driver support for the Microchip mcp98xx series of
temperature sensors.
This includes temperature reading, and rising/falling threshold events.
Matt Ranostay (2):
iio: temperature: DT binding doc for mcp98xx
iio: temperature: add support for mcp98xx sensors
.../bindings
Document compatible string, and required DT properties for mcp98xx
chipset driver
Signed-off-by: Matt Ranostay
---
.../bindings/iio/temperature/mcp98xx.txt | 22 ++
1 file changed, 22 insertions(+)
create mode 100644
Documentation/devicetree/bindings/iio
Add mcp98xx driver to allow temperature reading, and setting of
upper and lower alert thresholds.
Signed-off-by: Matt Ranostay
---
drivers/iio/temperature/Kconfig | 10 +
drivers/iio/temperature/Makefile | 1 +
drivers/iio/temperature/mcp98xx.c | 588
Ok will fix in v4. Please review the 2/2 patch when you get a chance :)
On Mon, Jul 13, 2015 at 2:42 AM, Jonathan Cameron wrote:
>
>
> On 13 July 2015 03:20:42 BST, Matt Ranostay wrote:
>>Document compatible string, and required DT properties for APDS9960
>>chipset dri
APDS9960 is a combination of ALS, proximity, and gesture sensors.
This patch adds support for these functions along with gain control,
integration time, and event thresholds.
Signed-off-by: Matt Ranostay
---
.../ABI/testing/sysfs-bus-iio-light-apds9960 | 128 +++
drivers/iio/light
* Typo correction in pm_runtime* initialization
Matt Ranostay (2):
iio: light: DT binding docs for APDS9960 driver
iio: light: add APDS9960 ALS + promixity driver
.../ABI/testing/sysfs-bus-iio-light-apds9960 | 128 +++
.../devicetree/bindings/iio/light/apds9960.txt | 19
Document compatible string, and required DT properties for APDS9960
chipset driver.
Reviewed-by: Marek Vasut
Signed-off-by: Matt Ranostay
---
.../devicetree/bindings/iio/light/apds9960.txt| 19 +++
1 file changed, 19 insertions(+)
create mode 100644 Documentation
On Tue, Jul 7, 2015 at 10:16 PM, Matt Ranostay wrote:
> APDS9960 is a combination of ALS, proximity, and gesture sensors.
>
> This patch adds support for these functions along with gain control,
> integration time, and event thresholds.
>
> Signed-off-by: Matt Ranostay
> -
be more clear about gesture features
* Changed gain setting from IIO_CHAN_INFO_CALIBSCALE to IIO_CHAN_INFO_SCALE
* Removed superfluous information in iio_chan_spec channels
* Fixed likely buffer overrun issue
* Make mutex and gain + it setting logic more clear
* Fixed typos in comments
Matt
Document compatible string, and required DT properties for APDS9960
chipset driver.
Reviewed-by: Marek Vasut
Signed-off-by: Matt Ranostay
---
.../devicetree/bindings/iio/light/apds9960.txt| 19 +++
1 file changed, 19 insertions(+)
create mode 100644 Documentation
APDS9960 is a combination of ALS, proximity, and gesture sensors.
This patch adds support for these functions along with gain control,
integration time, and event thresholds.
Signed-off-by: Matt Ranostay
---
.../ABI/testing/sysfs-bus-iio-light-apds9960 | 128 +++
drivers/iio/light
This patchset adds support for the APDS9960 ALS + proximity + gesture
sensor.
Included support for the various adjustable settings and controls:
* Falling and rising ALS + proximity thresholds events
* Gain controls
* ALS time integration
Matt Ranostay (2):
iio: light: DT binding docs for
APDS9960 is a combination ALS, proximity, and gesture sensor.
This patch adds support for these functions along with gain control,
integration time, and event thresholds.
Signed-off-by: Matt Ranostay
---
.../ABI/testing/sysfs-bus-iio-light-apds9960 | 125 ++
drivers/iio/light/Kconfig
Document compatible string, and required DT properties for APDS9960
chipset driver.
Reviewed-by: Marek Vasut
Signed-off-by: Matt Ranostay
---
.../devicetree/bindings/iio/light/apds9960.txt| 19 +++
1 file changed, 19 insertions(+)
create mode 100644 Documentation
Was there any more input or changes needed for this patchset?
Thanks,
Matt
On Tue, Jun 23, 2015 at 11:50 PM, Matt Ranostay wrote:
> changes from v5:
> * Dropped linux,led-brightness DT property
> * Removed several ifdefs to LED CLASS
> * Added cap11xx_init_leds stub
>
>
Several cap11xx variants have LEDs that be can be controlled, this
patchset implements this functionality.
Signed-off-by: Matt Ranostay
---
drivers/input/keyboard/cap11xx.c | 140 ++-
1 file changed, 137 insertions(+), 3 deletions(-)
diff --git a/drivers
Signed-off-by: Matt Ranostay
---
Documentation/devicetree/bindings/input/cap11xx.txt | 19 +++
1 file changed, 19 insertions(+)
diff --git a/Documentation/devicetree/bindings/input/cap11xx.txt
b/Documentation/devicetree/bindings/input/cap11xx.txt
index 7d0a300..8c67a0b 100644
changes from v5:
* Dropped linux,led-brightness DT property
* Removed several ifdefs to LED CLASS
* Added cap11xx_init_leds stub
Matt Ranostay (2):
dt: add cap11xx LED documentation
cap11xx: add LED support
.../devicetree/bindings/input/cap11xx.txt | 19 +++
drivers/input/keyboard
On Tue, Jun 23, 2015 at 11:07 AM, Dmitry Torokhov
wrote:
> On Tue, Jun 23, 2015 at 10:23:57AM -0700, Matt Ranostay wrote:
>> On Tue, Jun 23, 2015 at 1:36 AM, Jacek Anaszewski
>> wrote:
>> > On 06/22/2015 07:59 PM, Dmitry Torokhov wrote:
>> >>
>> >>
On Tue, Jun 23, 2015 at 1:36 AM, Jacek Anaszewski
wrote:
> On 06/22/2015 07:59 PM, Dmitry Torokhov wrote:
>>
>> On Wed, Jun 17, 2015 at 08:58:16PM -0700, Matt Ranostay wrote:
>>>
>>> Signed-off-by: Matt Ranostay
>>> ---
>>> .../
On Wed, Jun 17, 2015 at 11:51 PM, Jacek Anaszewski
wrote:
> Hi Matt,
>
>
> On 06/18/2015 05:58 AM, Matt Ranostay wrote:
>>
>> Several cap11xx variants have LEDs that be can be controlled, this
>> patchset implements this functionality.
>>
>> Signed-off-by
Signed-off-by: Matt Ranostay
---
.../devicetree/bindings/input/cap11xx.txt | 25 ++
1 file changed, 25 insertions(+)
diff --git a/Documentation/devicetree/bindings/input/cap11xx.txt
b/Documentation/devicetree/bindings/input/cap11xx.txt
index 7d0a300..09cdc43 100644
detect if LEDs are in use and
calculate which power state it should be in.
Matt Ranostay (2):
dt: add cap11xx LED documentation
cap11xx: add LED support
.../devicetree/bindings/input/cap11xx.txt | 25
drivers/input/keyboard/cap11xx.c | 140
Several cap11xx variants have LEDs that be can be controlled, this
patchset implements this functionality.
Signed-off-by: Matt Ranostay
---
drivers/input/keyboard/cap11xx.c | 141 ++-
1 file changed, 138 insertions(+), 3 deletions(-)
diff --git a/drivers
On Wed, Jun 17, 2015 at 3:38 PM, Dmitry Torokhov
wrote:
> On Wed, Jun 17, 2015 at 02:53:26PM -0700, Matt Ranostay wrote:
>> On Wed, Jun 17, 2015 at 1:59 AM, Daniel Mack wrote:
>> > On 06/17/2015 08:49 AM, Matt Ranostay wrote:
>> >> Actually after further reading of
On Wed, Jun 17, 2015 at 1:59 AM, Daniel Mack wrote:
> On 06/17/2015 08:49 AM, Matt Ranostay wrote:
>> Actually after further reading of the datasheet and testing with
>> i2ctools it seems cap11xx_input_close() isn't putting the device in
>> DEEP SLEEP mode.
>>
&g
Actually after further reading of the datasheet and testing with
i2ctools it seems cap11xx_input_close() isn't putting the device in
DEEP SLEEP mode.
Any thoughts why?
On Tue, Jun 16, 2015 at 11:34 PM, Matt Ranostay wrote:
> On Tue, Jun 16, 2015 at 2:55 PM, Matt Ranostay wrote:
>&g
On Tue, Jun 16, 2015 at 2:55 PM, Matt Ranostay wrote:
> On Tue, Jun 16, 2015 at 2:26 PM, Daniel Mack wrote:
>> On 06/16/2015 04:39 PM, Matt Ranostay wrote:
>>> On Tue, Jun 16, 2015 at 12:54 AM, Jacek Anaszewski
>>> wrote:
>>>> On 0
On Tue, Jun 16, 2015 at 2:26 PM, Daniel Mack wrote:
> On 06/16/2015 04:39 PM, Matt Ranostay wrote:
>> On Tue, Jun 16, 2015 at 12:54 AM, Jacek Anaszewski
>> wrote:
>>> On 06/16/2015 04:46 AM, Matt Ranostay wrote:
>
>>>> + for_each_child_of_node(
On Tue, Jun 16, 2015 at 12:54 AM, Jacek Anaszewski
wrote:
> On 06/16/2015 04:46 AM, Matt Ranostay wrote:
>>
>> Several cap11xx variants have LEDs that be can be controlled, this
>> patchset implements this functionality.
>>
>> Signed-off-by: Matt Ranostay
&
On Tue, Jun 16, 2015 at 12:57 AM, Jacek Anaszewski
wrote:
> On 06/16/2015 04:46 AM, Matt Ranostay wrote:
>>
>> Signed-off-by: Matt Ranostay
>> ---
>> .../devicetree/bindings/input/cap11xx.txt | 23
>> ++
>> 1 file chang
Signed-off-by: Matt Ranostay
---
.../devicetree/bindings/input/cap11xx.txt | 23 ++
1 file changed, 23 insertions(+)
diff --git a/Documentation/devicetree/bindings/input/cap11xx.txt
b/Documentation/devicetree/bindings/input/cap11xx.txt
index 7d0a300..01bb5b8 100644
Several cap11xx variants have LEDs that be can be controlled, this
patchset implements this functionality.
Signed-off-by: Matt Ranostay
---
drivers/input/keyboard/cap11xx.c | 128 ++-
1 file changed, 125 insertions(+), 3 deletions(-)
diff --git a/drivers
Changes from v3:
* Fix race condition in work_queue
* Make 0 value (0% duty cycle) an invalid brightness option
* Document why LED brightness is only set global but ON/OFF state isn't
Matt Ranostay (2):
dt: add cap11xx LED documentation
cap11xx: add LED support
.../devicetree/bin
On Mon, Jun 15, 2015 at 3:11 AM, Jacek Anaszewski
wrote:
> On 06/15/2015 10:56 AM, Matt Ranostay wrote:
>>
>> On Mon, Jun 15, 2015 at 1:15 AM, Jacek Anaszewski
>> wrote:
>>>
>>> Hi Matt,
>>>
>>>
>>> On 06/13/2015 06:17 AM, Matt
On Mon, Jun 15, 2015 at 2:03 AM, Daniel Mack wrote:
> On 06/15/2015 10:56 AM, Matt Ranostay wrote:
>> On Mon, Jun 15, 2015 at 1:15 AM, Jacek Anaszewski
>> wrote:
>
>>>> + error = devm_led_classdev_register(dev, &led->cdev
On Mon, Jun 15, 2015 at 3:10 AM, Jacek Anaszewski
wrote:
> On 06/15/2015 10:48 AM, Matt Ranostay wrote:
>>
>> On Mon, Jun 15, 2015 at 1:15 AM, Jacek Anaszewski
>> wrote:
>>>
>>> Hi Matt,
>>>
>>> On 06/13/2015 06:17 AM, Matt Ranostay wrot
On Mon, Jun 15, 2015 at 1:15 AM, Jacek Anaszewski
wrote:
> Hi Matt,
>
>
> On 06/13/2015 06:17 AM, Matt Ranostay wrote:
>>
>> Several cap11xx variants have LEDs that be can be controlled, this
>> patchset implements this functionality.
>>
>> Signed-off-by
On Mon, Jun 15, 2015 at 1:15 AM, Jacek Anaszewski
wrote:
> Hi Matt,
>
> On 06/13/2015 06:17 AM, Matt Ranostay wrote:
>>
>> Some cap11xx devices have LEDs that can be controlled from userpace
>> and via triggers. Document their use and functionality here.
>>
Some cap11xx devices have LEDs that can be controlled from userpace
and via triggers. Document their use and functionality here.
Signed-off-by: Matt Ranostay
---
.../devicetree/bindings/input/cap11xx.txt | 23 ++
1 file changed, 23 insertions(+)
diff --git a
Changes from v2:
* Use LED subsystem correctly, and dynamically allot used LEDs
* Add LED trigger support (e.g. heartbeat, mmc trigger, etc)
* Add DT properties for configuring LED usage, labels, and brightness
Matt Ranostay (2):
dt: add cap11xx LED documentation
cap11xx: add LED support
1 - 100 of 162 matches
Mail list logo
