Linux IIO development
 help / color / mirror / Atom feed
From: Joshua Crofts <joshua.crofts1@gmail.com>
To: Yuval Saar <thefireking@gmail.com>
Cc: linux-iio@vger.kernel.org, jic23@kernel.org,
	dlechner@baylibre.com, nuno.sa@analog.com, andy@kernel.org,
	maxwell@maxwelld.cc
Subject: Re: [PATCH v3 0/2] iio: adc: mcp3422: chip info and read_avail()
Date: Sat, 3 Oct 2026 15:40:36 +0200	[thread overview]
Message-ID: <20261003154036.0000115b@gmail.com> (raw)
In-Reply-To: <20261003001647.1975549-1-thefireking@gmail.com>

On Sat,  3 Oct 2026 03:16:45 +0300
Yuval Saar <thefireking@gmail.com> wrote:

> The MCP3422 family driver tells the parts apart with integer ids and
> a switch in probe, and it exposes the sampling-frequency and scale
> lists through custom sysfs show functions.
> 
> Move those differences into a per-chip structure, then publish the
> lists with read_avail() so the IIO core creates the attributes and
> in-kernel consumers can query them.
> 
> sampling_frequency_available stays shared by all.
> in_voltage_scale_available stays shared by type. Shared by direction
> would rename that file to in_scale_available.
> 
> No hardware. Each patch compiles. checkpatch --strict is clean, and
> the available-list text was checked against the IIO core formatters.
> 
> v3:
> - Split the chip-info change into its own precursor patch.
> - Drop the sample-rate defines that only repeated the numeric value.
> - Keep scale's available mask shared by type, so the sysfs name stays
>   in_voltage_scale_available.
> - Store scales as { integer, nano } pairs.
> v2: https://lore.kernel.org/linux-iio/20260921044709.27d59a97@jic23-hlaptop/
> v1: https://lore.kernel.org/linux-iio/20260919195507.94130-1-thefireking@gmail.com/
>

Do not send new versions as a reply to the previous version,
this messes up tooling like b4 and can appear obscured in people's
email clients.

-- 
Kind regards,
Joshua Crofts

      parent reply	other threads:[~2026-10-03 13:40 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-19 19:55 [PATCH] iio: adc: mcp3422: use sysfs_emit() in show functions Angel2Eyes
2026-09-19 22:33 ` Maxwell Doose
2026-09-19 22:45   ` Joshua Crofts
2026-09-20  0:30 ` Jonathan Cameron
2026-09-20 16:00 ` [PATCH v2] iio: adc: mcp3422: use read_avail() for available attributes Yuval Saar
2026-09-21  3:47   ` Jonathan Cameron
2026-09-25 16:50     ` Andy Shevchenko
2026-10-03  0:16 ` [PATCH v3 0/2] iio: adc: mcp3422: chip info and read_avail() Yuval Saar
2026-10-03  0:16   ` [PATCH v3 1/2] iio: adc: mcp3422: describe parts with chip_info Yuval Saar
2026-10-03 20:37     ` Andy Shevchenko
2026-10-04 16:38     ` Jonathan Cameron
2026-10-03  0:16   ` [PATCH v3 2/2] iio: adc: mcp3422: use read_avail() for available attributes Yuval Saar
2026-10-03 13:40   ` Joshua Crofts [this message]

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=20261003154036.0000115b@gmail.com \
    --to=joshua.crofts1@gmail.com \
    --cc=andy@kernel.org \
    --cc=dlechner@baylibre.com \
    --cc=jic23@kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=maxwell@maxwelld.cc \
    --cc=nuno.sa@analog.com \
    --cc=thefireking@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