From: Francesco Dolcini <francesco@dolcini.it>
To: Jonathan Cameron <jic23@kernel.org>
Cc: "João Paulo Gonçalves" <jpaulo.silvagoncalves@gmail.com>,
"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 14:12:52 +0200 [thread overview]
Message-ID: <20240803121252.GA6207@francesco-nb> (raw)
In-Reply-To: <20240803122127.221da36f@jic23-huawei>
Hello Jonathan,
On Sat, Aug 03, 2024 at 12:21:27PM +0100, Jonathan Cameron wrote:
> 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!)
The driver was just introduced by me in v6.11, I assume that the only
user is a board that is not yet available in the upstream Linux kernel
(we gonna send the DT soon), with that said I am relatively confident we
are not going to break any user.
The reason for sending this patch is that we just stumbled across
a different driver that was hard-coding the IRQ flags and it was not working
for our hardware, at that moment I realized that the decision on the just
added ti-ads1119 was not the best one.
The idea of this patch is to clean this up _before_ any user is
affected.
Francesco
next prev parent reply other threads:[~2024-08-03 12:13 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
2024-08-03 12:12 ` Francesco Dolcini [this message]
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=20240803121252.GA6207@francesco-nb \
--to=francesco@dolcini.it \
--cc=francesco.dolcini@toradex.com \
--cc=jic23@kernel.org \
--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