[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <0b478ed2-dd1e-4014-8501-2e1b50b473e3@baylibre.com>
Date: Tue, 22 Oct 2024 17:28:47 -0500
From: David Lechner <dlechner@...libre.com>
To: Jonathan Cameron <jic23@...nel.org>,
Antoniu Miclaus <antoniu.miclaus@...log.com>
Cc: robh@...nel.org, krzk+dt@...nel.org, nuno.sa@...log.com,
conor+dt@...nel.org, ukleinek@...nel.org, dragos.bogdan@...log.com,
linux-iio@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-pwm@...r.kernel.org
Subject: Re: [PATCH v4 6/6] iio: adc: ad4851: add ad485x driver
On 10/19/24 8:49 AM, Jonathan Cameron wrote:
> On Fri, 18 Oct 2024 13:42:10 +0300
> Antoniu Miclaus <antoniu.miclaus@...log.com> 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@...log.com>
>
> A few minor things from me that I could fix whilst applying,
> but David gave a much more detailed review of v3, so I'll wait
> for his feedback on this. I haven't dug into datasheets much and
> may well have missed other things.
>
Many of my review comments were not addressed at all. :-(
Plus one addressed incorrectly (rounding PWM period down instead
of the suggested rounding up).
I still have major concerns about userspace-facing things like the
questionable use of the offset attribute and fixing how oversampling
interacts with the scan_type.
Powered by blists - more mailing lists