All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hartmut Knaack <knaack.h@gmx.de>
To: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>,
	Jonathan Cameron <jic23@kernel.org>,
	Lars-Peter Clausen <lars@metafoo.de>,
	Peter Meerwald <pmeerw@pmeerw.net>
Cc: linux-iio@vger.kernel.org
Subject: Re: [PATCH] iio: inkern: add iio_write_channel_raw
Date: Thu, 11 Dec 2014 00:01:47 +0100	[thread overview]
Message-ID: <5488D0DB.2060400@gmx.de> (raw)
In-Reply-To: <1417041765-12782-1-git-send-email-dbaryshkov@gmail.com>

Dmitry Eremin-Solenikov schrieb am 26.11.2014 um 23:42:
> Introduce API for easy in-kernel setting of DAC values.
> 
Looking good in general, but indentation of parameters could be
improved to align with opening parenthesis. See inline.
> Signed-off-by: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>
> ---
>  drivers/iio/inkern.c         | 29 +++++++++++++++++++++++++++++
>  include/linux/iio/consumer.h | 11 +++++++++++
>  2 files changed, 40 insertions(+)
> 
> diff --git a/drivers/iio/inkern.c b/drivers/iio/inkern.c
> index f084610..5b03e69 100644
> --- a/drivers/iio/inkern.c
> +++ b/drivers/iio/inkern.c
> @@ -608,3 +608,32 @@ err_unlock:
>  	return ret;
>  }
>  EXPORT_SYMBOL_GPL(iio_get_channel_type);
> +
> +static int iio_channel_write(struct iio_channel *chan, int val, int val2,
> +	enum iio_chan_info_enum info)
Here.
> +{
> +	int ret;
> +
> +	ret = chan->indio_dev->info->write_raw(chan->indio_dev,
> +			chan->channel, val, val2, info);
Here.
> +
> +	return ret;
> +}
> +
> +int iio_write_channel_raw(struct iio_channel *chan, int val)
> +{
> +	int ret;
> +
> +	mutex_lock(&chan->indio_dev->info_exist_lock);
> +	if (chan->indio_dev->info == NULL) {
> +		ret = -ENODEV;
> +		goto err_unlock;
> +	}
> +
> +	ret = iio_channel_write(chan, val, 0, IIO_CHAN_INFO_RAW);
> +err_unlock:
> +	mutex_unlock(&chan->indio_dev->info_exist_lock);
> +
> +	return ret;
> +}
> +EXPORT_SYMBOL_GPL(iio_write_channel_raw);
> diff --git a/include/linux/iio/consumer.h b/include/linux/iio/consumer.h
> index 651f9a0..06f4688 100644
> --- a/include/linux/iio/consumer.h
> +++ b/include/linux/iio/consumer.h
> @@ -151,6 +151,17 @@ int iio_read_channel_average_raw(struct iio_channel *chan, int *val);
>  int iio_read_channel_processed(struct iio_channel *chan, int *val);
>  
>  /**
> + * iio_write_channel_raw() - write to a given channel
> + * @chan:		The channel being queried.
> + * @val:		Value being written.
> + *
> + * Note raw writes to iio channels are in dac counts and hence
> + * scale will need to be applied if standard units required.
> + */
> +int iio_write_channel_raw(struct iio_channel *chan,
> +			 int val);
And here, everything would easily fit in just one line.
> +
> +/**
>   * iio_get_channel_type() - get the type of a channel
>   * @channel:		The channel being queried.
>   * @type:		The type of the channel.
> 

  parent reply	other threads:[~2014-12-10 23:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-26 22:42 [PATCH] iio: inkern: add iio_write_channel_raw Dmitry Eremin-Solenikov
2014-11-27  8:07 ` Lars-Peter Clausen
2014-12-10 23:01 ` Hartmut Knaack [this message]
2014-12-12 10:17   ` Jonathan Cameron
2014-12-12 13:33     ` Dmitry Eremin-Solenikov

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=5488D0DB.2060400@gmx.de \
    --to=knaack.h@gmx.de \
    --cc=dbaryshkov@gmail.com \
    --cc=jic23@kernel.org \
    --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 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.