Linux IIO development
 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>, "Chris Hall" <c-hall@ti.com>,
	"Patrick Edwards" <pedwards@ti.com>,
	"Kurt Borja" <kuurtb@gmail.com>,
	"Nguyen Minh Tien" <zizuzacker@gmail.com>,
	linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/2] iio: adc: ti-ads112c14: buffered read support
Date: Sat, 1 Aug 2026 02:47:27 +0100	[thread overview]
Message-ID: <20260801024727.086bd896@jic23-huawei> (raw)
In-Reply-To: <20260727-iio-adc-ti-ads112c14-buffered-read-v3-0-cbbcaf030148@baylibre.com>

On Mon, 27 Jul 2026 09:09:49 -0500
"David Lechner (TI)" <dlechner@baylibre.com> wrote:

> This is the next phase of ti-ads112c14 support after [1].
> 
> Some design decision notes:
> * This just includes support for software triggers using the single-shot
>   mode for now. We will follow up later with DRDY interrupt support and
>   a new trigger to allow using the continuous mode.
> * We wanted to enable CRC checking for data integrity, so it is just
>   always enabled. This way, the buffer layout is always the same. I
>   don't think we have an existing control for toggling CRC checking
>   anyway.
> 
> [1]: https://lore.kernel.org/linux-iio/20260714-iio-adc-ti-ads122c14-v4-0-25f8e3084485@baylibre.com/
> 
> Signed-off-by: David Lechner (TI) <dlechner@baylibre.com>
Applied to the testing branch of iio.git.

Thanks

Jonathan

      parent reply	other threads:[~2026-08-01  1:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-27 14:09 [PATCH v3 0/2] iio: adc: ti-ads112c14: buffered read support David Lechner (TI)
2026-07-27 14:09 ` [PATCH v3 1/2] iio: adc: ti-ads112c14: add support for I2C CRC8 David Lechner (TI)
2026-07-27 14:09 ` [PATCH v3 2/2] iio: adc: ti-ads112c14: add support for buffered read David Lechner (TI)
2026-08-01  1:47 ` 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=20260801024727.086bd896@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=andy@kernel.org \
    --cc=c-hall@ti.com \
    --cc=dlechner@baylibre.com \
    --cc=kuurtb@gmail.com \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nuno.sa@analog.com \
    --cc=pedwards@ti.com \
    --cc=zizuzacker@gmail.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