From: Tomas Borquez <tomasborquez13@gmail.com>
To: Jonathan Cameron <jic23@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Lars-Peter Clausen <lars@metafoo.de>,
Michael Hennerich <Michael.Hennerich@analog.com>
Cc: "David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
linux-kernel@vger.kernel.org, linux-iio@vger.kernel.org,
linux-staging@lists.linux.dev,
"Tomas Borquez" <tomasborquez13@gmail.com>
Subject: [PATCH 0/5] staging: ad9832: driver cleanup
Date: Mon, 15 Dec 2025 16:08:01 -0300 [thread overview]
Message-ID: <20251215190806.11003-1-tomasborquez13@gmail.com> (raw)
This series cleans up the ad9832 driver with the goal of (eventually)
graduating it from staging. The main change is converting custom sysfs
attributes to IIO channel interface and adding sysfs documentation.
Changes since RFC:
- Split unrelated changes into separate patches: whitespace cleanup,
guard() conversion and dev_err_probe() (Jonathan)
- Changed channel type from IIO_ALTVOLTAGE to IIO_ALTCURRENT since
this is a current source DAC (Jonathan)
- Kept single channel with ext_info for frequencyN/phaseN attributes
rather than multiple indexed channels, as the device has only one
output (Jonathan)
- Phase attributes now accept radians directly instead of raw register
values, driver performs the conversion internally (Jonathan)
- Added read callbacks for frequency and phase attributes
- Added TODO comment for pincontrol_en noting it should become a DT
property during graduation (Jonathan)
- Added ABI documentation for new sysfs attributes
Tomas Borquez (5):
staging: iio: ad9832: clean up whitespace
staging: iio: ad9832: convert to guard(mutex)
staging: iio: ad9832: cleanup dev_err_probe()
staging: iio: ad9832: convert to iio channels and ext_info attrs
staging: iio: ad9832: add sysfs documentation
.../Documentation/sysfs-bus-iio-dds-ad9832 | 41 +++
drivers/staging/iio/frequency/ad9832.c | 315 +++++++++++++-----
2 files changed, 270 insertions(+), 86 deletions(-)
create mode 100644 drivers/staging/iio/Documentation/sysfs-bus-iio-dds-ad9832
--
2.43.0
next reply other threads:[~2025-12-15 19:08 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-15 19:08 Tomas Borquez [this message]
2025-12-15 19:08 ` [PATCH 1/5] staging: iio: ad9832: clean up whitespace Tomas Borquez
2025-12-18 14:27 ` Marcelo Schmitt
2025-12-21 19:17 ` Jonathan Cameron
2025-12-15 19:08 ` [PATCH 2/5] staging: iio: ad9832: convert to guard(mutex) Tomas Borquez
2025-12-18 14:34 ` Marcelo Schmitt
2025-12-18 15:16 ` Tomas Borquez
2025-12-21 19:22 ` Jonathan Cameron
2025-12-15 19:08 ` [PATCH 3/5] staging: iio: ad9832: cleanup dev_err_probe() Tomas Borquez
2025-12-18 14:38 ` Marcelo Schmitt
2025-12-21 19:25 ` Jonathan Cameron
2025-12-15 19:08 ` [PATCH 4/5] staging: iio: ad9832: convert to iio channels and ext_info attrs Tomas Borquez
2025-12-18 15:04 ` Marcelo Schmitt
2025-12-18 15:46 ` Tomas Borquez
2025-12-21 19:36 ` Jonathan Cameron
2025-12-15 19:08 ` [PATCH 5/5] staging: iio: ad9832: add sysfs documentation Tomas Borquez
2025-12-18 15:10 ` Marcelo Schmitt
2025-12-21 19:43 ` 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=20251215190806.11003-1-tomasborquez13@gmail.com \
--to=tomasborquez13@gmail.com \
--cc=Michael.Hennerich@analog.com \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=gregkh@linuxfoundation.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 \
/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