Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Rodrigo Alencar" <rodrigo.alencar@analog.com>
Cc: robh@kernel.org, conor+dt@kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v8 02/17] iio: ABI: raw, scale and offset for frequency/phase channels
Date: Tue, 14 Jul 2026 11:25:16 +0000	[thread overview]
Message-ID: <20260714112517.224631F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260714-ad9910-iio-driver-v8-2-36939c3c07d2@analog.com>

Thank you for your contribution! Sashiko AI review found 3 potential issue(s) to consider:
- [Low] Missing ABI documentation for 'in_' scale and offset attributes for frequency and phase channels.
- [Low] Incorrect KernelVersion inherited for new ABI entry `out_phaseY_raw`.
- [Low] Documenting ABI attributes for a non-existent IIO channel type (`frequency`).
--

--- Patch [2]: [PATCH v8 02/17] iio: ABI: raw, scale and offset for frequency/phase channels ---
commit 757abc8c6b95afb7c57d216bb7e4723c3c34e298
Author: Rodrigo Alencar <rodrigo.alencar@analog.com>

iio: ABI: raw, scale and offset for frequency/phase channels

Consider scale and offset attributes for frequency and phase channels.
Frequency channels are going to be introduced later alongside a DDS
device driver which is going to leverage those new attributes.

> diff --git a/Documentation/ABI/testing/sysfs-bus-iio b/Documentation/ABI/testing/sysfs-bus-iio
> index 90047189c3ebe..7ef0db8dad40f 100644
> --- a/Documentation/ABI/testing/sysfs-bus-iio
> +++ b/Documentation/ABI/testing/sysfs-bus-iio
> @@ -441,6 +441,10 @@ What:		/sys/bus/iio/devices/iio:deviceX/in_voltageY_i_offset
>  What:		/sys/bus/iio/devices/iio:deviceX/in_voltageY_q_offset
>  What:		/sys/bus/iio/devices/iio:deviceX/in_currentY_offset
>  What:		/sys/bus/iio/devices/iio:deviceX/in_current_offset
> +What:		/sys/bus/iio/devices/iio:deviceX/out_phaseY_offset
> +What:		/sys/bus/iio/devices/iio:deviceX/out_phase_offset
> +What:		/sys/bus/iio/devices/iio:deviceX/out_frequencyY_offset
> +What:		/sys/bus/iio/devices/iio:deviceX/out_frequency_offset
>  What:		/sys/bus/iio/devices/iio:deviceX/in_tempY_offset
>  What:		/sys/bus/iio/devices/iio:deviceX/in_temp_offset
>  What:		/sys/bus/iio/devices/iio:deviceX/in_pressureY_offset
> @@ -474,6 +478,10 @@ What:		/sys/bus/iio/devices/iio:deviceX/in_voltage_scale
>  What:		/sys/bus/iio/devices/iio:deviceX/in_voltage-voltage_scale
>  What:		/sys/bus/iio/devices/iio:deviceX/out_voltageY_scale
>  What:		/sys/bus/iio/devices/iio:deviceX/out_altvoltageY_scale
> +What:		/sys/bus/iio/devices/iio:deviceX/out_phaseY_scale
> +What:		/sys/bus/iio/devices/iio:deviceX/out_phase_scale
> +What:		/sys/bus/iio/devices/iio:deviceX/out_frequencyY_scale
> +What:		/sys/bus/iio/devices/iio:deviceX/out_frequency_scale

[Severity: Low]
Should the 'in_' variants for these scale and offset attributes be
documented here as well?

The description added later in this patch for in_frequencyY_raw mentions
that scale and offset are applied, but only the 'out_' variants are
being documented here.

>  What:		/sys/bus/iio/devices/iio:deviceX/in_currentY_scale
>  What:		/sys/bus/iio/devices/iio:deviceX/in_currentY_supply_scale

[ ... ]

> @@ -2147,7 +2155,16 @@ Description:
>  		specific attributes. This is useful for userspace to be able to
>  		better identify an individual channel.
>  
> +What:		/sys/bus/iio/devices/iio:deviceX/in_frequencyY_raw
> +What:		/sys/bus/iio/devices/iio:deviceX/out_frequencyY_raw

[Severity: Low]
The commit message notes that frequency channels will be introduced
later. Is it standard practice to document ABI attributes for a channel
type (like IIO_FREQUENCY) before the channel type exists in the IIO
core?

> +KernelVersion:	7.3
> +Contact:	linux-iio@vger.kernel.org
> +Description:
> +		Raw (unscaled) frequency reading from channel Y.
> +		Units after application of scale and offset are Hz.
> +
>  What:		/sys/bus/iio/devices/iio:deviceX/in_phaseY_raw
> +What:		/sys/bus/iio/devices/iio:deviceX/out_phaseY_raw
>  KernelVersion:	4.18

[Severity: Low]
Does grouping out_phaseY_raw here incorrectly imply that it was
introduced in KernelVersion 4.18, rather than the current release?

>  Contact:	linux-iio@vger.kernel.org
>  Description:

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260714-ad9910-iio-driver-v8-0-36939c3c07d2@analog.com?part=2

  reply	other threads:[~2026-07-14 11:25 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-14 11:02 [PATCH v8 00/17] AD9910 Direct Digital Synthesizer Rodrigo Alencar via B4 Relay
2026-07-14 11:02 ` [PATCH v8 01/17] iio: ABI: add attributes for altcurrent channels Rodrigo Alencar via B4 Relay
2026-07-14 11:14   ` sashiko-bot
2026-07-14 11:02 ` [PATCH v8 02/17] iio: ABI: raw, scale and offset for frequency/phase channels Rodrigo Alencar via B4 Relay
2026-07-14 11:25   ` sashiko-bot [this message]
2026-07-14 11:02 ` [PATCH v8 03/17] iio: ABI: add parent entry for iio channels Rodrigo Alencar via B4 Relay
2026-07-14 11:02 ` [PATCH v8 04/17] iio: add IIO_FREQUENCY channel type Rodrigo Alencar via B4 Relay
2026-07-14 11:02 ` [PATCH v8 05/17] iio: core: support 64-bit register through debugfs Rodrigo Alencar via B4 Relay
2026-07-14 11:02 ` [PATCH v8 06/17] iio: core: create local __iio_chan_prefix_emit() for reuse Rodrigo Alencar via B4 Relay
2026-07-14 11:46   ` Andy Shevchenko
2026-07-14 11:02 ` [PATCH v8 07/17] iio: test: add kunit tests for channel prefix naming generation Rodrigo Alencar via B4 Relay
2026-07-14 12:12   ` sashiko-bot
2026-07-14 11:02 ` [PATCH v8 08/17] iio: core: add hierarchical channel relationships Rodrigo Alencar via B4 Relay
2026-07-14 11:02 ` [PATCH v8 09/17] dt-bindings: iio: frequency: add ad9910 Rodrigo Alencar via B4 Relay
2026-07-14 11:02 ` [PATCH v8 10/17] iio: frequency: ad9910: initial driver implementation Rodrigo Alencar via B4 Relay
2026-07-14 12:29   ` sashiko-bot
2026-07-14 11:02 ` [PATCH v8 11/17] iio: frequency: ad9910: add basic parallel port support Rodrigo Alencar via B4 Relay
2026-07-14 11:02 ` [PATCH v8 12/17] iio: frequency: ad9910: add digital ramp generator support Rodrigo Alencar via B4 Relay
2026-07-14 11:02 ` [PATCH v8 13/17] iio: frequency: ad9910: add RAM mode support Rodrigo Alencar via B4 Relay
2026-07-14 13:17   ` sashiko-bot
2026-07-14 11:02 ` [PATCH v8 14/17] iio: frequency: ad9910: add output shift keying support Rodrigo Alencar via B4 Relay
2026-07-14 11:02 ` [PATCH v8 15/17] iio: frequency: ad9910: show channel priority in debugfs Rodrigo Alencar via B4 Relay
2026-07-14 11:02 ` [PATCH v8 16/17] iio: ABI: add docs for ad9910 sysfs and debugfs entries Rodrigo Alencar via B4 Relay
2026-07-14 11:02 ` [PATCH v8 17/17] docs: iio: add documentation for ad9910 driver Rodrigo Alencar via B4 Relay

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=20260714112517.224631F000E9@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=rodrigo.alencar@analog.com \
    --cc=sashiko-reviews@lists.linux.dev \
    /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