[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <aTLQxIGc5jMgQnnx@debian-BULLSEYE-live-builder-AMD64>
Date: Fri, 5 Dec 2025 09:32:04 -0300
From: Marcelo Schmitt <marcelo.schmitt1@...il.com>
To: Tomas Melin <tomas.melin@...sala.com>
Cc: Marcelo Schmitt <marcelo.schmitt@...log.com>, linux-iio@...r.kernel.org,
devicetree@...r.kernel.org, linux-doc@...r.kernel.org,
linux-kernel@...r.kernel.org, jic23@...nel.org, nuno.sa@...log.com,
dlechner@...libre.com, andy@...nel.org,
Michael.Hennerich@...log.com, robh@...nel.org, krzk+dt@...nel.org,
conor+dt@...nel.org, corbet@....net
Subject: Re: [PATCH v3 3/3] Docs: iio: Add AD4134
On 12/05, Tomas Melin wrote:
> Hi,
>
> On 04/12/2025 17:32, Marcelo Schmitt wrote:
> > On 12/03, Tomas Melin wrote:
> >> Hi,
> >>
> >> On 02/12/2025 22:55, Marcelo Schmitt wrote:
> >>> Add initial documentation for the ad4134 IIO driver.
> >>
> >> I wonder is there some information in here that is not readily available
> >> in the device datasheet? After all, isn't idea with this file to
> >> document peculiarities that are not easily found elsewhere?
> >
> > You are correct, these docs are mostly from data sheet info.
> > The main idea of having the doc is to make clear what peripheral connection
> > schema is currently supported.
> > Because AD4134 is both flexible and somewhat extensible in the way it can be
> > connected to the host, we could have different wiring configurations, for
> > example
>
> Thanks for your explanation. My humble opinion is that it would be
> enough to mention in the commit message for the driver being added, or
> in the device-tree bindings that basic I/O mode is only configuration
> that is currently supported.
Okay, I'll drop the docs from v4.
Thanks,
Marcelo
Powered by blists - more mailing lists