mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: "David Lechner (TI)" <dlechner@baylibre.com>
Cc: "Nuno Sá" <nuno.sa@analog.com>,
	"Andy Shevchenko" <andy@kernel.org>,
	"Jonathan Corbet" <corbet@lwn.net>,
	"Shuah Khan" <skhan@linuxfoundation.org>,
	"Randy Dunlap" <rdunlap@infradead.org>,
	linux-iio@vger.kernel.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org, "Chris Hall" <c-hall@ti.com>,
	"Patrick Edwards" <pedwards@ti.com>,
	"Kurt Borja" <kuurtb@gmail.com>
Subject: Re: [PATCH] docs: iio: add documentation for ti-ads112c14 driver
Date: Sun, 18 Oct 2026 03:07:44 +0100	[thread overview]
Message-ID: <20261018030744.13855d8f@jic23-hlaptop> (raw)
In-Reply-To: <20261002-iio-adc-ti-ads112c14-docs-v1-1-d5f3efb27727@baylibre.com>

On Fri, 02 Oct 2026 15:05:13 -0500
"David Lechner (TI)" <dlechner@baylibre.com> wrote:

> Add documentation for the TI ADS112C14 and ADS122C14 ADC driver.
> 
> These chips have several quirks that don't map cleanly to the usual IIO
> ABI, so it is worth documenting them for users. This covers how the
> devicetree channel nodes map to IIO channels, the system monitor
> channels, the order in which the interdependent filter_type,
> oversampling_ratio and sampling_frequency attributes need to be written,
> the settlingtime attribute and when it applies, burnout current, GPIOs,
> debugfs register access and the different behavior of buffered reads
> depending on which trigger is used. Also include some devicetree
> examples of typical sensor configurations.
> 
> Signed-off-by: David Lechner (TI) <dlechner@baylibre.com>
Nice doc.
Applied to the testing branch of iio.git

Thanks,

Jonathan

      reply	other threads:[~2026-10-18  2:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-02 20:05 David Lechner (TI)
2026-10-18  2:07 ` Jonathan Cameron [this message]

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=20261018030744.13855d8f@jic23-hlaptop \
    --to=jic23@kernel.org \
    --cc=andy@kernel.org \
    --cc=c-hall@ti.com \
    --cc=corbet@lwn.net \
    --cc=dlechner@baylibre.com \
    --cc=kuurtb@gmail.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nuno.sa@analog.com \
    --cc=pedwards@ti.com \
    --cc=rdunlap@infradead.org \
    --cc=skhan@linuxfoundation.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
all inboxes | Powered by JetHome®