Devicetree
 help / color / mirror / Atom feed
From: Marcelo Schmitt <marcelo.schmitt1@gmail.com>
To: Tomas Melin <tomas.melin@vaisala.com>
Cc: Marcelo Schmitt <marcelo.schmitt@analog.com>,
	linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	jic23@kernel.org, nuno.sa@analog.com, dlechner@baylibre.com,
	andy@kernel.org, Michael.Hennerich@analog.com, robh@kernel.org,
	krzk+dt@kernel.org, conor+dt@kernel.org, corbet@lwn.net
Subject: Re: [PATCH v3 3/3] Docs: iio: Add AD4134
Date: Fri, 5 Dec 2025 09:32:04 -0300	[thread overview]
Message-ID: <aTLQxIGc5jMgQnnx@debian-BULLSEYE-live-builder-AMD64> (raw)
In-Reply-To: <49465e36-882c-41c2-a8bb-3c2e87bcdfd7@vaisala.com>

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

  reply	other threads:[~2025-12-05 12:30 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-02 20:54 [PATCH v3 0/3] iio: adc: Add AD4134 minimum I/O support Marcelo Schmitt
2025-12-02 20:55 ` [PATCH v3 1/3] dt-bindings: iio: adc: Add AD4134 Marcelo Schmitt
2025-12-05  7:52   ` Tomas Melin
2025-12-05 12:50     ` Marcelo Schmitt
2025-12-07 13:13       ` Jonathan Cameron
2025-12-07 13:22   ` Jonathan Cameron
2025-12-02 20:55 ` [PATCH v3 2/3] iio: adc: Initial support for AD4134 Marcelo Schmitt
2025-12-02 21:26   ` Andy Shevchenko
2025-12-03 11:02     ` Nuno Sá
2025-12-03 12:59       ` Andy Shevchenko
2025-12-03 14:48         ` Nuno Sá
2025-12-03 14:56           ` Andy Shevchenko
2025-12-04 14:58     ` Marcelo Schmitt
2025-12-07 13:41   ` Jonathan Cameron
2025-12-02 20:55 ` [PATCH v3 3/3] Docs: iio: Add AD4134 Marcelo Schmitt
2025-12-03 11:57   ` Tomas Melin
2025-12-04 15:32     ` Marcelo Schmitt
2025-12-05  7:58       ` Tomas Melin
2025-12-05 12:32         ` Marcelo Schmitt [this message]
2025-12-07 13:28           ` Jonathan Cameron

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=aTLQxIGc5jMgQnnx@debian-BULLSEYE-live-builder-AMD64 \
    --to=marcelo.schmitt1@gmail.com \
    --cc=Michael.Hennerich@analog.com \
    --cc=andy@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=corbet@lwn.net \
    --cc=devicetree@vger.kernel.org \
    --cc=dlechner@baylibre.com \
    --cc=jic23@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo.schmitt@analog.com \
    --cc=nuno.sa@analog.com \
    --cc=robh@kernel.org \
    --cc=tomas.melin@vaisala.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