From: Lorenzo Bianconi <lorenzo@kernel.org>
To: Sean Nyekjaer <sean@geanix.com>
Cc: linux-iio@vger.kernel.org, jic23@kernel.org,
lorenzo.bianconi83@gmail.com, denis.ciocca@st.com,
mario.tesi@st.com, armando.visconti@st.com, martin@geanix.com
Subject: Re: [PATCH v6 5/6] iio: imu: st_lsm6dsx: add motion report function and call from interrupt
Date: Wed, 11 Sep 2019 14:59:51 +0200 [thread overview]
Message-ID: <20190911125951.GA4291@localhost.localdomain> (raw)
In-Reply-To: <632ea600-509e-ad83-4752-6e6fc3000345@geanix.com>
[-- Attachment #1: Type: text/plain, Size: 1330 bytes --]
On Sep 11, Sean Nyekjaer wrote:
>
> On 10/09/2019 14.27, Lorenzo Bianconi wrote:
> > > Could you please try to carry out the following test?
> > > 1- set the FIFO watermark to a high level (e.g. 128)
> > > $echo 256 > /sys/bus/iio/devices/iio:device{x}/buffer/length
> > > $echo 128 > /sys/bus/iio/devices/iio:device{x}/buffer/watermark
> > > 2- set a low acc odr (e.g 13Hz)
> > > $echo 13 > /sys/bus/iio/devices/iio:device{x}/sampling_frequency
> > > 3- start reading from the accel and generate a wake-upp event
> > >
> > > Is still happen? Are you able to decode bus transaction? (register addresses,
> > > data read, ..)
> > >
>
> Do you still want this tested?
no, not necessary
>
> [...]
>
> > Could you please try to enable the LIR (Latched interrupt - BIT(0) in 0x58)?
> > Please remember that on ISM330DLC the interrupt will be automatically cleared
> > reading the wake up src register after a time slice equals to 1/ODR so the it
> > will be set for longer time if you run the device at low ODR
>
>
> "iio: imu: st_lsm6dsx: enable LIR for sensor events"
> "iio: imu: st_lsm6dsx: enable clear on read for latched interrupts"
> Does allow us to get events and buffered reads simultaneously.
>
cool :)
Regards,
Lorenzo
> I will drop PATCH 6/6.
>
> /Sean
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2019-09-11 12:59 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-09 11:28 [PATCH v6 1/6] iio: imu: st_lsm6dsx: move interrupt thread to core Sean Nyekjaer
2019-09-09 11:28 ` [PATCH v6 2/6] iio: imu: st_lsm6dsx: add motion events Sean Nyekjaer
2019-09-09 11:28 ` [PATCH v6 3/6] iio: imu: st_lsm6dsx: add wakeup-source option Sean Nyekjaer
2019-09-09 11:28 ` [PATCH v6 4/6] iio: imu: st_lsm6dsx: always enter interrupt thread Sean Nyekjaer
2019-09-09 11:28 ` [PATCH v6 5/6] iio: imu: st_lsm6dsx: add motion report function and call from interrupt Sean Nyekjaer
2019-09-09 11:51 ` Sean Nyekjaer
2019-09-15 12:20 ` Jonathan Cameron
2019-09-15 12:24 ` Sean Nyekjaer
2019-09-15 13:06 ` Jonathan Cameron
2019-09-09 12:05 ` Lorenzo Bianconi
2019-09-09 12:41 ` Sean Nyekjaer
2019-09-10 7:12 ` Lorenzo Bianconi
2019-09-10 7:17 ` Sean Nyekjaer
2019-09-10 7:26 ` Lorenzo Bianconi
2019-09-10 12:27 ` Lorenzo Bianconi
2019-09-11 12:41 ` Sean Nyekjaer
2019-09-11 12:59 ` Lorenzo Bianconi [this message]
2019-09-09 11:28 ` [PATCH v6 6/6] iio: imu: st_lsm6dsx: prohibit the use of events and buffered reads simultaneously Sean Nyekjaer
2019-09-09 11:55 ` Lorenzo Bianconi
2019-09-09 11:59 ` Sean Nyekjaer
2019-09-09 12:01 ` Sean Nyekjaer
2019-09-09 12:45 ` [PATCH v6.1 " Sean Nyekjaer
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=20190911125951.GA4291@localhost.localdomain \
--to=lorenzo@kernel.org \
--cc=armando.visconti@st.com \
--cc=denis.ciocca@st.com \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=lorenzo.bianconi83@gmail.com \
--cc=mario.tesi@st.com \
--cc=martin@geanix.com \
--cc=sean@geanix.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.