All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alison Schofield <amsfield22@gmail.com>
To: jic23@kernel.org
Cc: lars@metafoo.de, Michael.Hennerich@analog.com, knaack.h@gmx.de,
	pmeerw@pmeerw.net, linux-iio@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: [PATCH 0/7] iio: adc: clean up claims on direct mode in ad7* drivers
Date: Tue, 24 May 2016 12:15:25 -0700	[thread overview]
Message-ID: <cover.1464115008.git.amsfield22@gmail.com> (raw)

This set looks at the ad7* drivers and migrates them to use the 
iio helper functions iio_device_claim|release_direct_mode(). 

The first three (7266,7791,7793) were not already holding a lock on
direct mode, so this will be a change in behavior for those drivers.

The last four (7476,7887,7923,799x) were already locking so these
are migrations to the claim/release helper functions.

Worth noting: This does not clean up all mlock (ab-)uses in ad799x. 
This driver is still using mlock in a few other places not associated
with locking down direct mode. 

Alison Schofield (7):
  iio: adc: ad7266: claim direct mode during sensor read
  iio: adc: ad7791: claim direct mode when writing frequency
  iio: adc: ad7793: claim direct mode when writing frequency
  iio: adc: ad7476: use iio helper function to guarantee direct mode
  iio: adc: ad7887: use iio helper function to guarantee direct mode
  iio: adc: ad7923: use iio helper function to guarantee direct mode
  iio: adc: ad799x: use iio helper function to guarantee direct mode

 drivers/iio/adc/ad7266.c |  7 +++----
 drivers/iio/adc/ad7476.c | 11 +++++------
 drivers/iio/adc/ad7791.c | 15 ++++-----------
 drivers/iio/adc/ad7793.c | 13 ++++---------
 drivers/iio/adc/ad7887.c | 11 +++++------
 drivers/iio/adc/ad7923.c | 11 +++++------
 drivers/iio/adc/ad799x.c | 24 +++++++++---------------
 7 files changed, 35 insertions(+), 57 deletions(-)

-- 
2.1.4

             reply	other threads:[~2016-05-24 19:15 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-24 19:15 Alison Schofield [this message]
2016-05-24 19:16 ` [PATCH 1/7] iio: adc: ad7266: claim direct mode during sensor read Alison Schofield
2016-05-25 10:33   ` Daniel Baluta
2016-05-29 17:02     ` Jonathan Cameron
2016-05-24 19:16 ` [PATCH 2/7] iio: adc: ad7791: claim direct mode when writing frequency Alison Schofield
2016-05-25 10:34   ` Daniel Baluta
2016-05-29 17:06     ` Jonathan Cameron
2016-05-29 17:07       ` Jonathan Cameron
2016-05-31 13:20       ` Lars-Peter Clausen
2016-05-24 19:17 ` [PATCH 3/7] iio: adc: ad7793: " Alison Schofield
2016-05-25 10:36   ` Daniel Baluta
2016-05-29 18:33     ` Jonathan Cameron
2016-05-31 13:21       ` Lars-Peter Clausen
2016-05-24 19:18 ` [PATCH 4/7] iio: adc: ad7476: use iio helper function to guarantee direct mode Alison Schofield
2016-05-25 10:37   ` Daniel Baluta
2016-05-29 18:35     ` Jonathan Cameron
2016-05-24 19:18 ` [PATCH 5/7] iio: adc: ad7887: " Alison Schofield
2016-05-25 10:38   ` Daniel Baluta
2016-05-29 18:35     ` Jonathan Cameron
2016-05-24 19:19 ` [PATCH 6/7] iio: adc: ad7923: " Alison Schofield
2016-05-25 10:41   ` Daniel Baluta
2016-05-29 18:36     ` Jonathan Cameron
2016-05-24 19:20 ` [PATCH 7/7] iio: adc: ad799x: " Alison Schofield
2016-05-25 10:42   ` Daniel Baluta
2016-05-29 18:39     ` Jonathan Cameron

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=cover.1464115008.git.amsfield22@gmail.com \
    --to=amsfield22@gmail.com \
    --cc=Michael.Hennerich@analog.com \
    --cc=jic23@kernel.org \
    --cc=knaack.h@gmx.de \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pmeerw@pmeerw.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.