devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Ana-Maria Cusco <ana-maria.cusco@analog.com>
Cc: Michael Hennerich <michael.hennerich@analog.com>,
	Lars-Peter Clausen <lars@metafoo.de>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Conor Dooley <conor+dt@kernel.org>, <linux-iio@vger.kernel.org>,
	<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] iio: amplifiers: hmc425a: Add Support HMC540S 4-bit Attenuator
Date: Mon, 28 Aug 2023 15:35:22 +0100	[thread overview]
Message-ID: <20230828153522.754cb7ff@jic23-huawei> (raw)
In-Reply-To: <20230816110906.144540-1-ana-maria.cusco@analog.com>

On Wed, 16 Aug 2023 14:09:05 +0300
Ana-Maria Cusco <ana-maria.cusco@analog.com> wrote:

> From: Michael Hennerich <michael.hennerich@analog.com>
> 
> This adds support for the Analog Devices HMC540s 1 dB LSB
> Silicon MMIC 4-Bit Digital Positive Control Attenuator, 0.1 - 8 GHz
> 
> Signed-off-by: Ana-Maria Cusco <ana-maria.cusco@analog.com>

Hi Ana-Maria

Generally for all but single patch series, I'd prefer a cover letter.
For new drivers, just put a short description of the device in there.
There are various reasons, but the simplest one is that it provides
a place where people can offer Reviewed-by etc for the whole series
in a form that the b4 tool I (and lots of other maintainers) use can
pick it up automatically.

Anyhow, actual patches look great to me.

Applied to the togreg branch of iio.git and pushed out as testing for now.
I will be rebasing on 5.6-rc1 once it's available after which these should
get picked up by linux-next.

Thanks,

Jonathan

> ---
>  drivers/iio/amplifiers/hmc425a.c | 17 +++++++++++++++++
>  1 file changed, 17 insertions(+)
> 
> diff --git a/drivers/iio/amplifiers/hmc425a.c b/drivers/iio/amplifiers/hmc425a.c
> index 108f0f1685ef..e87d35d50a95 100644
> --- a/drivers/iio/amplifiers/hmc425a.c
> +++ b/drivers/iio/amplifiers/hmc425a.c
> @@ -21,6 +21,7 @@
>  
>  enum hmc425a_type {
>  	ID_HMC425A,
> +	ID_HMC540S,
>  };
>  
>  struct hmc425a_chip_info {
> @@ -70,6 +71,9 @@ static int hmc425a_read_raw(struct iio_dev *indio_dev,
>  		case ID_HMC425A:
>  			gain = ~code * -500;
>  			break;
> +		case ID_HMC540S:
> +			gain = ~code * -1000;
> +			break;
>  		}
>  
>  		*val = gain / 1000;
> @@ -106,6 +110,9 @@ static int hmc425a_write_raw(struct iio_dev *indio_dev,
>  	case ID_HMC425A:
>  		code = ~((abs(gain) / 500) & 0x3F);
>  		break;
> +	case ID_HMC540S:
> +		code = ~((abs(gain) / 1000) & 0xF);
> +		break;
>  	}
>  
>  	mutex_lock(&st->lock);
> @@ -157,6 +164,7 @@ static const struct iio_chan_spec hmc425a_channels[] = {
>  /* Match table for of_platform binding */
>  static const struct of_device_id hmc425a_of_match[] = {
>  	{ .compatible = "adi,hmc425a", .data = (void *)ID_HMC425A },
> +	{ .compatible = "adi,hmc540s", .data = (void *)ID_HMC540S },
>  	{},
>  };
>  MODULE_DEVICE_TABLE(of, hmc425a_of_match);
> @@ -171,6 +179,15 @@ static struct hmc425a_chip_info hmc425a_chip_info_tbl[] = {
>  		.gain_max = 0,
>  		.default_gain = -0x40, /* set default gain -31.5db*/
>  	},
> +	[ID_HMC540S] = {
> +		.name = "hmc540s",
> +		.channels = hmc425a_channels,
> +		.num_channels = ARRAY_SIZE(hmc425a_channels),
> +		.num_gpios = 4,
> +		.gain_min = -15000,
> +		.gain_max = 0,
> +		.default_gain = -0x10, /* set default gain -15.0db*/
> +	},
>  };
>  
>  static int hmc425a_probe(struct platform_device *pdev)


      parent reply	other threads:[~2023-08-28 14:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-16 11:09 [PATCH 1/2] iio: amplifiers: hmc425a: Add Support HMC540S 4-bit Attenuator Ana-Maria Cusco
2023-08-16 11:09 ` [PATCH 2/2] dt-bindings: iio: hmc425a: add entry for HMC540S Ana-Maria Cusco
2023-08-16 14:36   ` Conor Dooley
2023-09-12  6:36     ` Hennerich, Michael
2023-09-12  6:56       ` Krzysztof Kozlowski
2023-09-12  9:16         ` Jonathan Cameron
2023-09-12 11:28           ` Hennerich, Michael
2023-08-28 14:35 ` 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=20230828153522.754cb7ff@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=ana-maria.cusco@analog.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michael.hennerich@analog.com \
    --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).