Linux IIO development
 help / color / mirror / Atom feed
From: Marcelo Schmitt <marcelo.schmitt1@gmail.com>
To: Siddharth Menon <simeddon@gmail.com>
Cc: Jonathan Cameron <jic23@kernel.org>, linux-iio@vger.kernel.org
Subject: Re: GSoC IIO project: Siddharth Menon
Date: Mon, 3 Mar 2025 01:48:22 -0300	[thread overview]
Message-ID: <Z8U0lsntJpTuBzyT@debian-BULLSEYE-live-builder-AMD64> (raw)
In-Reply-To: <CAGd6pzOO_8VV8RPVz81-LE=eisuPjYsRQZAYgyfxwKLjKSM06Q@mail.gmail.com>

Hello Siddharth,

On 02/28, Siddharth Menon wrote:
> subject: Criteria for cleanup patch
> 
> Hello again,
> I was going through some of the staging drivers. There are quite a few
> checkpatch warnings under rtl8723bs, but they are mostly styling changes.
> Would sending in patches for these be appropriate?

Maybe. Though, I think rtl8723bs wouldn't belong to IIO (maybe
drivers/net/wireless) so I would ask that question at the wireless mailing list,
linux-wireless@vger.kernel.org.

> 
> I had considered dt bindings earlier as they seemed like a more relevant
> contribution.

I did a quick look at the IIO staging drivers and here are some comments and
improvement suggestions for those.

drivers/staging/iio/accel/adis16203.c
Suggested improvements:
- Use include/linux/units.h
- Drop spi_set_drvdata()

drivers/staging/iio/adc/ad7816.c
Looks interesting at first glance. Not complicated, yet something to play with
as they have a "control byte" to select which channel to read and a CONVST pin
to handle.

drivers/staging/iio/addac/adt7316*
The device can communicate through I2C or SPI so could use regmap API to
standardize data transfers in the driver.
There was an old patch updating to regmap
https://marc.info/?l=linux-iio&m=154853847705361&w=2.
Aside from I2C related changes by and minor clean up changes, this driver hasn't
got updates in a while.
Suggested improvements:
- Use regmap to standardize data transfers.
- Add devicetree documentation.
- Check/change if attributes can use standard ABI and document those that are specific.

drivers/staging/iio/frequency/ad9832*
Suggested improvements:
- Use devm_regulator_get_enable_read_voltage().
- Use FIELD_PREP to set bit fields.
- Support for devicetree probing (struct for device match of_device_id).
- Devicetree documentation.
- Maybe drop platform data stuff.
- Check/change if attributes can use standard ABI and document those that are specific.

drivers/staging/iio/frequency/ad9834*
Somewhat similar to ad9832. For updating the ABI, might be useful to check out
previous patch set
https://patchwork.kernel.org/project/linux-iio/patch/20190225191731.5822-2-beniamin.bia@analog.com/
Suggested improvements:
- Support for devicetree probing (struct for device match of_device_id).
- Devicetree documentation.
- Check/change if attributes can use standard ABI and document those that are specific.

drivers/staging/iio/impedance-analyzer/ad5933.c
Suggested improvements:
- Check/change if attributes can use standard ABI and document those that are specific.
- Better test?


Regards,
Marcelo

  reply	other threads:[~2025-03-03  4:47 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-21 15:53 GSoC IIO project: Siddharth Menon Siddharth Menon
2025-02-22 15:11 ` Jonathan Cameron
2025-02-28  5:37   ` Siddharth Menon
2025-03-03  4:48     ` Marcelo Schmitt [this message]
2025-03-05 13:36       ` Siddharth Menon
2025-03-05 14:07         ` Marcelo Schmitt
2025-03-05 14:57       ` Jonathan Cameron
2025-03-06 18:55         ` Siddharth Menon
2025-03-09 16:11           ` Jonathan Cameron
2025-04-07 22:45             ` Siddharth Menon
2025-04-08  3:57               ` Marcelo Schmitt
2025-04-08  7:40                 ` Siddharth Menon

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=Z8U0lsntJpTuBzyT@debian-BULLSEYE-live-builder-AMD64 \
    --to=marcelo.schmitt1@gmail.com \
    --cc=jic23@kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=simeddon@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