Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
MIME-Version: 1.0
References: <20230414102744.150-1-honda@mechatrax.com> <5c8f68f0157d9ae66e6d88d648fcfd26e68be307.camel@gmail.com>
In-Reply-To: <5c8f68f0157d9ae66e6d88d648fcfd26e68be307.camel@gmail.com>
From:   Masahiro Honda <honda@mechatrax.com>
Date:   Wed, 19 Apr 2023 20:58:37 +0900
Message-ID: <CA+Tz-SHS28N_nABk0F=rhdg8tvzPFC=+RiOrC6X7n+51LBJs6Q@mail.gmail.com>
Subject: Re: [PATCH v2] Fix IRQ issue by setting IRQ_DISABLE_UNLAZY flag
To:     =?UTF-8?B?TnVubyBTw6E=?= <noname.nuno@gmail.com>
Cc:     Lars-Peter Clausen <lars@metafoo.de>,
        Michael Hennerich <Michael.Hennerich@analog.com>,
        Jonathan Cameron <jic23@kernel.org>, linux-iio@vger.kernel.org,
        linux-kernel@vger.kernel.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Precedence: bulk

Hi Nuno,

Thank you for your advice.

On Tue, Apr 18, 2023 at 8:06=E2=80=AFPM Nuno S=C3=A1 <noname.nuno@gmail.com=
> wrote:
>
> I'm not really keen with having the Kconfig option. I'm fairly convinced =
that
> this might be a problem affecting all sigma delta ADCs and even if they a=
ren't
> affected, I do not think that setting this IRQ flag will do any arm (othe=
r than
> less efficiency maybe).
>
>
> If you really want to be on the safe side, we could add a new boolean to =
'struct
> ad_sigma_delta_info' that would be enabled for your device and when true,=
 the
> LAZY bit is set. Once we prove that all devices might be affected by this=
 issue,
> we could remove the boolean and make it a default setting.
>
> - Nuno S=C3=A1

I understand. I'll only set and clear the IRQ flag.