From: Jonathan Cameron <jic23@kernel.org>
To: Marcelo Schmitt <marcelo.schmitt@analog.com>
Cc: <linux-spi@vger.kernel.org>, <linux-iio@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
Axel Haslam <ahaslam@baylibre.com>, <broonie@kernel.org>,
<nuno.sa@analog.com>, <dlechner@baylibre.com>, <andy@kernel.org>,
<marcelo.schmitt1@gmail.com>
Subject: Re: [PATCH v3 1/1] spi: offload: Add offset parameter
Date: Sun, 28 Sep 2025 11:00:52 +0100 [thread overview]
Message-ID: <20250928110052.6fefd6a1@jic23-huawei> (raw)
In-Reply-To: <d73804d605d494c6420adb7c0b67f6707628832d.1758913065.git.marcelo.schmitt@analog.com>
On Fri, 26 Sep 2025 16:01:05 -0300
Marcelo Schmitt <marcelo.schmitt@analog.com> wrote:
> From: Axel Haslam <ahaslam@baylibre.com>
>
> Add an offset parameter that can be passed in the periodic trigger.
> This is useful for example when ADC drivers implement a separate periodic
> signal to trigger conversion and need offload to read the result with
> some delay. While at it, add some documentation to offload periodic trigger
> parameters.
>
> Signed-off-by: Axel Haslam <ahaslam@baylibre.com>
> Signed-off-by: Marcelo Schmitt <marcelo.schmitt@analog.com>
Hi Axel, Marcelo,
Is there a build time dependency on this for the ad4030 series?
I'm assuming this will go via Mark's SPI tree, so this is really a question
of do we need to ask him for an immutable branch or not.
I don't think there is such a dependency but just wanted to check!
Jonathan
next prev parent reply other threads:[~2025-09-28 10:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-26 19:00 [PATCH v3 0/1] Add SPI offload trigger offset Marcelo Schmitt
2025-09-26 19:01 ` [PATCH v3 1/1] spi: offload: Add offset parameter Marcelo Schmitt
2025-09-26 20:10 ` David Lechner
2025-09-28 10:00 ` Jonathan Cameron [this message]
2025-09-28 13:49 ` Marcelo Schmitt
2025-09-29 9:34 ` [PATCH v3 0/1] Add SPI offload trigger offset Mark Brown
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=20250928110052.6fefd6a1@jic23-huawei \
--to=jic23@kernel.org \
--cc=ahaslam@baylibre.com \
--cc=andy@kernel.org \
--cc=broonie@kernel.org \
--cc=dlechner@baylibre.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=marcelo.schmitt1@gmail.com \
--cc=marcelo.schmitt@analog.com \
--cc=nuno.sa@analog.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
all inboxes | Powered by JetHome®