All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Kim Jinseob <kimjinseob88@gmail.com>
Cc: "Rob Herring" <robh@kernel.org>,
	"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
	"Conor Dooley" <conor+dt@kernel.org>,
	"David Lechner" <dlechner@baylibre.com>,
	"Nuno Sá" <nuno.sa@analog.com>,
	"Andy Shevchenko" <andy@kernel.org>,
	"Jonathan Corbet" <corbet@lwn.net>,
	"Shuah Khan" <skhan@linuxfoundation.org>,
	linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH RFC v6 2/5] Documentation: iio: add Open Sensor Fusion driver overview
Date: Wed, 1 Jul 2026 01:13:15 +0100	[thread overview]
Message-ID: <20260701011315.2a7c56af@jic23-huawei> (raw)
In-Reply-To: <CALMSew+=8P851Wdc=zDLsU5T9YC_ZeTHRotCzYiFP=LNznZhDQ@mail.gmail.com>

On Tue, 30 Jun 2026 14:04:43 +0900
Kim Jinseob <kimjinseob88@gmail.com> wrote:

> I will remove "initial" there in the next revision.
> 
Hi Jinseob

A small process thing that a lot of people get 'wrong' is to reply when only
saying you are making the suggested change. That adds a lot of noise to the
mailing list. The correct place for this information is in the change log
for the next version.

Thanks,

Jonathan

> Thanks
> 
> Jinseob
> 
> 2026년 6월 30일 (화) 오전 8:03, Jonathan Cameron <jic23@kernel.org>님이 작성:
> >
> > On Mon, 29 Jun 2026 04:13:34 +0900
> > Jinseob Kim <kimjinseob88@gmail.com> wrote:
> >  
> > > Document the Linux IIO mapping for Open Sensor Fusion devices.
> > >
> > > The overview explains that sensor channels are discovered at runtime
> > > from mandatory capability reports. It also documents that OSF0 is a
> > > wire-format detail and that protocol_major and protocol_minor carry
> > > protocol compatibility information.
> > >
> > > Signed-off-by: Jinseob Kim <kimjinseob88@gmail.com>  
> >
> > One small thing inline.  Otherwise looks good to me!
> >
> > Jonathan
> >  
> > > diff --git a/Documentation/iio/open-sensor-fusion.rst b/Documentation/iio/open-sensor-fusion.rst
> > > new file mode 100644
> > > index 000000000..832901f5e
> > > --- /dev/null
> > > +++ b/Documentation/iio/open-sensor-fusion.rst  
> >  
> > > +Timestamps
> > > +----------
> > > +
> > > +OSF frames include a device-side ``timestamp_us`` field. Buffered IIO samples use
> > > +an IIO timestamp captured on the host when samples are pushed to IIO buffers.
> > > +The initial driver does not correlate the device timestamp with the host IIO
> > > +clock.  
> >
> > Really small thing but I would avoid talking about 'initial' driver.
> > It can cause confusion about when something is true and when it is not
> > as we may have multiple non 'initial' drivers before you get to changing
> > this handling. So just remove that word.
> >  


  reply	other threads:[~2026-07-01  0:13 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-28 19:13 [PATCH RFC v6 0/5] iio: add Open Sensor Fusion IIO driver Jinseob Kim
2026-06-28 19:13 ` [PATCH RFC v6 1/5] dt-bindings: iio: add Open Sensor Fusion device Jinseob Kim
2026-06-28 19:19   ` sashiko-bot
2026-06-29 15:39   ` Conor Dooley
2026-06-30  5:02     ` Kim Jinseob
2026-06-28 19:13 ` [PATCH RFC v6 2/5] Documentation: iio: add Open Sensor Fusion driver overview Jinseob Kim
2026-06-29 23:02   ` Jonathan Cameron
2026-06-30  5:04     ` Kim Jinseob
2026-07-01  0:13       ` Jonathan Cameron [this message]
2026-06-28 19:13 ` [PATCH RFC v6 3/5] iio: osf: add protocol decoding Jinseob Kim
2026-06-29 14:05   ` Andy Shevchenko
2026-06-30  5:07     ` Kim Jinseob
2026-06-28 19:13 ` [PATCH RFC v6 4/5] iio: osf: add authenticated stream parser Jinseob Kim
2026-06-28 19:26   ` sashiko-bot
2026-06-29 14:10   ` Andy Shevchenko
2026-06-29 23:06     ` Jonathan Cameron
2026-06-30  5:12       ` Kim Jinseob
2026-06-30 11:56         ` Andy Shevchenko
2026-06-28 19:13 ` [PATCH RFC v6 5/5] iio: osf: add UART IIO driver Jinseob Kim
2026-06-28 19:26   ` sashiko-bot
2026-07-02 11:55   ` Julian Braha
2026-06-29 14:09 ` [PATCH RFC v6 0/5] iio: add Open Sensor Fusion " Andy Shevchenko
2026-06-29 14:12   ` Andy Shevchenko
2026-06-29 15:25 ` David Lechner
2026-06-29 16:47   ` Kim Jinseob
2026-06-29 22:58   ` Jonathan Cameron

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=20260701011315.2a7c56af@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=andy@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=corbet@lwn.net \
    --cc=devicetree@vger.kernel.org \
    --cc=dlechner@baylibre.com \
    --cc=kimjinseob88@gmail.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nuno.sa@analog.com \
    --cc=robh@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.