linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Beniamin Bia <beniamin.bia@analog.com>
Cc: <lars@metafoo.de>, <Michael.Hennerich@analog.com>,
	<pmeerw@pmeerw.net>, <linux-iio@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>, <biabeniamin@outlook.com>,
	<knaack.h@gmx.de>, <robh+dt@kernel.org>, <mark.rutland@arm.com>,
	<devicetree@vger.kernel.org>
Subject: Re: [PATCH v5 2/5] iio: amplifiers: ad8366: Add write_raw_get_fmt function
Date: Fri, 14 Feb 2020 14:05:55 +0000	[thread overview]
Message-ID: <20200214140555.3b732ad4@archlinux> (raw)
In-Reply-To: <20200206151149.32122-2-beniamin.bia@analog.com>

On Thu, 6 Feb 2020 17:11:46 +0200
Beniamin Bia <beniamin.bia@analog.com> wrote:

> This patch add write_raw_get_fmt function to specify conversion for
> hardware gain.
> 
> Signed-off-by: Beniamin Bia <beniamin.bia@analog.com>
Applied to the togreg branch of iio.git and pushed out as testing for
the autobuilders to play with it.

Thanks,

Jonathan

> ---
> Changes in v5:
> -nothing changed
> 
>  drivers/iio/amplifiers/ad8366.c | 13 +++++++++++++
>  1 file changed, 13 insertions(+)
> 
> diff --git a/drivers/iio/amplifiers/ad8366.c b/drivers/iio/amplifiers/ad8366.c
> index 0176d3d8cc9c..95972ab60f42 100644
> --- a/drivers/iio/amplifiers/ad8366.c
> +++ b/drivers/iio/amplifiers/ad8366.c
> @@ -180,9 +180,22 @@ static int ad8366_write_raw(struct iio_dev *indio_dev,
>  	return ret;
>  }
>  
> +static int ad8366_write_raw_get_fmt(struct iio_dev *indio_dev,
> +				    struct iio_chan_spec const *chan,
> +				    long mask)
> +{
> +	switch (mask) {
> +	case IIO_CHAN_INFO_HARDWAREGAIN:
> +		return IIO_VAL_INT_PLUS_MICRO_DB;
> +	default:
> +		return -EINVAL;
> +	}
> +}
> +
>  static const struct iio_info ad8366_info = {
>  	.read_raw = &ad8366_read_raw,
>  	.write_raw = &ad8366_write_raw,
> +	.write_raw_get_fmt = &ad8366_write_raw_get_fmt,
>  };
>  
>  #define AD8366_CHAN(_channel) {				\


  reply	other threads:[~2020-02-14 14:06 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-06 15:11 [PATCH v5 1/5] iio: core: Handle 'dB' suffix in core Beniamin Bia
2020-02-06 15:11 ` [PATCH v5 2/5] iio: amplifiers: ad8366: Add write_raw_get_fmt function Beniamin Bia
2020-02-14 14:05   ` Jonathan Cameron [this message]
2020-02-06 15:11 ` [PATCH v5 3/5] iio: amplifiers: hmc425a: Add support for HMC425A attenuator Beniamin Bia
2020-02-14 14:09   ` Jonathan Cameron
2020-02-20 12:32     ` Bia, Beniamin
2020-03-08 17:31       ` Jonathan Cameron
2020-02-06 15:11 ` [PATCH v5 4/5] dt-bindings: iio: amplifiers: Add docs for HMC425A Step Attenuator Beniamin Bia
2020-02-06 21:34   ` Rob Herring
2020-02-14 14:14     ` Jonathan Cameron
2020-02-06 15:11 ` [PATCH v5 5/5] MAINTAINERS: add entry for hmc425a driver Beniamin Bia
2020-02-14 14:14   ` Jonathan Cameron
2020-02-14 14:04 ` [PATCH v5 1/5] iio: core: Handle 'dB' suffix in core 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=20200214140555.3b732ad4@archlinux \
    --to=jic23@kernel.org \
    --cc=Michael.Hennerich@analog.com \
    --cc=beniamin.bia@analog.com \
    --cc=biabeniamin@outlook.com \
    --cc=devicetree@vger.kernel.org \
    --cc=knaack.h@gmx.de \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=pmeerw@pmeerw.net \
    --cc=robh+dt@kernel.org \
    /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).