linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Matt Ranostay <mranostay@gmail.com>, linux-iio@vger.kernel.org
Cc: Matt Ranostay <matt@ranostay.consulting>
Subject: Re: [PATCH v3] iio: trigger: allow immutable triggers to be assigned
Date: Sat, 3 Sep 2016 15:32:53 +0100	[thread overview]
Message-ID: <1b63c7d3-dfb8-65de-2bd7-6cd6993b8ff5@kernel.org> (raw)
In-Reply-To: <1472884575-29831-1-git-send-email-matt@ranostay.consulting>

On 03/09/16 07:36, Matt Ranostay wrote:
> From: Matt Ranostay <mranostay@gmail.com>
> 
> There are times when an assigned trigger to a device shouldn't ever
> change after intialization.
> 
> Examples of this being used is when an provider device has a trigger
> that is assigned to an ADC, which uses it populate data into a callback
> buffer.
> 
> Signed-off-by: Matt Ranostay <matt@ranostay.consulting>
Applied to the togreg branch of iio.git.

Initially pushed out as testing for the autobuilders to play
with it.

Peter, if you want to add an Ack / review or other comment
before I push this out as togreg, that would be cool.

Jonathan
> ---
> 
> Changes from v1:
>  * use bool instead of int for trig_readonly property
> 
> Changes from v2:
>  * make commit message more verbose
>  * change dst to indio_dev
> 
>  drivers/iio/industrialio-trigger.c | 20 ++++++++++++++++++++
>  include/linux/iio/iio.h            |  2 ++
>  include/linux/iio/trigger.h        |  9 +++++++++
>  3 files changed, 31 insertions(+)
> 
> diff --git a/drivers/iio/industrialio-trigger.c b/drivers/iio/industrialio-trigger.c
> index 7ad82fdd3e5b..3dde81e57e97 100644
> --- a/drivers/iio/industrialio-trigger.c
> +++ b/drivers/iio/industrialio-trigger.c
> @@ -119,6 +119,22 @@ void iio_trigger_unregister(struct iio_trigger *trig_info)
>  }
>  EXPORT_SYMBOL(iio_trigger_unregister);
>  
> +int iio_trigger_set_immutable(struct iio_dev *indio_dev, struct iio_trigger *trig)
> +{
> +	if (!indio_dev || !trig)
> +		return -EINVAL;
> +
> +	mutex_lock(&indio_dev->mlock);
> +	WARN_ON(indio_dev->trig_readonly);
> +
> +	indio_dev->trig = iio_trigger_get(trig);
> +	indio_dev->trig_readonly = true;
> +	mutex_unlock(&indio_dev->mlock);
> +
> +	return 0;
> +}
> +EXPORT_SYMBOL(iio_trigger_set_immutable);
> +
>  /* Search for trigger by name, assuming iio_trigger_list_lock held */
>  static struct iio_trigger *__iio_trigger_find_by_name(const char *name)
>  {
> @@ -384,6 +400,10 @@ static ssize_t iio_trigger_write_current(struct device *dev,
>  		mutex_unlock(&indio_dev->mlock);
>  		return -EBUSY;
>  	}
> +	if (indio_dev->trig_readonly) {
> +		mutex_unlock(&indio_dev->mlock);
> +		return -EPERM;
> +	}
>  	mutex_unlock(&indio_dev->mlock);
>  
>  	trig = iio_trigger_find_by_name(buf, len);
> diff --git a/include/linux/iio/iio.h b/include/linux/iio/iio.h
> index 854e2dad1e0d..786952cd509f 100644
> --- a/include/linux/iio/iio.h
> +++ b/include/linux/iio/iio.h
> @@ -483,6 +483,7 @@ struct iio_buffer_setup_ops {
>   * @scan_timestamp:	[INTERN] set if any buffers have requested timestamp
>   * @scan_index_timestamp:[INTERN] cache of the index to the timestamp
>   * @trig:		[INTERN] current device trigger (buffer modes)
> + * @trig_readonly	[INTERN] mark the current trigger immutable
>   * @pollfunc:		[DRIVER] function run on trigger being received
>   * @pollfunc_event:	[DRIVER] function run on events trigger being received
>   * @channels:		[DRIVER] channel specification structure table
> @@ -523,6 +524,7 @@ struct iio_dev {
>  	bool				scan_timestamp;
>  	unsigned			scan_index_timestamp;
>  	struct iio_trigger		*trig;
> +	bool				trig_readonly;
>  	struct iio_poll_func		*pollfunc;
>  	struct iio_poll_func		*pollfunc_event;
>  
> diff --git a/include/linux/iio/trigger.h b/include/linux/iio/trigger.h
> index 1c9e028e0d4a..a122bdd4076c 100644
> --- a/include/linux/iio/trigger.h
> +++ b/include/linux/iio/trigger.h
> @@ -132,6 +132,15 @@ int iio_trigger_register(struct iio_trigger *trig_info);
>  void iio_trigger_unregister(struct iio_trigger *trig_info);
>  
>  /**
> + * iio_trigger_set_immutable() - set an immutable trigger on destination
> + *
> + * @indio_dev - IIO device structure containing the device
> + * @trig - trigger to assign to device
> + *
> + **/
> +int iio_trigger_set_immutable(struct iio_dev *indio_dev, struct iio_trigger *trig);
> +
> +/**
>   * iio_trigger_poll() - called on a trigger occurring
>   * @trig:	trigger which occurred
>   *
> 


      reply	other threads:[~2016-09-03 14:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-03  6:36 [PATCH v3] iio: trigger: allow immutable triggers to be assigned Matt Ranostay
2016-09-03 14:32 ` Jonathan Cameron [this message]

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=1b63c7d3-dfb8-65de-2bd7-6cd6993b8ff5@kernel.org \
    --to=jic23@kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=matt@ranostay.consulting \
    --cc=mranostay@gmail.com \
    /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).