Re: [PATCH 3/7] iio: adc: ad7793: claim direct mode when writing frequency

2016-05-31 Thread Lars-Peter Clausen
On 05/29/2016 08:33 PM, Jonathan Cameron wrote: > On 25/05/16 11:36, Daniel Baluta wrote: >> On Tue, May 24, 2016 at 10:17 PM, Alison Schofield >> wrote: >>> Driver was checking for direct mode and trying to lock it, but >>> left a gap where mode could change before the

Re: [PATCH 3/7] iio: adc: ad7793: claim direct mode when writing frequency

2016-05-31 Thread Lars-Peter Clausen
On 05/29/2016 08:33 PM, Jonathan Cameron wrote: > On 25/05/16 11:36, Daniel Baluta wrote: >> On Tue, May 24, 2016 at 10:17 PM, Alison Schofield >> wrote: >>> Driver was checking for direct mode and trying to lock it, but >>> left a gap where mode could change before the desired operation. >>>

Re: [PATCH 3/7] iio: adc: ad7793: claim direct mode when writing frequency

2016-05-29 Thread Jonathan Cameron
On 25/05/16 11:36, Daniel Baluta wrote: > On Tue, May 24, 2016 at 10:17 PM, Alison Schofield > wrote: >> Driver was checking for direct mode and trying to lock it, but >> left a gap where mode could change before the desired operation. >> Use iio_device_claim_direct_mode()

Re: [PATCH 3/7] iio: adc: ad7793: claim direct mode when writing frequency

2016-05-29 Thread Jonathan Cameron
On 25/05/16 11:36, Daniel Baluta wrote: > On Tue, May 24, 2016 at 10:17 PM, Alison Schofield > wrote: >> Driver was checking for direct mode and trying to lock it, but >> left a gap where mode could change before the desired operation. >> Use iio_device_claim_direct_mode() to guarantee device

Re: [PATCH 3/7] iio: adc: ad7793: claim direct mode when writing frequency

2016-05-25 Thread Daniel Baluta
On Tue, May 24, 2016 at 10:17 PM, Alison Schofield wrote: > Driver was checking for direct mode and trying to lock it, but > left a gap where mode could change before the desired operation. > Use iio_device_claim_direct_mode() to guarantee device stays in > direct mode. > >

Re: [PATCH 3/7] iio: adc: ad7793: claim direct mode when writing frequency

2016-05-25 Thread Daniel Baluta
On Tue, May 24, 2016 at 10:17 PM, Alison Schofield wrote: > Driver was checking for direct mode and trying to lock it, but > left a gap where mode could change before the desired operation. > Use iio_device_claim_direct_mode() to guarantee device stays in > direct mode. > > Signed-off-by: Alison

[PATCH 3/7] iio: adc: ad7793: claim direct mode when writing frequency

2016-05-24 Thread Alison Schofield
Driver was checking for direct mode and trying to lock it, but left a gap where mode could change before the desired operation. Use iio_device_claim_direct_mode() to guarantee device stays in direct mode. Signed-off-by: Alison Schofield Cc: Daniel Baluta

[PATCH 3/7] iio: adc: ad7793: claim direct mode when writing frequency

2016-05-24 Thread Alison Schofield
Driver was checking for direct mode and trying to lock it, but left a gap where mode could change before the desired operation. Use iio_device_claim_direct_mode() to guarantee device stays in direct mode. Signed-off-by: Alison Schofield Cc: Daniel Baluta --- drivers/iio/adc/ad7793.c | 13