Re: [PATCH] staging: iio: ad7606: use iio_device_{claim|release}_direct_mode()

2016-04-10 Thread Jonathan Cameron
On 06/04/16 19:06, Lars-Peter Clausen wrote: > On 04/03/2016 11:09 AM, Jonathan Cameron wrote: >> On 01/04/16 17:53, Alison Schofield wrote: >>> Two instances are moved to the new claim/release API: >>> >>> In the first instance, the driver was using mlock followed by >>> iio_buffer_enabled().

Re: [PATCH] staging: iio: ad7606: use iio_device_{claim|release}_direct_mode()

2016-04-06 Thread Lars-Peter Clausen
On 04/03/2016 11:09 AM, Jonathan Cameron wrote: > On 01/04/16 17:53, Alison Schofield wrote: >> Two instances are moved to the new claim/release API: >> >> In the first instance, the driver was using mlock followed by >> iio_buffer_enabled(). Replace that code with the new API to guarantee >> the

Re: [PATCH] staging: iio: ad7606: use iio_device_{claim|release}_direct_mode()

2016-04-05 Thread Alison Schofield
On Sun, Apr 03, 2016 at 10:09:13AM +0100, Jonathan Cameron wrote: > On 01/04/16 17:53, Alison Schofield wrote: > > Two instances are moved to the new claim/release API: > > > > In the first instance, the driver was using mlock followed by > > iio_buffer_enabled(). Replace that code with the new

[PATCH] staging: iio: ad7606: use iio_device_{claim|release}_direct_mode()

2016-04-01 Thread Alison Schofield
Two instances are moved to the new claim/release API: In the first instance, the driver was using mlock followed by iio_buffer_enabled(). Replace that code with the new API to guarantee the device stays in direct mode. There is no change in driver behavior. In the second instance, the driver was