Linux IIO development
 help / color / mirror / Atom feed
From: Philippe De Muyter <phdm@macq.eu>
To: Lorenzo Bianconi <lorenzo@kernel.org>
Cc: Lorenzo Bianconi <lorenzo.bianconi@redhat.com>,
	jic23@kernel.org, linux-iio@vger.kernel.org
Subject: Re: [PATCH] iio: imu: st_lsm6dsx: no answer after some iio_generic_buffer test cycles
Date: Tue, 14 Feb 2023 10:42:54 +0100	[thread overview]
Message-ID: <20230214094254.GA12246@frolo.macqel> (raw)
In-Reply-To: <Y+oWpKubqhgvCOVx@lore-desk>

Hi Lorenzo,

On Mon, Feb 13, 2023 at 11:53:24AM +0100, Lorenzo Bianconi wrote:
> 
> are you running level or edge interrupts? If you are using edge ones can you
> please check your kernel has the following fix?
> 
> commit 3f9bce7a22a3f8ac9d885c9d75bc45569f24ac8b
> Author: Lorenzo Bianconi <lorenzo@kernel.org>
> Date:   Sat Nov 14 19:39:05 2020 +0100
> 
>     iio: imu: st_lsm6dsx: fix edge-trigger interrupts
> 
I had missed this one.  Adding it fixes the bug.

Thank you !

Philippe

  reply	other threads:[~2023-02-14  9:43 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-08 14:42 [PATCH] iio: imu: st_lsm6dsx: discard samples during filters settling time Lorenzo Bianconi
2023-02-08 16:23 ` Philippe De Muyter
2023-02-08 16:34   ` Lorenzo Bianconi
2023-02-08 17:15     ` Philippe De Muyter
2023-02-08 17:28       ` Lorenzo Bianconi
2023-02-12 10:21 ` Lorenzo Bianconi
2023-02-13  9:19   ` Philippe De Muyter
2023-02-13 10:16     ` [PATCH] iio: imu: st_lsm6dsx: no answer after some iio_generic_buffer test cycles Philippe De Muyter
2023-02-13 10:53       ` Lorenzo Bianconi
2023-02-14  9:42         ` Philippe De Muyter [this message]
2023-02-18 13:56 ` [PATCH] iio: imu: st_lsm6dsx: discard samples during filters settling time Jonathan Cameron
2023-02-20  9:12   ` Lorenzo Bianconi
2023-02-20 11:28     ` Philippe De Muyter
2023-02-20 11:31       ` Lorenzo Bianconi
2023-02-20 12:41     ` Jonathan Cameron
2023-02-20 13:07       ` Lorenzo Bianconi

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=20230214094254.GA12246@frolo.macqel \
    --to=phdm@macq.eu \
    --cc=jic23@kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=lorenzo.bianconi@redhat.com \
    --cc=lorenzo@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