From: Jonathan Cameron <jic23@kernel.org>
To: Antoniu Miclaus <antoniu.miclaus@analog.com>
Cc: <robh@kernel.org>, <conor+dt@kernel.org>,
<linux-iio@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<devicetree@vger.kernel.org>
Subject: Re: [PATCH v3 2/3] iio: amplifiers: adl8113: add driver support
Date: Sun, 16 Nov 2025 15:38:19 +0000 [thread overview]
Message-ID: <20251116153819.7afc9de0@jic23-huawei> (raw)
In-Reply-To: <20251114115725.5660-3-antoniu.miclaus@analog.com>
On Fri, 14 Nov 2025 11:57:24 +0000
Antoniu Miclaus <antoniu.miclaus@analog.com> wrote:
> Add support for adl8113 10MHz to 12GHz Low Noise Amplifier with
> 10MHz to 14GHz bypass switches.
>
> Signed-off-by: Antoniu Miclaus <antoniu.miclaus@analog.com>
Hi Antoniu
A few really minor things inline that are in the category of
things I'd just tidy up whilst applying.
However, I want to know more about real usecases. Probably best
place to discuss those is wrt to patch 3 so I'll reply to that.
> diff --git a/drivers/iio/amplifiers/adl8113.c b/drivers/iio/amplifiers/adl8113.c
> new file mode 100644
> index 000000000000..155291f4ec89
> --- /dev/null
> +++ b/drivers/iio/amplifiers/adl8113.c
> @@ -0,0 +1,252 @@
> +// SPDX-License-Identifier: GPL-2.0
> +/*
> + * ADL8113 Low Noise Amplifier with integrated bypass switches
> + *
> + * Copyright 2025 Analog Devices Inc.
> + */
> +
> +#include <linux/array_size.h>
> +#include <linux/device.h>
> +#include <linux/err.h>
> +#include <linux/gpio/consumer.h>
> +#include <linux/iio/iio.h>
> +#include <linux/mod_devicetable.h>
> +#include <linux/module.h>
> +#include <linux/platform_device.h>
> +#include <linux/property.h>
> +#include <linux/regulator/consumer.h>
> +#include <linux/slab.h>
> +#include <linux/sysfs.h>
Is this used?
> +static const char * const adl8113_supply_names[] = {
> + "vdd1",
> + "vdd2",
> + "vss2"
This one should have a trailing comma because maybe we'll have
another supply at some future point. At very least it's not obvious
from code alone that we never will so convention is to have that comma.
> +};
> +
> +static const struct iio_chan_spec_ext_info adl8113_ext_info[] = {
> + IIO_ENUM("signal_path", IIO_SHARED_BY_ALL, &adl8113_signal_path_enum),
> + IIO_ENUM_AVAILABLE("signal_path", IIO_SHARED_BY_ALL,
> + &adl8113_signal_path_enum),
> + { },
Trivial but no trailing comma given nothing can come after this.
> +};
next prev parent reply other threads:[~2025-11-16 15:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-14 11:57 [PATCH v3 0/3] iio: amplifiers: add support for ADL8113 Low Noise Amplifier Antoniu Miclaus
2025-11-14 11:57 ` [PATCH v3 1/3] dt-bindings: iio: amplifiers: add adl8113 Antoniu Miclaus
2025-11-17 19:22 ` Conor Dooley
2025-11-17 23:42 ` David Lechner
2025-11-14 11:57 ` [PATCH v3 2/3] iio: amplifiers: adl8113: add driver support Antoniu Miclaus
2025-11-16 15:38 ` Jonathan Cameron [this message]
2025-11-14 11:57 ` [PATCH v3 3/3] Documentation: ABI: adl8113: add documentation Antoniu Miclaus
2025-11-16 15:50 ` Jonathan Cameron
2025-11-17 23:59 ` David Lechner
2025-11-18 8:08 ` Nuno Sá
2025-11-19 9:09 ` Miclaus, Antoniu
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=20251116153819.7afc9de0@jic23-huawei \
--to=jic23@kernel.org \
--cc=antoniu.miclaus@analog.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@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