public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephan Gerhold <stephan@gerhold.net>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Jonathan Cameron <jic23@kernel.org>,
	Lars-Peter Clausen <lars@metafoo.de>,
	Rob Herring <robh+dt@kernel.org>,
	Linus Walleij <linus.walleij@linaro.org>,
	Peter Meerwald <pmeerw@pmeerw.net>,
	linux-iio <linux-iio@vger.kernel.org>,
	devicetree <devicetree@vger.kernel.org>,
	Bastien Nocera <hadess@hadess.net>,
	Hans de Goede <hdegoede@redhat.com>
Subject: Re: [PATCH 0/6] iio: accel: bmc150: Add support for BMA253/BMA254
Date: Thu, 10 Jun 2021 13:25:35 +0200	[thread overview]
Message-ID: <YMH2r3TXp0+qYiLN@gerhold.net> (raw)
In-Reply-To: <CAHp75Vervzi9zXdWef8vpGZwM5wS3LtuKTY9f5j9QA0Asbea2Q@mail.gmail.com>

On Thu, Jun 10, 2021 at 01:51:22PM +0300, Andy Shevchenko wrote:
> On Thu, Jun 10, 2021 at 1:48 PM Stephan Gerhold <stephan@gerhold.net> wrote:
> > On Thu, Jun 10, 2021 at 01:29:26PM +0300, Andy Shevchenko wrote:
> > > On Thu, Jun 10, 2021 at 12:56 PM Stephan Gerhold <stephan@gerhold.net> wrote:
> > > >
> > > > The Bosch BMA253 accelerometer is very similar to both BMA254 and BMA255.
> > > > The current situation is very confusing: BMA254 is supported by the bma180
> > > > driver, but BMA255 is supported by the bmc150-accel driver.
> > > >
> > > > It turns out the bma180 and bmc150-accel drivers have quite some overlap,
> > > > and BMA253/BMA254 would be a bit better supported in bmc150
> > > > (which has support for the motion trigger/interrupt).
> > > >
> > > > This series adds BMA253 support to bmc150-accel and also moves BMA254
> > > > over to bmc150, removing some unnecessary code from the bma180 driver.
> > > >
> > > > I asked Linus Walleij to test these patches on BMA254 a while ago
> > > > and he suggested that I already add his Reviewed-by.
> > >
> > > I add
> > >
> > >
> > > After addressing comments per patch 1, feel free to add my
> > > Reviewed-by: Andy Shevchenko <andy.shevchenko@gmail.com>
> > > to the series.
> > >
> >
> > Thanks for the review!
> >
> > I think the re-ordering should be a separate commit to make the diff not
> > too confusing. Is it fine for you if I send that as a follow-up patch?
> > I already have two more patches that would conflict with the reordering,
> > so it would be easier to include that in the next series.
> >
> > But I can also re-send the entire series with the extra patch if you
> > prefer that, just let me know. :)
> 
> I think that doing the reordering first (if there are no fixes so far)
> is a good idea.
> 

OK, I will try to do that somehow. I will probably prepend one of my
additional patches to this series since it has a Fixes: tag that would
just cause the stable people headaches later when backporting.

Thanks,
Stephan

      reply	other threads:[~2021-06-10 11:25 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-10  9:52 [PATCH 0/6] iio: accel: bmc150: Add support for BMA253/BMA254 Stephan Gerhold
2021-06-10  9:52 ` [PATCH 1/6] iio: accel: bmc150: Drop misleading/duplicate chip identifiers Stephan Gerhold
2021-06-10 10:24   ` Andy Shevchenko
2021-06-10  9:52 ` [PATCH 2/6] dt-bindings: iio: accel: bma255: Document bosch,bma253 Stephan Gerhold
2021-06-10  9:52 ` [PATCH 3/6] iio: accel: bmc150: Add device IDs for BMA253 Stephan Gerhold
2021-06-10  9:52 ` [PATCH 4/6] dt-bindings: iio: bma255: Allow multiple interrupts Stephan Gerhold
2021-06-10  9:52 ` [PATCH 5/6] dt-bindings: iio: accel: bma180/bma255: Move bma254 to bma255 schema Stephan Gerhold
2021-06-10  9:53 ` [PATCH 6/6] iio: accel: bma180/bmc150: Move BMA254 to bmc150-accel driver Stephan Gerhold
2021-06-10 10:17 ` [PATCH 0/6] iio: accel: bmc150: Add support for BMA253/BMA254 Hans de Goede
2021-06-10 10:29 ` Andy Shevchenko
2021-06-10 10:47   ` Stephan Gerhold
2021-06-10 10:51     ` Andy Shevchenko
2021-06-10 11:25       ` Stephan Gerhold [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=YMH2r3TXp0+qYiLN@gerhold.net \
    --to=stephan@gerhold.net \
    --cc=andy.shevchenko@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=hadess@hadess.net \
    --cc=hdegoede@redhat.com \
    --cc=jic23@kernel.org \
    --cc=lars@metafoo.de \
    --cc=linus.walleij@linaro.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=pmeerw@pmeerw.net \
    --cc=robh+dt@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