Linux IIO development
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Marcelo Schmitt <marcelo.schmitt1@gmail.com>
Cc: Siddharth Menon <simeddon@gmail.com>, linux-iio@vger.kernel.org
Subject: Re: GSoC IIO project: Siddharth Menon
Date: Wed, 5 Mar 2025 14:57:49 +0000	[thread overview]
Message-ID: <20250305145749.413fe30b@jic23-huawei> (raw)
In-Reply-To: <Z8U0lsntJpTuBzyT@debian-BULLSEYE-live-builder-AMD64>


> 
> 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.

This one is an interesting part - I have one somewhere from trying to help
on the previous go at cleaning it up.  One issue is that I couldn't manage
to get a stable SPI connection patched onto the dev board.  It kind of
worked if I used a long cable and did a rain dance, but not enough to really
test it.

Jonathan

  parent reply	other threads:[~2025-03-05 14:57 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
2025-03-05 13:36       ` Siddharth Menon
2025-03-05 14:07         ` Marcelo Schmitt
2025-03-05 14:57       ` Jonathan Cameron [this message]
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=20250305145749.413fe30b@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=marcelo.schmitt1@gmail.com \
    --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