Re: [PATCH 5/6] staging: iio: tsl2x7x: refactor {read,write}_event_value to allow handling multiple iio_event_infos

2017-07-01 Thread Jonathan Cameron
On Sat, 1 Jul 2017 06:37:07 -0400 Brian Masney wrote: > On Sat, Jul 01, 2017 at 10:40:20AM +0100, Jonathan Cameron wrote: > > On Thu, 29 Jun 2017 13:03:51 -0400 > > Brian Masney wrote: > > > > > tsl2x7x_read_thresh() and tsl2x7x_write_thresh() currently assumes > > > that IIO_EV_INFO_VALUE is

Re: [PATCH 5/6] staging: iio: tsl2x7x: refactor {read,write}_event_value to allow handling multiple iio_event_infos

2017-07-01 Thread Brian Masney
On Sat, Jul 01, 2017 at 10:40:20AM +0100, Jonathan Cameron wrote: > On Thu, 29 Jun 2017 13:03:51 -0400 > Brian Masney wrote: > > > tsl2x7x_read_thresh() and tsl2x7x_write_thresh() currently assumes > > that IIO_EV_INFO_VALUE is the only iio_event_info that will be > > passed in. This patch refac

Re: [PATCH 5/6] staging: iio: tsl2x7x: refactor {read,write}_event_value to allow handling multiple iio_event_infos

2017-07-01 Thread Jonathan Cameron
On Thu, 29 Jun 2017 13:03:51 -0400 Brian Masney wrote: > tsl2x7x_read_thresh() and tsl2x7x_write_thresh() currently assumes > that IIO_EV_INFO_VALUE is the only iio_event_info that will be > passed in. This patch refactors these two functions so that > additional iio_event_infos can be passed in

[PATCH 5/6] staging: iio: tsl2x7x: refactor {read,write}_event_value to allow handling multiple iio_event_infos

2017-06-29 Thread Brian Masney
tsl2x7x_read_thresh() and tsl2x7x_write_thresh() currently assumes that IIO_EV_INFO_VALUE is the only iio_event_info that will be passed in. This patch refactors these two functions so that additional iio_event_infos can be passed in. The functions are renamed from tsl2x7x_{read,write}_thresh() to