From: David Lechner <dlechner@baylibre.com>
To: Antoniu Miclaus <antoniu.miclaus@analog.com>,
jic23@kernel.org, robh@kernel.org, conor+dt@kernel.org,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-pwm@vger.kernel.org
Subject: Re: [PATCH v8 8/8] iio: adc: ad4851: add ad485x driver
Date: Fri, 13 Dec 2024 17:43:06 -0600 [thread overview]
Message-ID: <2f7c5893-695c-4633-9142-10e70c1b3220@baylibre.com> (raw)
In-Reply-To: <20241213164445.23195-8-antoniu.miclaus@analog.com>
On 12/13/24 10:44 AM, Antoniu Miclaus wrote:
> Add support for the AD485X a fully buffered, 8-channel simultaneous
> sampling, 16/20-bit, 1 MSPS data acquisition system (DAS) with
> differential, wide common-mode range inputs.
>
> Signed-off-by: Antoniu Miclaus <antoniu.miclaus@analog.com>
> ---
> changes in v8:
> - fix kernel bot warnings.
> - drop optional members from chip info struct
> - drop final line continuation
> - drop ext_scan_type and num_ext_scan_type duplicate set.
> - create common function for parsing channels to avoid code duplication.
> - add comment for fields not set in the parts chip info struct.
> - add safety margin for pwm duty cycle.
> - use FIELD_PREP where indicated.
> - use chip resolution instead of chan->scan_type.realbits where indicated.
> - move the reset procedure before setting refbuf/refsel registers.
> - use iio_get_current_scan_type where indicated.
> - refull and compute scales if osr is changed.
> - take into account the osr for the sampling frequency.
> - drop num_channels division by 2 which remained from v6.
> - drop ad4851_scan_type_16 since it is not used.
> - change sign based on diff in iio channel definition.
> - shrink same register writes into a single operation.
I'm a bit confused on what the intention is now. In v7, diff-channels
was added to the DT bindings but in v8 it was removed again.
Did you change your mind internally again? Or is the intention still
to specify single-ended/differential in the devicetree?
It really helps reviewers if you include a cover letter and explain
the reasoning behind big changes like this. Otherwise we are left
guessing.
next prev parent reply other threads:[~2024-12-13 23:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-13 16:44 [PATCH v8 1/8] iio: backend: add API for interface get Antoniu Miclaus
2024-12-13 16:44 ` [PATCH v8 2/8] iio: backend: add support for data size set Antoniu Miclaus
2024-12-13 23:09 ` David Lechner
2024-12-13 16:44 ` [PATCH v8 3/8] iio: backend: add API for oversampling Antoniu Miclaus
2024-12-13 23:10 ` David Lechner
2024-12-14 12:50 ` Jonathan Cameron
2024-12-13 16:44 ` [PATCH v8 4/8] iio: adc: adi-axi-adc: add interface type Antoniu Miclaus
2024-12-13 16:44 ` [PATCH v8 5/8] iio: adc: adi-axi-adc: set data format Antoniu Miclaus
2024-12-14 12:48 ` Jonathan Cameron
2024-12-13 16:44 ` [PATCH v8 6/8] iio: adc: adi-axi-adc: add oversampling Antoniu Miclaus
2024-12-13 16:44 ` [PATCH v8 7/8] dt-bindings: iio: adc: add ad4851 Antoniu Miclaus
2024-12-13 23:07 ` David Lechner
2024-12-13 16:44 ` [PATCH v8 8/8] iio: adc: ad4851: add ad485x driver Antoniu Miclaus
2024-12-13 23:43 ` David Lechner [this message]
2024-12-14 13:43 ` Jonathan Cameron
2024-12-13 23:07 ` [PATCH v8 1/8] iio: backend: add API for interface get David Lechner
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=2f7c5893-695c-4633-9142-10e70c1b3220@baylibre.com \
--to=dlechner@baylibre.com \
--cc=antoniu.miclaus@analog.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=robh@kernel.org \
/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