linux-kernel - Re: [PATCH v3] iio: Add driver for Silabs si1132, si1141/2/3 and si1145/6/7 ambient light, uv index and proximity sensors

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Sun, 26 Jun 2016 16:18:06 +0100
From:	Jonathan Cameron <jic23@...nel.org>
To:	Crestez Dan Leonard <leonard.crestez@...el.com>,
	linux-iio@...r.kernel.org
Cc:	linux-kernel@...r.kernel.org, Hartmut Knaack <knaack.h@....de>,
	Lars-Peter Clausen <lars@...afoo.de>,
	Peter Meerwald-Stadler <pmeerw@...erw.net>,
	Daniel Baluta <daniel.baluta@...el.com>
Subject: Re: [PATCH v3] iio: Add driver for Silabs si1132, si1141/2/3 and
 si1145/6/7 ambient light, uv index and proximity sensors

On 21/06/16 15:37, Crestez Dan Leonard wrote:
> On 06/19/2016 02:57 PM, Jonathan Cameron wrote:
>> On 17/06/16 12:10, Crestez Dan Leonard wrote:
>>> From: Peter Meerwald <pmeerw@...erw.net>
>>>
>>> The si114x supports x=1,2,3 IR LEDs for proximity sensing together with
>>> visible and IR ambient light sensing (ALS).
>>>
>>> Newer parts (si1132, si1145/6/7) can measure UV light and compute an UV index
>>>
>>> Changes since v2:
>>> * Add myself to copyright
>>> * Remove TODO: power management.
>>> It's fine because by default the device remains sleeping.
>>> * Elaborate comments on si1145_data
>>> * Adjust comment syntax
>>> * Drop special case for reading single words.
>>> * Use manual request_irq to ensure proper init/free ordering
>>>
>>> Changes since Peter's v1:
>>> * Fix set_chlist returning positive value on success
>>> * Do not assume channel addresses are in order of scan index
>>> * Take lock in buffer_preenable
>>> * Print part/rev/seq id at probe time
>>> * Cleanup param query/update
>>> * Poll for response when executing commands
>>> * Allow writes even when buffer enabled
>>> * Add interrupt support
>>> * Rename new to uncompressed_meas_rate for clarity
>>> * Fix handling IIO_CHAN_INFO_SCALE:
>>> Make it so that when changing the scale the processed value remains
>>> identical in identical conditions. The exposed value should be
>>> proportional to 2 ** -ADC_GAIN.
>>> * Initialize UCOEF registers to default values from datasheet
>>> Otherwise by default the coefficients are zero and so are all the
>>> values read back
>>> * Fix reading in_uvindex_raw manually (not in buffer mode)
>>> * Expose in_uvindex_scale=0.01
>>> * Expose ADC offset, making zero values meaningful
>>> This is not very well documented, for example the si1145/6/7 datasheet
>>> lists register 0x1a as 'reserved'. It might make sense to just return a
>>> constant on these models.
>>>
>>> This was tested on si1143 and si1145
>>>
>>> Link to v2: https://www.spinics.net/lists/linux-iio/msg25055.html
>>>
>> Can you explain what the autonomous stuff is about?  Has me confused.
>> Is it an attempt to allow driving the device with a software trigger
>> when no interrupt is provided?  (I think it is but correct me if I'm
>> wrong).  I'm definitely not happy with this approach as a trigger 'in'
>> should always result in data 'out'.  If you are running multiple
>> sensors off one software trigger you'd expect to get the same amount of
>> data from each.
> 
> That "bool autonomous" is true when the device is in "autonomous
> measurement" mode rather than the default "on-demand" mode. I guess it
> might even be possible to replace it with a macro that checks for
> indio_dev flags?
> 
> The driver supports both hardware triggers (from the interrupt) and
> software triggers. With software triggers the device is instructed to
> make measurements automatically and the data is read at the frequency of
> the software trigger.
> 
> I guess this would work a bit strange if the device sampling frequency
> is too different from the software trigger sampling frequency. Since the
> device has no internal fifo to drain at a specific rate it will not
> misbehave. It's just that if the sw freq is higher than the hw freq you
> will see a "square-ish" signal out.
> 
> I also don't think this issue is specific to this driver. It would
> affect most devices with software triggers, right?
yes.  This is fine if ugly should anyone do it.  The values are the
best available, nothing more.

Thanks for the clarification!

Just those other little bits from the review to clean up and this one
should be good to go.

Jonathan
> --
> To unsubscribe from this list: send the line "unsubscribe linux-iio" in
> the body of a message to majordomo@...r.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>