linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jacopo Mondi <jacopo+renesas@jmondi.org>
To: Jonathan Cameron <jic23@kernel.org>,
	Lars-Peter Clausen <lars@metafoo.de>
Cc: Jacopo Mondi <jacopo+renesas@jmondi.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Andrea Merello <andrea.merello@gmail.com>,
	Magnus Damm <magnus.damm@gmail.com>,
	linux-iio@vger.kernel.org, linux-staging@lists.linux.dev
Subject: [PATCH 0/2] staging: iio: imu: Add CEVA BNO08x through the staging tree
Date: Thu, 16 Jun 2022 12:00:04 +0200	[thread overview]
Message-ID: <20220616100006.22045-1-jacopo+renesas@jmondi.org> (raw)

Hello,
   this series adds support for the CEVA BNO08x Sensor Hub through the staging
tree.

The driver currently only support reading a rotation vector in quaternion, which
is just one of the many features supported by the device.

What's relevant here is the protocol handling part, which is used to exposed a
triggered buffer and direct access IIO interfaces. The BNO08x family implements
a packed-based protocol which requires parsing on the driver side. This driver
implements such parsing routine by copying the full received packets and
synchronize the possible multiple consumers which might want to access the data.

Sent through the staging tree as the HW platform I used to test is not available
anymore and I cannot guarantee maintainership of the driver.

However I hope the driver can serve as a useful reference for future
developments.

Thanks
  j

Jacopo Mondi (2):
  dt-bindings: staging: iio: imu: Document CEVA BNO08x
  staging: iio: imu: Add CEVA BNO08x driver

 .../bindings/staging/iio/imu/ceva,bno08x.yaml |  63 ++
 MAINTAINERS                                   |   7 +
 drivers/staging/iio/Kconfig                   |   1 +
 drivers/staging/iio/Makefile                  |   1 +
 drivers/staging/iio/imu/bno08x/Kconfig        |  11 +
 drivers/staging/iio/imu/bno08x/Makefile       |   3 +
 drivers/staging/iio/imu/bno08x/bno08x.c       | 618 ++++++++++++++++++
 7 files changed, 704 insertions(+)
 create mode 100644 Documentation/devicetree/bindings/staging/iio/imu/ceva,bno08x.yaml
 create mode 100644 drivers/staging/iio/imu/bno08x/Kconfig
 create mode 100644 drivers/staging/iio/imu/bno08x/Makefile
 create mode 100644 drivers/staging/iio/imu/bno08x/bno08x.c

--
2.35.1


             reply	other threads:[~2022-06-16 10:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-16 10:00 Jacopo Mondi [this message]
2022-06-16 10:00 ` [PATCH 1/2] dt-bindings: staging: iio: imu: Document CEVA BNO08x Jacopo Mondi
2022-06-27 22:25   ` Rob Herring
2022-06-16 10:00 ` [PATCH 2/2] staging: iio: imu: Add CEVA BNO08x driver Jacopo Mondi
2022-06-16 10:26   ` Greg Kroah-Hartman
2022-06-16 10:36     ` Jacopo Mondi
2022-06-16 10:57       ` Greg Kroah-Hartman
2022-06-16 12:30         ` Jacopo Mondi
2022-06-17 17:20           ` Jonathan Cameron
2022-06-16 11:12   ` Dan Carpenter
2022-06-17 17:49   ` Jonathan Cameron
2022-06-20  9:14     ` Dan Carpenter

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=20220616100006.22045-1-jacopo+renesas@jmondi.org \
    --to=jacopo+renesas@jmondi.org \
    --cc=andrea.merello@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jic23@kernel.org \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-staging@lists.linux.dev \
    --cc=magnus.damm@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;
as well as URLs for NNTP newsgroup(s).