linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tomas Melin <tomas.melin@vaisala.com>
To: Marcelo Schmitt <marcelo.schmitt1@gmail.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:58:58 +0200	[thread overview]
Message-ID: <49465e36-882c-41c2-a8bb-3c2e87bcdfd7@vaisala.com> (raw)
In-Reply-To: <aTGpgEFew2vP1CTG@debian-BULLSEYE-live-builder-AMD64>

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.

Thanks,
Tomas


> 
>                                                               +-------------+
>   +----------------------+                                    |  DATA HOST  |
>   |       AD4134         |                                    |             |
>   |                      |                                    |             |
>   |Data interface  DOUT0 |----------------------------------->| GPI0        |
>   |for ADC data    DOUT1 |----------------------------------->| GPI1        |
>   |read back       DOUT2 |----------------------------------->| GPI2        |
>   |                DOUT3 |----------------------------------->| GPI3        |
>   |                DCLK  |<--------------+        +---------->| GPI4        |
>   |                ODR   |<------------+ |        | +-------->| GPI5        |
>   |                      |             | |        | | +------>| GPI6        |
>   |                      |             | |        | | | +---->| GPI7        |
>   | SPI interface   CS   |<-------+    | +--------|-|-|-|-----| DCLK        |
>   | for register    SCLK |<-----+ |    |          | | | |     |             |
>   | access          SDI  |<---+ | |    |          | | | |     | TRIGGER     |
>   |                 SDO  |--+ | | |    |          | | | |     +-------------+
>   +----------------------+  | | | |    +----------|-|-|-|---------+
>                             | | | +---------------+ | | |
>                             | | +-------------------+ | |
>                             | +-----------------------+ |
>                             +---------------------------+
> 
> or even with two devices [1].
> [1]: https://lore.kernel.org/linux-iio/aRIIDTUR5Pyz1Rxi@debian-BULLSEYE-live-builder-AMD64/
> 
> That is not a current use case but it could be possible. I think it's likely we
> will need extra software to support those cases and, when we get to that, we
> would be adding more diagrams to this doc. Still, no strong opinion, we can
> alternatively add the doc only when we get to those more complex cases.
> I'll follow reviewers' preferences if you or anybody else express any.
> 
> Best regards,
> Marcelo


  reply	other threads:[~2025-12-05  7:59 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 [this message]
2025-12-05 12:32         ` Marcelo Schmitt
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=49465e36-882c-41c2-a8bb-3c2e87bcdfd7@vaisala.com \
    --to=tomas.melin@vaisala.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.schmitt1@gmail.com \
    --cc=marcelo.schmitt@analog.com \
    --cc=nuno.sa@analog.com \
    --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;
as well as URLs for NNTP newsgroup(s).