From: Alexandru Tachici <alexandru.tachici@analog.com>
To: <linux-iio@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Cc: <jic23@kernel.org>, Alexandru Tachici <alexandru.tachici@analog.com>
Subject: [PATCH 0/2 V3] iio: adc: ad7124 fix wrong irq flag
Date: Mon, 13 Jan 2020 12:26:51 +0200 [thread overview]
Message-ID: <20200113102653.20900-1-alexandru.tachici@analog.com> (raw)
In-Reply-To: <20200111112317.1cf2d878@archlinux>
Before these patches the ad7124 driver used a wrong irq flag
because it is using the ad-sigma-delta layer which hardcoded
the used irq flag. This caused an early read of the
data register when ad7124 was set on continous mode giving
a bad conversion.
This V3 series fixes the above explained unwanted behaviour.
1. Allow drivers to set their own irq flag for the iio
triggered buffer.
2. Set the right irq flag in the ad_sigma_delta_info
in ad7124 driver.
Alexandru Tachici (2):
iio: adc: ad-sigma-delta: Allow custom IRQ flags
iio: adc: ad7124: Set IRQ type to falling
drivers/iio/adc/ad7124.c | 2 ++
drivers/iio/adc/ad7780.c | 1 +
drivers/iio/adc/ad7791.c | 1 +
drivers/iio/adc/ad7793.c | 1 +
drivers/iio/adc/ad_sigma_delta.c | 2 +-
include/linux/iio/adc/ad_sigma_delta.h | 2 ++
6 files changed, 8 insertions(+), 1 deletion(-)
--
2.20.1
next prev parent reply other threads:[~2020-01-13 10:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-06 10:57 [PATCH] iio: ad_sigma_delta: Add custom irq flags Alexandru Tachici
2020-01-07 8:41 ` Tachici, Alexandru
2020-01-07 11:06 ` [PATCH V2] " Alexandru Tachici
2020-01-11 11:23 ` Jonathan Cameron
2020-01-13 10:26 ` Alexandru Tachici [this message]
2020-01-13 10:26 ` [PATCH 1/2 V3] iio: adc: ad-sigma-delta: Allow custom IRQ flags Alexandru Tachici
2020-01-18 11:18 ` Jonathan Cameron
2020-01-13 10:26 ` [PATCH 2/2 V3] iio: adc: ad7124: Set IRQ type to falling Alexandru Tachici
2020-01-18 11:20 ` 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=20200113102653.20900-1-alexandru.tachici@analog.com \
--to=alexandru.tachici@analog.com \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.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;
as well as URLs for NNTP newsgroup(s).