From: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
To: Jacopo Mondi <jacopo@jmondi.org>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jacopo Mondi <jacopo+renesas@jmondi.org>,
Jonathan Cameron <jic23@kernel.org>,
"Lars-Peter Clausen" <lars@metafoo.de>,
Andrea Merello <andrea.merello@gmail.com>,
"Magnus Damm" <magnus.damm@gmail.com>,
<linux-iio@vger.kernel.org>, <linux-staging@lists.linux.dev>,
Vincent Whitchurch <vincent.whitchurch@axis.com>
Subject: Re: [PATCH 2/2] staging: iio: imu: Add CEVA BNO08x driver
Date: Fri, 17 Jun 2022 18:20:37 +0100 [thread overview]
Message-ID: <20220617182037.00007469@Huawei.com> (raw)
In-Reply-To: <20220616123014.ogdutud3lsnqmexa@uno.localdomain>
On Thu, 16 Jun 2022 14:30:14 +0200
Jacopo Mondi <jacopo@jmondi.org> wrote:
> Hi Greg
>
> On Thu, Jun 16, 2022 at 12:57:30PM +0200, Greg Kroah-Hartman wrote:
> > On Thu, Jun 16, 2022 at 12:36:34PM +0200, Jacopo Mondi wrote:
> > > Hi Greg
> > >
> > > On Thu, Jun 16, 2022 at 12:26:18PM +0200, Greg Kroah-Hartman wrote:
> > > > On Thu, Jun 16, 2022 at 12:00:06PM +0200, Jacopo Mondi wrote:
> > > > > From: Jacopo Mondi <jacopo@jmondi.org>
> > > > >
> > > > > Add support for CEVA BNO08x Sensor Hub.
> > > > >
> > > > > The BNO08X family (BNO080/85/86) is a System in Package (SiP) that
> > > > > integrates a triaxial accelerometer, triaxial gyroscope, magnetometer
> > > > > and a 32-bit ARM Cortex-M0+ microcontroller running CEVA's SH-2
> > > > > firmware.
> > > > >
> > > > > Datasheet:
> > > > > https://www.ceva-dsp.com/wp-content/uploads/2019/10/BNO080_085-Datasheet.pdf
> > > > >
> > > > > Signed-off-by: Jacopo Mondi <jacopo@jmondi.org>
> > > > > ---
> > > > > 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 ++++++++++++++++++++++++
> > > >
> > > > Why are you adding a new driver to staging/iio/ and not to the real part
> > > > of the kernel? What needs to be done to it to get it out of here?
> > >
> > > Mostly because I don't have access to the hw development platform
> > > anymore, and the one I had was not reliable enough for any further
> > > development anyway.
> > >
> > > I went for staging as I cannot guarantee I can test any requested
> > > change on the series.
> > >
> > > I'm afraid this is a "take it or leave it" series, and as the driver
> > > does anyway work (even if for a single feature) I thought it was worth
> > > sending it upstream anyway.
> >
> > Sure, but staging is not a dumping ground, if you want to submit it and
> > run away, I can't take it here, sorry.
> >
> > Perhaps just let this live as a patch on the mailing list and if anyone
> > else wants to pick it up and maintain it, they can do so.
>
> That would be fine with me. Dan already had a comment, let's see if
> Jonathan or others from the IIO subsystem have more and see what to
> do.
>
We can do a superficial review, but I'm thinking the same as Greg - maybe
just living on the mailing list until someone has hardware and can test is
the best plan long term. Note, one option would be to emulate it. We've done
that for a few bits of hard to setup or hard to acquire hardware where we
want to be able to refactor the code. Also because it's nice to have CI :)
Vincent's (+CC) Roadtest is great for that though this device may be a bit complex
to easily emulate.
https://lore.kernel.org/all/20220311162445.346685-1-vincent.whitchurch@axis.com/
Jonathan
> Thanks
> j
> >
> > thanks,
> >
> > greg k-h
next prev parent reply other threads:[~2022-06-17 17:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-16 10:00 [PATCH 0/2] staging: iio: imu: Add CEVA BNO08x through the staging tree Jacopo Mondi
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 [this message]
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=20220617182037.00007469@Huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=andrea.merello@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jacopo+renesas@jmondi.org \
--cc=jacopo@jmondi.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 \
--cc=vincent.whitchurch@axis.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 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.