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 v2 3/6] iio: dac: ad5686: refactor device list and file header comments
Date: Fri, 24 Jul 2026 12:16:37 +0000	[thread overview]
Message-ID: <20260724121637.EB3811F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260724-ad5686-extend-dev-support-v2-3-cfc2b30ce988@analog.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] Incomplete implementation of device removal: AD5337R is left in ID tables despite commit message claim.
--

--- Patch [3]: [PATCH v2 3/6] iio: dac: ad5686: refactor device list and file header comments ---
commit f78bcff1ca70cede516f95f60a18e8d26ad243b8
Author: Rodrigo Alencar <rodrigo.alencar@analog.com>

iio: dac: ad5686: refactor device list and file header comments

This commit refactors the Kconfig device list by sorting devices by channel
count and removes device descriptions from the file headers. It also states
in the commit message that AD5337R is being omitted.

> AD5337R is ommited as it does not seem to exist, i.e. its documentation could not be found.

[Severity: Medium]
Is the removal of AD5337R incomplete in this patch?

The commit message notes that AD5337R is omitted, and it was removed from
the Kconfig text, but the driver still registers the device.

For example, it remains in the i2c_device_id table:

drivers/iio/dac/ad5696-i2c.c:ad5686_i2c_id[] = {
    ...
    { .name = "ad5337r", .driver_data = (kernel_ulong_t)&ad5337r_chip_info },
    ...
}

It also remains in the of_device_id table in the same file:

drivers/iio/dac/ad5696-i2c.c:ad5686_of_match[] = {
    ...
    { .compatible = "adi,ad5337r", .data = &ad5337r_chip_info },
    ...
}

The core driver also still exports its chip info structure:

drivers/iio/dac/ad5686.c:
const struct ad5686_chip_info ad5337r_chip_info = {
    .channels = ad5337r_channels,
    .int_vref_mv = 2500,
    .num_channels = 2,
    .regmap_type = AD5686_REGMAP,
};
EXPORT_SYMBOL_NS_GPL(ad5337r_chip_info, "IIO_AD5686");

Should these entries be removed as well to fully drop the device support?

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260724-ad5686-extend-dev-support-v2-0-cfc2b30ce988@analog.com?part=3

  reply	other threads:[~2026-07-24 12:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-24 12:03 [PATCH v2 0/6] iio: dac: ad5686: extend device support Rodrigo Alencar via B4 Relay
2026-07-24 12:03 ` [PATCH v2 1/6] dt-bindings: iio: dac: ad5696: add AD5673R/AD5677R support Rodrigo Alencar via B4 Relay
2026-07-24 12:18   ` sashiko-bot
2026-07-24 12:03 ` [PATCH v2 2/6] iio: dac: ad5696: add AD5673R/AD5677R entries to of_match table Rodrigo Alencar via B4 Relay
2026-07-24 12:03 ` [PATCH v2 3/6] iio: dac: ad5686: refactor device list and file header comments Rodrigo Alencar via B4 Relay
2026-07-24 12:16   ` sashiko-bot [this message]
2026-07-24 12:03 ` [PATCH v2 4/6] dt-bindings: iio: dac: ad5696: extend device support Rodrigo Alencar via B4 Relay
2026-07-24 12:17   ` sashiko-bot
2026-07-24 12:03 ` [PATCH v2 5/6] dt-bindings: iio: dac: ad5686: " Rodrigo Alencar via B4 Relay
2026-07-24 12:03 ` [PATCH v2 6/6] iio: dac: ad5686: extend device support with new parts 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=20260724121637.EB3811F000E9@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