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 v2 3/3] Documentation: ABI: adl8113: add documentation
Date: Sun, 9 Nov 2025 17:18:22 +0000 [thread overview]
Message-ID: <20251109171822.135460aa@jic23-huawei> (raw)
In-Reply-To: <20251108174357.3748-4-antoniu.miclaus@analog.com>
On Sat, 8 Nov 2025 17:43:54 +0000
Antoniu Miclaus <antoniu.miclaus@analog.com> wrote:
> Add ABI documentation for the ADL8113 Low Noise Amplifier,
> covering the 4 pin-selectable operating modes.
>
> Signed-off-by: Antoniu Miclaus <antoniu.miclaus@analog.com>
I'm still reluctant to have a mode parameter because they are close
to unusable because they always indicate something highly device
specific that no generic userspace can make use of.
My hang up continues to be that the first two are normal _scale
controls, but the 2nd two are saying use this path for the signal
with analog components in it, but providing no info on what that
means wrt to what is measured.
If we do go ahead with this, then it needs a more specific name
to avoid trampling on the namespace as "mode" would.
> ---
>
> Changes in v2:
> - Enhance external_bypass_a mode description: clarify signal routing from RFIN to OUT_A and from IN_A to RFOUT
> - Enhance external_bypass_b mode description: clarify signal routing from RFIN to OUT_B and from IN_B to RFOUT
> .../testing/sysfs-bus-iio-amplifiers-adl8113 | 32 +++++++++++++++++++
> 1 file changed, 32 insertions(+)
> create mode 100644 Documentation/ABI/testing/sysfs-bus-iio-amplifiers-adl8113
>
> diff --git a/Documentation/ABI/testing/sysfs-bus-iio-amplifiers-adl8113 b/Documentation/ABI/testing/sysfs-bus-iio-amplifiers-adl8113
> new file mode 100644
> index 000000000000..6e3994283a45
> --- /dev/null
> +++ b/Documentation/ABI/testing/sysfs-bus-iio-amplifiers-adl8113
> @@ -0,0 +1,32 @@
> +What: /sys/bus/iio/devices/iio:deviceX/mode
> +Date: January 2025
> +KernelVersion: 6.14
> +Contact: linux-iio@vger.kernel.org
> +Description:
> + This attribute allows the user to set the operation mode of the
> + ADL8113 Low Noise Amplifier. The available modes control signal
> + routing through different paths within the device.
> +
> + The supported modes are:
> +
> + * internal_amplifier - Signal passes through the internal low
> + noise amplifier (VA=0, VB=0). Provides 14dB gain.
> +
> + * internal_bypass - Signal bypasses through internal bypass path
> + (VA=1, VB=1). Provides 0dB gain.
> +
> + * external_bypass_a - Signal routes from RFIN to OUT_A and from IN_A to RFOUT
> + (VA=0, VB=1). Provides 0dB gain.
> +
> + * external_bypass_b - Signal routes from RFIN to OUT_B and from IN_B to RFOUT
> + (VA=1, VB=0). Provides 0dB gain.
> +
> +What: /sys/bus/iio/devices/iio:deviceX/mode_available
> +Date: January 2025
> +KernelVersion: 6.14
> +Contact: linux-iio@vger.kernel.org
> +Description:
> + Reading this attribute returns a space-separated list of all
> + available operation modes for the ADL8113 device. The modes
> + control the signal path and determine whether the signal passes
> + through the internal amplifier or various bypass paths.
prev parent reply other threads:[~2025-11-09 17:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-08 17:43 [PATCH v2 0/3] iio: amplifiers: add support for ADL8113 Low Noise Amplifier Antoniu Miclaus
2025-11-08 17:43 ` [PATCH v2 1/3] dt-bindings: iio: amplifiers: add adl8113 Antoniu Miclaus
2025-11-08 18:25 ` Rob Herring (Arm)
2025-11-08 17:43 ` [PATCH v2 2/3] iio: amplifiers: adl8113: add driver support Antoniu Miclaus
2025-11-09 17:22 ` Jonathan Cameron
2025-11-11 14:06 ` Miclaus, Antoniu
2025-11-15 18:12 ` Jonathan Cameron
2025-11-08 17:43 ` [PATCH v2 3/3] Documentation: ABI: adl8113: add documentation Antoniu Miclaus
2025-11-09 17:18 ` 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=20251109171822.135460aa@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