All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Nuno Sá" <noname.nuno@gmail.com>
To: "Jonathan Cameron" <jic23@kernel.org>, "Nuno Sá" <nuno.sa@analog.com>
Cc: linux-iio@vger.kernel.org, Lars-Peter Clausen <lars@metafoo.de>,
	Michael Hennerich <Michael.Hennerich@analog.com>
Subject: Re: [PATCH] iio: adc: ad7791: fix IRQ flags
Date: Mon, 06 Feb 2023 12:13:50 +0100	[thread overview]
Message-ID: <e619b7ba249457a542f04a198133e4ba9255d16c.camel@gmail.com> (raw)
In-Reply-To: <e60e97d614a03c5a6e1e86b330a3d3ae47d3d220.camel@gmail.com>

On Mon, 2023-01-30 at 10:01 +0100, Nuno Sá wrote:
> On Sat, 2023-01-21 at 16:58 +0000, Jonathan Cameron wrote:
> > On Fri, 20 Jan 2023 13:46:45 +0100
> > Nuno Sá <nuno.sa@analog.com> wrote:
> > 
> > > The interrupt is triggered on the falling edge rather than being
> > > a
> > > level
> > > low interrupt.
> > > 
> > > Fixes: da4d3d6bb9f6 ("iio: adc: ad-sigma-delta: Allow custom IRQ
> > > flags")
> > > Signed-off-by: Nuno Sá <nuno.sa@analog.com>
> > 
> > What are the symptoms of this?  Given the ad_sigma_delta.c irq
> > handler
> > disables the interrupt until after the data read is done (at which
> > point the
> > level is presumably high again), I don't immediately see why the
> > change
> > here has any impact - either we trigger on the fall, or on the fact
> > it
> > has become low..
> > 
> > 
> 
> Honestly I did not checked this in any HW. This was just by
> inspecting
> the datasheet and confirming that the LOW IRQ is not coherent with
> what
> we have in other sigma delta ADCs.
> 
> However, after some git blaming, I found this [1] which shows that
> this
> might be an issue...
> 
> Hmm, maybe makes sense to add a link to the bellow patch in the
> commit
> description...
>  
> [1]:
> https://lore.kernel.org/linux-iio/20200113102653.20900-3-alexandru.tachici@analog.com
> /
> 
> - Nuno Sá

Hi Jonathan,

Anything that I should do in this one? As I did not tested it, it might
not be a real issue but I still think the patch is good even though it
might not deserve a Fixes tag...

- Nuno Sá

  reply	other threads:[~2023-02-06 11:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-20 12:46 [PATCH] iio: adc: ad7791: fix IRQ flags Nuno Sá
2023-01-21 16:58 ` Jonathan Cameron
2023-01-30  9:01   ` Nuno Sá
2023-02-06 11:13     ` Nuno Sá [this message]
2023-02-18 17:07       ` 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=e619b7ba249457a542f04a198133e4ba9255d16c.camel@gmail.com \
    --to=noname.nuno@gmail.com \
    --cc=Michael.Hennerich@analog.com \
    --cc=jic23@kernel.org \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=nuno.sa@analog.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.