From: Gabriel Rondon <grondon@gmail.com>
To: Yash Suthar <yashsuthar983@gmail.com>
Cc: Jonathan Cameron <jic23@kernel.org>,
Andy Shevchenko <andy@kernel.org>,
David Lechner <dlechner@baylibre.com>,
Linus Walleij <linusw@kernel.org>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/3] iio: accel: bmc150: DMA-safe buffers and use iio_push_to_buffers_with_ts()
Date: Mon, 17 Aug 2026 00:46:46 +0100 [thread overview]
Message-ID: <20260816234646.15767-1-grondon@gmail.com> (raw)
In-Reply-To: <20260815175728.99541-1-yashsuthar983@gmail.com>
On Sat, 15 Aug 2026 23:27:25 +0530, Yash Suthar wrote:
> The trigger path used a plain s16 buffer while the FIFO path already had
> a properly typed scan member (__le16 + aligned timestamp). Those two
> buffers did the same job, and s16 does not represent little-endian data.
Built the series on top of current iio/togreg with gcc 13.3, x86_64
allmodconfig and W=1: the three bmc150 objects (core, i2c, spi) compile
cleanly with no new warnings.
I also used it as the base for v4 of my bmc150 series (event-enable
race fix + guard(mutex) conversion), which is rebased on top of these
patches:
https://lore.kernel.org/linux-iio/20260816234231.14168-1-grondon@gmail.com/
Gabriel
prev parent reply other threads:[~2026-08-16 23:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-15 17:57 [PATCH v2 0/3] iio: accel: bmc150: DMA-safe buffers and use iio_push_to_buffers_with_ts() Yash Suthar
2026-08-15 17:57 ` [PATCH v2 1/3] iio: accel: bmc150: use aligned scan buffer for both trigger and fifo Yash Suthar
2026-08-17 12:15 ` Linus Walleij
2026-08-22 21:55 ` Jonathan Cameron
2026-08-22 22:02 ` Jonathan Cameron
2026-08-15 17:57 ` [PATCH v2 2/3] iio: accel: bmc150: use DMA-safe buffers for regmap bulk reads Yash Suthar
2026-08-17 12:15 ` Linus Walleij
2026-08-22 22:06 ` Jonathan Cameron
2026-08-24 19:36 ` Yash Suthar
2026-08-15 17:57 ` [PATCH v2 3/3] iio: accel: bmc150: use iio_push_to_buffers_with_ts() Yash Suthar
2026-08-17 12:15 ` Linus Walleij
2026-08-16 23:46 ` Gabriel Rondon [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=20260816234646.15767-1-grondon@gmail.com \
--to=grondon@gmail.com \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--cc=linusw@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=yashsuthar983@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