Linux IIO development
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: Lothar Rubusch <l.rubusch@gmail.com>,
	lars@metafoo.de, Michael.Hennerich@analog.com, robh@kernel.org,
	krzk+dt@kernel.org, conor+dt@kernel.org,
	devicetree@vger.kernel.org, linux-iio@vger.kernel.org,
	linux-kernel@vger.kernel.org, eraretuya@gmail.com
Subject: Re: [PATCH v8 3/7] dt-bindings: iio: accel: adxl345: add interrupt-names
Date: Sat, 28 Dec 2024 14:30:38 +0000	[thread overview]
Message-ID: <20241228143038.29c7a9a5@jic23-huawei> (raw)
In-Reply-To: <36gtabgmu7f2mafxzq4siwbf2hocyoudgi7mhkr3v33ajqcn57@xq7l63lrgdxf>

On Fri, 27 Dec 2024 08:58:00 +0100
Krzysztof Kozlowski <krzk@kernel.org> wrote:

> On Wed, Dec 25, 2024 at 06:13:34PM +0000, Lothar Rubusch wrote:
> > Add interrupt-names INT1 and INT2 for the two interrupt lines of the
> > sensor.
> > 
> > When one of the two interrupt lines is connected, the interrupt as its
> > interrupt-name, need to be declared in the devicetree. The driver then
> > configures the sensor to indicate its events on either INT1 or INT2.
> > 
> > If no interrupt is configured, then no interrupt-name should be
> > configured, and vice versa. In this case the sensor runs in FIFO BYPASS
> > mode. This allows sensor measurements, but none of the sensor events.
> > 
> > Signed-off-by: Lothar Rubusch <l.rubusch@gmail.com>  
> 
> Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> 
> Best regards,
> Krzysztof
> 
Applied. thanks

Jonathan

  reply	other threads:[~2024-12-28 14:30 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-25 18:13 [PATCH v8 0/7] iio: accel: adxl345: add FIFO operating with IRQ triggered watermark events Lothar Rubusch
2024-12-25 18:13 ` [PATCH v8 1/7] iio: accel: adxl345: add function to switch measuring mode Lothar Rubusch
2024-12-28 14:29   ` Jonathan Cameron
2024-12-25 18:13 ` [PATCH v8 2/7] dt-bindings: iio: accel: adxl345: make interrupts not a required property Lothar Rubusch
2024-12-28 14:30   ` Jonathan Cameron
2024-12-25 18:13 ` [PATCH v8 3/7] dt-bindings: iio: accel: adxl345: add interrupt-names Lothar Rubusch
2024-12-27  7:58   ` Krzysztof Kozlowski
2024-12-28 14:30     ` Jonathan Cameron [this message]
2024-12-25 18:13 ` [PATCH v8 4/7] iio: accel: adxl345: introduce interrupt handling Lothar Rubusch
2024-12-25 18:13 ` [PATCH v8 5/7] iio: accel: adxl345: initialize FIFO delay value for SPI Lothar Rubusch
2024-12-25 18:13 ` [PATCH v8 6/7] iio: accel: adxl345: add FIFO with watermark events Lothar Rubusch
2024-12-28 14:45   ` Jonathan Cameron
2024-12-28 16:11     ` Lothar Rubusch
2025-01-04 12:49       ` Jonathan Cameron
2024-12-25 18:13 ` [PATCH v8 7/7] iio: accel: adxl345: complete the list of defines Lothar Rubusch
2024-12-28 14:47   ` Jonathan Cameron
2024-12-28 15:48     ` Lothar Rubusch
2025-01-04 12:51       ` 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=20241228143038.29c7a9a5@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=Michael.Hennerich@analog.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=eraretuya@gmail.com \
    --cc=krzk+dt@kernel.org \
    --cc=krzk@kernel.org \
    --cc=l.rubusch@gmail.com \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh@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