From: Jonathan Cameron <jic23@kernel.org>
To: Lars-Peter Clausen <lars@metafoo.de>,
Hartmut Knaack <knaack.h@gmx.de>,
Peter Meerwald <pmeerw@pmeerw.net>
Cc: linux-iio@vger.kernel.org
Subject: Re: [PATCH 5/8] iio: __iio_update_buffers: Verify configuration before starting to apply it
Date: Sun, 17 May 2015 10:14:09 +0100 [thread overview]
Message-ID: <55585BE1.4060606@kernel.org> (raw)
In-Reply-To: <1431525891-19285-6-git-send-email-lars@metafoo.de>
On 13/05/15 15:04, Lars-Peter Clausen wrote:
> Currently __iio_update_buffers() verifies whether the new configuration
> will work in the middle of the update sequence. This means if the new
> configuration is invalid we need to rollback the changes already made. This
> patch moves the validation of the new configuration at the beginning of
> __iio_update_buffers() and will not start to make any changes if the new
> configuration is invalid.
It's funny how code evolves sometimes. It never occurred to me that
we could do this before actually unwinding the buffers but of course
we can. :)
>
> Signed-off-by: Lars-Peter Clausen <lars@metafoo.de>
This one looks good, will wait on responses to the previous before taking
it however.
> ---
> drivers/iio/industrialio-buffer.c | 164 +++++++++++++++++++++++---------------
> 1 file changed, 100 insertions(+), 64 deletions(-)
>
> diff --git a/drivers/iio/industrialio-buffer.c b/drivers/iio/industrialio-buffer.c
> index 8ecba2f..68e2669 100644
> --- a/drivers/iio/industrialio-buffer.c
> +++ b/drivers/iio/industrialio-buffer.c
> @@ -603,20 +603,104 @@ static void iio_free_scan_mask(struct iio_dev *indio_dev,
> kfree(mask);
> }
>
> +struct iio_device_config {
> + unsigned int mode;
> + const unsigned long *scan_mask;
> + unsigned int scan_bytes;
> + bool scan_timestamp;
> +};
> +
> +static int iio_verify_update(struct iio_dev *indio_dev,
> + struct iio_buffer *insert_buffer, struct iio_buffer *remove_buffer,
> + struct iio_device_config *config)
> +{
> + unsigned long *compound_mask;
> + const unsigned long *scan_mask;
> + struct iio_buffer *buffer;
> + bool scan_timestamp;
> +
> + memset(config, 0, sizeof(*config));
> +
> + /*
> + * If there is just one buffer and we are removing it there is nothing
> + * to verify.
> + */
> + if (remove_buffer && !insert_buffer &&
> + list_is_singular(&indio_dev->buffer_list))
> + return 0;
> +
> + /* Definitely possible for devices to support both of these. */
> + if ((indio_dev->modes & INDIO_BUFFER_TRIGGERED) && indio_dev->trig) {
> + config->mode = INDIO_BUFFER_TRIGGERED;
> + } else if (indio_dev->modes & INDIO_BUFFER_HARDWARE) {
> + config->mode = INDIO_BUFFER_HARDWARE;
> + } else if (indio_dev->modes & INDIO_BUFFER_SOFTWARE) {
> + config->mode = INDIO_BUFFER_SOFTWARE;
> + } else {
> + /* Can only occur on first buffer */
> + if (indio_dev->modes & INDIO_BUFFER_TRIGGERED)
> + dev_dbg(&indio_dev->dev, "Buffer not started: no trigger\n");
> + return -EINVAL;
> + }
> +
> + /* What scan mask do we actually have? */
> + compound_mask = kcalloc(BITS_TO_LONGS(indio_dev->masklength),
> + sizeof(long), GFP_KERNEL);
> + if (compound_mask == NULL)
> + return -ENOMEM;
> +
> + scan_timestamp = false;
> +
> + list_for_each_entry(buffer, &indio_dev->buffer_list, buffer_list) {
> + if (buffer == remove_buffer)
> + continue;
> + bitmap_or(compound_mask, compound_mask, buffer->scan_mask,
> + indio_dev->masklength);
> + scan_timestamp |= buffer->scan_timestamp;
> + }
> +
> + if (insert_buffer) {
> + bitmap_or(compound_mask, compound_mask,
> + insert_buffer->scan_mask, indio_dev->masklength);
> + scan_timestamp |= insert_buffer->scan_timestamp;
> + }
> +
> + if (indio_dev->available_scan_masks) {
> + scan_mask = iio_scan_mask_match(indio_dev->available_scan_masks,
> + indio_dev->masklength,
> + compound_mask);
> + kfree(compound_mask);
> + if (scan_mask == NULL)
> + return -EINVAL;
> + } else {
> + scan_mask = compound_mask;
> + }
> +
> + config->scan_bytes = iio_compute_scan_bytes(indio_dev,
> + scan_mask, scan_timestamp);
> + config->scan_mask = scan_mask;
> + config->scan_timestamp = scan_timestamp;
> +
> + return 0;
> +}
> +
> static int __iio_update_buffers(struct iio_dev *indio_dev,
> struct iio_buffer *insert_buffer,
> struct iio_buffer *remove_buffer)
> {
> int ret;
> - int success = 0;
> - struct iio_buffer *buffer;
> - unsigned long *compound_mask;
> const unsigned long *old_mask;
> + struct iio_device_config new_config;
> +
> + ret = iio_verify_update(indio_dev, insert_buffer, remove_buffer,
> + &new_config);
> + if (ret)
> + return ret;
>
> if (insert_buffer) {
> ret = iio_buffer_request_update(indio_dev, insert_buffer);
> if (ret)
> - return ret;
> + goto err_free_config;
> }
>
> /* Wind down existing buffers - iff there are any */
> @@ -624,13 +708,13 @@ static int __iio_update_buffers(struct iio_dev *indio_dev,
> if (indio_dev->setup_ops->predisable) {
> ret = indio_dev->setup_ops->predisable(indio_dev);
> if (ret)
> - return ret;
> + goto err_free_config;
> }
>
> if (indio_dev->setup_ops->postdisable) {
> ret = indio_dev->setup_ops->postdisable(indio_dev);
> if (ret)
> - return ret;
> + goto err_free_config;
> }
>
> indio_dev->currentmode = INDIO_DIRECT_MODE;
> @@ -652,59 +736,10 @@ static int __iio_update_buffers(struct iio_dev *indio_dev,
> return 0;
> }
>
> - /* What scan mask do we actually have? */
> - compound_mask = kcalloc(BITS_TO_LONGS(indio_dev->masklength),
> - sizeof(long), GFP_KERNEL);
> - if (compound_mask == NULL) {
> - iio_free_scan_mask(indio_dev, old_mask);
> - return -ENOMEM;
> - }
> - indio_dev->scan_timestamp = 0;
> -
> - list_for_each_entry(buffer, &indio_dev->buffer_list, buffer_list) {
> - bitmap_or(compound_mask, compound_mask, buffer->scan_mask,
> - indio_dev->masklength);
> - indio_dev->scan_timestamp |= buffer->scan_timestamp;
> - }
> - if (indio_dev->available_scan_masks) {
> - indio_dev->active_scan_mask =
> - iio_scan_mask_match(indio_dev->available_scan_masks,
> - indio_dev->masklength,
> - compound_mask);
> - kfree(compound_mask);
> - if (indio_dev->active_scan_mask == NULL) {
> - /*
> - * Roll back.
> - * Note can only occur when adding a buffer.
> - */
> - iio_buffer_deactivate(insert_buffer);
> - if (old_mask) {
> - indio_dev->active_scan_mask = old_mask;
> - success = -EINVAL;
> - }
> - else {
> - ret = -EINVAL;
> - return ret;
> - }
> - }
> - } else {
> - indio_dev->active_scan_mask = compound_mask;
> - }
> -
> - /* Definitely possible for devices to support both of these. */
> - if ((indio_dev->modes & INDIO_BUFFER_TRIGGERED) && indio_dev->trig) {
> - indio_dev->currentmode = INDIO_BUFFER_TRIGGERED;
> - } else if (indio_dev->modes & INDIO_BUFFER_HARDWARE) {
> - indio_dev->currentmode = INDIO_BUFFER_HARDWARE;
> - } else if (indio_dev->modes & INDIO_BUFFER_SOFTWARE) {
> - indio_dev->currentmode = INDIO_BUFFER_SOFTWARE;
> - } else { /* Should never be reached */
> - /* Can only occur on first buffer */
> - if (indio_dev->modes & INDIO_BUFFER_TRIGGERED)
> - dev_dbg(&indio_dev->dev, "Buffer not started: no trigger\n");
> - ret = -EINVAL;
> - goto error_remove_inserted;
> - }
> + indio_dev->currentmode = new_config.mode;
> + indio_dev->active_scan_mask = new_config.scan_mask;
> + indio_dev->scan_timestamp = new_config.scan_timestamp;
> + indio_dev->scan_bytes = new_config.scan_bytes;
>
> iio_update_demux(indio_dev);
>
> @@ -717,10 +752,7 @@ static int __iio_update_buffers(struct iio_dev *indio_dev,
> goto error_remove_inserted;
> }
> }
> - indio_dev->scan_bytes =
> - iio_compute_scan_bytes(indio_dev,
> - indio_dev->active_scan_mask,
> - indio_dev->scan_timestamp);
> +
> if (indio_dev->info->update_scan_mode) {
> ret = indio_dev->info
> ->update_scan_mode(indio_dev,
> @@ -744,7 +776,7 @@ static int __iio_update_buffers(struct iio_dev *indio_dev,
>
> iio_free_scan_mask(indio_dev, old_mask);
>
> - return success;
> + return 0;
>
> error_run_postdisable:
> if (indio_dev->setup_ops->postdisable)
> @@ -756,6 +788,10 @@ error_remove_inserted:
> iio_free_scan_mask(indio_dev, indio_dev->active_scan_mask);
> indio_dev->active_scan_mask = old_mask;
> return ret;
> +
> +err_free_config:
> + iio_free_scan_mask(indio_dev, new_config.scan_mask);
> + return ret;
> }
>
> int iio_update_buffers(struct iio_dev *indio_dev,
>
next prev parent reply other threads:[~2015-05-17 9:14 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-13 14:04 [PATCH 0/8] iio: Refactor __iio_update_buffers() Lars-Peter Clausen
2015-05-13 14:04 ` [PATCH 1/8] iio: Replace printk in __iio_update_buffers with dev_dbg Lars-Peter Clausen
2015-05-17 8:42 ` Jonathan Cameron
2015-05-13 14:04 ` [PATCH 2/8] iio: __iio_update_buffers: Slightly refactor scan mask memory management Lars-Peter Clausen
2015-05-17 8:48 ` Jonathan Cameron
2015-05-13 14:04 ` [PATCH 3/8] iio: __iio_update_buffers: Perform request_update() only for new buffers Lars-Peter Clausen
2015-05-17 9:01 ` Jonathan Cameron
2015-05-13 14:04 ` [PATCH 4/8] iio: __iio_update_buffers: Update mode before preenable/after postdisable Lars-Peter Clausen
2015-05-17 9:10 ` Jonathan Cameron
2015-05-17 11:38 ` Lars-Peter Clausen
2015-05-17 11:44 ` Jonathan Cameron
2015-05-13 14:04 ` [PATCH 5/8] iio: __iio_update_buffers: Verify configuration before starting to apply it Lars-Peter Clausen
2015-05-17 9:14 ` Jonathan Cameron [this message]
2015-05-13 14:04 ` [PATCH 6/8] iio: __iio_update_buffers: Split enable and disable path into helper functions Lars-Peter Clausen
2015-05-17 9:17 ` Jonathan Cameron
2015-05-13 14:04 ` [PATCH 7/8] iio: __iio_update_buffers: Leave device in sane state on error Lars-Peter Clausen
2015-05-17 9:22 ` Jonathan Cameron
2015-05-13 14:04 ` [PATCH 8/8] DO NOT APPLY! __iio_update_buffers error path testing Lars-Peter Clausen
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=55585BE1.4060606@kernel.org \
--to=jic23@kernel.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).