From: Jonathan Cameron <jic23@kernel.org>
To: Jinseob Kim <kimjinseob88@gmail.com>
Cc: linux-iio@vger.kernel.org,
"David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH RFC 0/3] iio: add Open Sensor Fusion UART driver
Date: Fri, 22 May 2026 16:22:59 +0100 [thread overview]
Message-ID: <20260522162259.39d99626@jic23-huawei> (raw)
In-Reply-To: <20260520072843.3593-1-kimjinseob88@gmail.com>
On Wed, 20 May 2026 16:28:40 +0900
Jinseob Kim <kimjinseob88@gmail.com> wrote:
> Open Sensor Fusion is a UART-attached sensor aggregation device. The current
> prototype sends OSF protocol v0 frames over a host UART link. This RFC adds the
> first Linux IIO receive path for that UART stream.
>
> The first transport is serdev UART. USB, real sensor reads, fusion output, and
> production timestamp correlation are intentionally left out of this series.
>
> The driver code is kept in one patch for the first RFC to avoid intermediate
> non-buildable states. The internal files are still split by protocol, stream,
> core, transport, and IIO code.
Even for an RFC you need to break it up. If you do it right there won't
be non-buildable states. Take a look at how any complex IIO driver is added.
Key thing here seems to be that we need some references.
Superficially sounds like an open source sensor hub implementation but
we need a datasheet / reference manual to be able to review this properly.
I'll have a first look but it's likely to be somewhat superficial.
prev parent reply other threads:[~2026-05-22 15:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-20 7:28 [PATCH RFC 0/3] iio: add Open Sensor Fusion UART driver Jinseob Kim
2026-05-20 7:28 ` [PATCH RFC 1/3] dt-bindings: iio: imu: add Open Sensor Fusion UART binding Jinseob Kim
2026-05-20 16:33 ` Conor Dooley
2026-05-20 7:28 ` [PATCH RFC 2/3] iio: osf: add Open Sensor Fusion UART IIO driver Jinseob Kim
2026-05-20 8:04 ` sashiko-bot
2026-05-22 16:24 ` Jonathan Cameron
2026-05-20 7:28 ` [PATCH RFC 3/3] MAINTAINERS: add Open Sensor Fusion IIO driver entry Jinseob Kim
2026-05-20 7:59 ` Joshua Crofts
[not found] ` <CALMSewJinjbnHT_sOgWmHVeThv3su_E6fioyAjEWKzf7uROc2Q@mail.gmail.com>
2026-05-20 8:14 ` j k
2026-05-20 8:22 ` Joshua Crofts
2026-05-20 11:14 ` Jonathan Cameron
2026-05-20 11:55 ` [PATCH RFC 0/3] iio: add Open Sensor Fusion UART driver Andy Shevchenko
2026-05-22 15:22 ` 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=20260522162259.39d99626@jic23-huawei \
--to=jic23@kernel.org \
--cc=andy@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=kimjinseob88@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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