devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Stephan Gerhold <stephan@gerhold.net>
Cc: Rob Herring <robh+dt@kernel.org>,
	Andy Shevchenko <andy.shevchenko@gmail.com>,
	devicetree@vger.kernel.org, Lars-Peter Clausen <lars@metafoo.de>,
	~postmarketos/upstreaming@lists.sr.ht,
	Jonathan Cameron <jic23@kernel.org>,
	Linus Walleij <linus.walleij@linaro.org>,
	Hans de Goede <hdegoede@redhat.com>,
	linux-iio@vger.kernel.org
Subject: Re: [PATCH 1/3] dt-bindings: iio: accel: bma255: Fix interrupt type
Date: Thu, 24 Jun 2021 14:38:14 -0600	[thread overview]
Message-ID: <20210624203814.GA1948531@robh.at.kernel.org> (raw)
In-Reply-To: <20210614163150.7774-2-stephan@gerhold.net>

On Mon, 14 Jun 2021 18:31:48 +0200, Stephan Gerhold wrote:
> Bosch accelerometers similar to BMA255 are initially configured to
> emit an active-high interrupt signal. This is currently not re-configured
> in the bmc150-accel driver so the interrupt should most certainly be
> IRQ_TYPE_EDGE_RISING (or potentially IRQ_TYPE_LEVEL_HIGH).
> (Unless there is some kind of inverter installed on the board...)
> 
> At the moment the bmc150-accel driver forcefully requests the IRQ
> using IRQF_TRIGGER_RISING, which means that the IRQ type is currently
> ignored in all existing device trees.
> 
> Fixes: 6259551 ("iio: accel: bmc150-accel: Add DT bindings")
> Cc: Linus Walleij <linus.walleij@linaro.org>
> Signed-off-by: Stephan Gerhold <stephan@gerhold.net>
> ---
> It's probably better to let the bmc150-accel driver rely on the IRQ
> type provided by the device tree in case of inverters or something.
> 
> However:
>   1. We need to fix up several broken device trees first (I found
>      IRQ_TYPE_LEVEL_LOW in some device trees).
>   2. Similarly, I'm not sure if this might break some ACPI devices
>      in case they have the wrong IRQ type listed?
> 
> As a first step this patch just fixes the documentation.
> ---
>  Documentation/devicetree/bindings/iio/accel/bosch,bma255.yaml | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 

Acked-by: Rob Herring <robh@kernel.org>

  parent reply	other threads:[~2021-06-24 20:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-14 16:31 [PATCH 0/3] dt-bindings: iio: accel: bma255: Fix interrupt type / merge bma180 Stephan Gerhold
2021-06-14 16:31 ` [PATCH 1/3] dt-bindings: iio: accel: bma255: Fix interrupt type Stephan Gerhold
2021-06-16  8:37   ` Linus Walleij
2021-06-24 20:38   ` Rob Herring [this message]
2021-06-14 16:31 ` [PATCH 2/3] dt-bindings: iio: accel: bma255: Sort compatibles Stephan Gerhold
2021-06-16  8:38   ` Linus Walleij
2021-06-24 20:38   ` Rob Herring
2021-06-14 16:31 ` [PATCH 3/3] dt-bindings: iio: accel: bma255: Merge bosch,bma180 schema Stephan Gerhold
2021-06-16  9:04   ` Linus Walleij
2021-06-16 17:36     ` Stephan Gerhold
2021-06-24 20:40   ` Rob Herring
2021-07-18 14:51 ` [PATCH 0/3] dt-bindings: iio: accel: bma255: Fix interrupt type / merge bma180 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=20210624203814.GA1948531@robh.at.kernel.org \
    --to=robh@kernel.org \
    --cc=andy.shevchenko@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=hdegoede@redhat.com \
    --cc=jic23@kernel.org \
    --cc=lars@metafoo.de \
    --cc=linus.walleij@linaro.org \
    --cc=linux-iio@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).