From: Jonathan Cameron <jic23@kernel.org>
To: "João Paulo Gonçalves" <jpaulo.silvagoncalves@gmail.com>
Cc: Francesco Dolcini <francesco@dolcini.it>,
Lars-Peter Clausen <lars@metafoo.de>,
Francesco Dolcini <francesco.dolcini@toradex.com>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] iio: adc: ads1119: Fix IRQ flags
Date: Sat, 3 Aug 2024 12:21:27 +0100 [thread overview]
Message-ID: <20240803122127.221da36f@jic23-huawei> (raw)
In-Reply-To: <20240731142016.6immldd7i4y7v2iw@joaog-nb>
On Wed, 31 Jul 2024 11:20:16 -0300
João Paulo Gonçalves <jpaulo.silvagoncalves@gmail.com> wrote:
> On Wed, Jul 31, 2024 at 04:06:57PM +0200, Francesco Dolcini wrote:
> > From: Francesco Dolcini <francesco.dolcini@toradex.com>
> >
> > Remove IRQF_TRIGGER_FALLING flag from irq request, this should come from
> > the platform firmware and should not be hard-coded into the driver.
> >
> > Add IRQF_ONESHOT flag to the irq request, the interrupt should not be
> > re-activated in interrupt context, it should be done only after the
> > device irq handler run.
> >
>
> Reviwed-by: João Paulo Gonçalves <jpaulo.silvagoncalves@gmail.com>
For the direction, there is a risk that we will break someone who
has a firmware that isn't setting this correctly.
I don't mind doing that if we have another board that needs control
(and is setting it appropriately) though. Is that true here, or is
this just cleanup?
If it's cleanup we tend to leave these alone (but not introduce them
into new code!)
Jonathan
next prev parent reply other threads:[~2024-08-03 11:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-31 14:06 [PATCH v1] iio: adc: ads1119: Fix IRQ flags Francesco Dolcini
2024-07-31 14:20 ` João Paulo Gonçalves
2024-08-03 11:21 ` Jonathan Cameron [this message]
2024-08-03 12:12 ` Francesco Dolcini
2024-08-03 15:48 ` 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=20240803122127.221da36f@jic23-huawei \
--to=jic23@kernel.org \
--cc=francesco.dolcini@toradex.com \
--cc=francesco@dolcini.it \
--cc=jpaulo.silvagoncalves@gmail.com \
--cc=lars@metafoo.de \
--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