From: David Lechner <dlechner@baylibre.com>
To: Bhargav Joshi <rougueprince47@gmail.com>,
lars@metafoo.de, Michael.Hennerich@analog.com, jic23@kernel.org
Cc: nuno.sa@analog.com, andy@kernel.org, linux-iio@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-staging@lists.linux.dev
Subject: Re: [RFC PATCH] staging: iio: ad9832: modernize ABI and remove dds.h dependency
Date: Sat, 7 Mar 2026 12:24:59 -0600 [thread overview]
Message-ID: <97043046-0cf7-4762-9a3e-67f1f47a2694@baylibre.com> (raw)
In-Reply-To: <20260305210347.120446-1-rougueprince47@gmail.com>
On 3/5/26 3:03 PM, Bhargav Joshi wrote:
> The AD9832 driver currently relies on legacy custom IIO macros defined
> in dds.h. This triggers checkpatch.pl warnings (NON_OCTAL_PERMISSIONS)
> and, more importantly, exposes a non-standard sysfs ABI (e.g.,
> frequency0, frequency1, phase0-3) directly to user space.
>
> This patch removes the custom macros and migrates the driver to standard
> IIO API mechanisms:
> - Standard attributes (frequency, phase) now use info_mask_separate.
> - Non standard specific toggles (frequencysymbol, phasesymbol,
> pincontrol) have been migrated to an ext_info array.
> - Remove dds.h header dependency.
> - Pointless frequency_scale and phase_scale attributes are dropped as
> suggested by Jonathan in
> https://lore.kernel.org/linux-iio/20251231180939.422e9e62@jic23-huawei/
>
> NOTE: This patch introduces an intentional ABI changes. The non-standard
> attributes (out_altvoltage0_frequency0, etc.) have been removed. They
> are replaced by standard attributes (out_altvoltage0_frequency and
> out_altvoltage0_phase). Routing to correct register while writing is
> handled by checking currently active frequencysymbol or phasesymbol.
>
> Testing: This patch has been strictly compile-tested. I do not have
> access to physical AD9832 hardware. I am submitting this as an RFC to
> see if these changes are acceptable, and to ask if someone with physical
> hardware could test thisg and provide a Tested-by tag.
>
Since this is changing ABI, I think it would best if someone who actually
has the hardware and plans to use it should be making the changes to
make sure they actually work as intended.
next prev parent reply other threads:[~2026-03-07 18:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-05 21:03 [RFC PATCH] staging: iio: ad9832: modernize ABI and remove dds.h dependency Bhargav Joshi
2026-03-07 18:24 ` David Lechner [this message]
2026-03-07 21:05 ` Marcelo Schmitt
2026-03-07 21:18 ` Marcelo Schmitt
2026-03-08 23:44 ` Bhargav Joshi
2026-03-08 18:31 ` Jonathan Cameron
2026-03-08 23:19 ` Bhargav Joshi
2026-03-22 12:08 ` Jonathan Cameron
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=97043046-0cf7-4762-9a3e-67f1f47a2694@baylibre.com \
--to=dlechner@baylibre.com \
--cc=Michael.Hennerich@analog.com \
--cc=andy@kernel.org \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=nuno.sa@analog.com \
--cc=rougueprince47@gmail.com \
/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