Devicetree
 help / color / mirror / Atom feed
From: Antoniu Miclaus <antoniu.miclaus@analog.com>
To: <jic23@kernel.org>, <robh@kernel.org>, <conor+dt@kernel.org>,
	<linux-iio@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<devicetree@vger.kernel.org>
Cc: Antoniu Miclaus <antoniu.miclaus@analog.com>
Subject: [PATCH v3 0/3] iio: amplifiers: add support for ADL8113 Low Noise Amplifier
Date: Fri, 14 Nov 2025 11:57:22 +0000	[thread overview]
Message-ID: <20251114115725.5660-1-antoniu.miclaus@analog.com> (raw)

This patch series adds support for the Analog Devices ADL8113, a 10MHz to 12GHz
Low Noise Amplifier with integrated bypass switches.

The ADL8113 provides four operation modes controlled by two GPIO pins:
- Internal Amplifier (14dB gain)
- Internal Bypass (0dB gain)
- External Bypass A (0dB gain) - Signal routes from RFIN to OUT_A and from IN_A to RFOUT
- External Bypass B (0dB gain) - Signal routes from RFIN to OUT_B and from IN_B to RFOUT

The external bypass modes enable external signal processing, conditioning, or filtering
while maintaining signal integrity through dedicated signal paths.

Changes in v3:
- Refactor driver architecture to separate gain mode and signal path controls
- Replace single "mode" attribute with separate "signal_path" and "hardwaregain" attributes
- Add write support for hardwaregain to enable switching between amplifier (14dB) and bypass (0dB) modes
- Automatically handle signal path constraints (external paths force bypass mode)
- Simplify device tree bindings by removing extra blank line
- Update ABI documentation to reflect the new signal_path attribute interface
- Add comprehensive validation for gain/path combinations

Antoniu Miclaus (3):
  dt-bindings: iio: amplifiers: add adl8113
  iio: amplifiers: adl8113: add driver support
  Documentation: ABI: adl8113: add documentation

 .../testing/sysfs-bus-iio-amplifiers-adl8113  |  30 +++
 .../bindings/iio/amplifiers/adi,adl8113.yaml  |  64 +++++
 drivers/iio/amplifiers/Kconfig                |  12 +
 drivers/iio/amplifiers/Makefile               |   1 +
 drivers/iio/amplifiers/adl8113.c              | 252 ++++++++++++++++++
 5 files changed, 359 insertions(+)
 create mode 100644 Documentation/ABI/testing/sysfs-bus-iio-amplifiers-adl8113
 create mode 100644 Documentation/devicetree/bindings/iio/amplifiers/adi,adl8113.yaml
 create mode 100644 drivers/iio/amplifiers/adl8113.c

-- 
2.43.0


             reply	other threads:[~2025-11-14 11:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-14 11:57 Antoniu Miclaus [this message]
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
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=20251114115725.5660-1-antoniu.miclaus@analog.com \
    --to=antoniu.miclaus@analog.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jic23@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