From: Jonathan Cameron <jic23@kernel.org>
To: Stephan Gerhold <stephan@gerhold.net>
Cc: Lars-Peter Clausen <lars@metafoo.de>,
Rob Herring <robh+dt@kernel.org>,
Linus Walleij <linus.walleij@linaro.org>,
linux-iio@vger.kernel.org, devicetree@vger.kernel.org,
Hans de Goede <hdegoede@redhat.com>,
Andy Shevchenko <andy.shevchenko@gmail.com>,
~postmarketos/upstreaming@lists.sr.ht,
Nikita Travkin <nikita@trvn.ru>
Subject: Re: [PATCH v2 0/4] iio: accel: bmc150: Add support for INT2 and BMC156
Date: Sun, 8 Aug 2021 16:51:55 +0100 [thread overview]
Message-ID: <20210808165155.161ecfcb@jic23-huawei> (raw)
In-Reply-To: <20210802155657.102766-1-stephan@gerhold.net>
On Mon, 2 Aug 2021 17:56:53 +0200
Stephan Gerhold <stephan@gerhold.net> wrote:
> This series makes it possible to set up interrupts with the BMC150 driver
> on boards where only the INT2 pin is connected (and not INT1). This is
> particularly always the case for BMC156 since for some reason it only
> has the INT2 pin and not the INT1 pin.
>
> These changes were already partially discussed here:
> https://lore.kernel.org/linux-iio/YMOphuXSoODIVX06@gerhold.net/
Hopefully one of us or someone else will come back to this and
figure out a clean solution to generic fw support for getting named IRQs.
In the meantime this will be fine for this particular driver.
Some fun to look forwards to ;)
Applied to the togreg branch of iio.git and pushed out as testing for 0-day
to poke at it and see what we missed.
Thanks,
Jonathan
>
> Changes in v2:
> - PATCH 1/4: Clarify order of "interrupts" with "interrupt-names"
> - PATCH 4/4: Wrap a long line, clarify BOSCH_UNKNOWN with a comment
>
> v1: https://lore.kernel.org/linux-iio/20210719112156.27087-1-stephan@gerhold.net/
>
> Stephan Gerhold (4):
> dt-bindings: iio: accel: bma255: Add interrupt-names
> dt-bindings: iio: accel: bma255: Add bosch,bmc156_accel
> iio: accel: bmc150: Make it possible to configure INT2 instead of INT1
> iio: accel: bmc150: Add support for BMC156
>
> .../bindings/iio/accel/bosch,bma255.yaml | 34 +++++++-
> drivers/iio/accel/Kconfig | 5 +-
> drivers/iio/accel/bmc150-accel-core.c | 78 +++++++++++++++----
> drivers/iio/accel/bmc150-accel-i2c.c | 10 ++-
> drivers/iio/accel/bmc150-accel-spi.c | 10 ++-
> drivers/iio/accel/bmc150-accel.h | 20 ++++-
> 6 files changed, 134 insertions(+), 23 deletions(-)
>
prev parent reply other threads:[~2021-08-08 15:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-02 15:56 [PATCH v2 0/4] iio: accel: bmc150: Add support for INT2 and BMC156 Stephan Gerhold
2021-08-02 15:56 ` [PATCH v2 1/4] dt-bindings: iio: accel: bma255: Add interrupt-names Stephan Gerhold
2021-08-06 21:49 ` Rob Herring
2021-08-02 15:56 ` [PATCH v2 2/4] dt-bindings: iio: accel: bma255: Add bosch,bmc156_accel Stephan Gerhold
2021-08-02 15:56 ` [PATCH v2 3/4] iio: accel: bmc150: Make it possible to configure INT2 instead of INT1 Stephan Gerhold
2021-08-03 23:34 ` Linus Walleij
2021-08-02 15:56 ` [PATCH v2 4/4] iio: accel: bmc150: Add support for BMC156 Stephan Gerhold
2021-08-08 15:51 ` 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=20210808165155.161ecfcb@jic23-huawei \
--to=jic23@kernel.org \
--cc=andy.shevchenko@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=hdegoede@redhat.com \
--cc=lars@metafoo.de \
--cc=linus.walleij@linaro.org \
--cc=linux-iio@vger.kernel.org \
--cc=nikita@trvn.ru \
--cc=robh+dt@kernel.org \
--cc=stephan@gerhold.net \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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