From: Philipp Zabel <p.zabel@pengutronix.de>
To: Jinjie Ruan <ruanjinjie@huawei.com>,
laurentiu.palcu@oss.nxp.com, l.stach@pengutronix.de,
maarten.lankhorst@linux.intel.com, mripard@kernel.org,
tzimmermann@suse.de, airlied@gmail.com, daniel@ffwll.ch,
shawnguo@kernel.org, s.hauer@pengutronix.de,
kernel@pengutronix.de, festevam@gmail.com, robdclark@gmail.com,
sean@poorly.run, konradybcio@kernel.org,
quic_abhinavk@quicinc.com, dmitry.baryshkov@linaro.org,
marijn.suijten@somainline.org, thierry.reding@gmail.com,
mperttunen@nvidia.com, jonathanh@nvidia.com, agx@sigxcpu.org,
gregkh@linuxfoundation.org, jordan@cosmicpenguin.net,
dri-devel@lists.freedesktop.org, imx@lists.linux.dev,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
freedreno@lists.freedesktop.org, linux-tegra@vger.kernel.org
Subject: Re: [PATCH v2 3/5] drm/imx/ipuv3: Use IRQF_NO_AUTOEN flag in request_irq()
Date: Fri, 20 Sep 2024 16:53:19 +0200 [thread overview]
Message-ID: <13010c194e4674f6bdef84bcf748030a1d46b814.camel@pengutronix.de> (raw)
In-Reply-To: <20240912083020.3720233-4-ruanjinjie@huawei.com>
On Do, 2024-09-12 at 16:30 +0800, Jinjie Ruan wrote:
> disable_irq() after request_irq() still has a time gap in which
> interrupts can come. request_irq() with IRQF_NO_AUTOEN flag will
> disable IRQ auto-enable when request IRQ.
>
> Fixes: 47b1be5c0f4e ("staging: imx/drm: request irq only after adding the crtc")
> Reviewed-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
> Signed-off-by: Jinjie Ruan <ruanjinjie@huawei.com>
Reviewed-by: Philipp Zabel <p.zabel@pengutronix.de>
regards
Philipp
next prev parent reply other threads:[~2024-09-20 14:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-12 8:30 [PATCH v2 0/5] drm: Use IRQF_NO_AUTOEN flag in request_irq() Jinjie Ruan
2024-09-12 8:30 ` [PATCH v2 1/5] drm/imx: " Jinjie Ruan
2024-09-20 12:44 ` Laurentiu Palcu
2024-09-12 8:30 ` [PATCH v2 2/5] drm/imx/dcss: " Jinjie Ruan
2024-09-20 12:45 ` Laurentiu Palcu
2024-09-12 8:30 ` [PATCH v2 3/5] drm/imx/ipuv3: " Jinjie Ruan
2024-09-20 14:53 ` Philipp Zabel [this message]
2024-09-12 8:30 ` [PATCH v2 4/5] drm/tegra: dpaux: " Jinjie Ruan
2024-09-12 8:30 ` [PATCH v2 5/5] drm/msm/adreno: " Jinjie Ruan
2024-09-21 20:55 ` (subset) [PATCH v2 0/5] drm: " Dmitry Baryshkov
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=13010c194e4674f6bdef84bcf748030a1d46b814.camel@pengutronix.de \
--to=p.zabel@pengutronix.de \
--cc=agx@sigxcpu.org \
--cc=airlied@gmail.com \
--cc=daniel@ffwll.ch \
--cc=dmitry.baryshkov@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=festevam@gmail.com \
--cc=freedreno@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=imx@lists.linux.dev \
--cc=jonathanh@nvidia.com \
--cc=jordan@cosmicpenguin.net \
--cc=kernel@pengutronix.de \
--cc=konradybcio@kernel.org \
--cc=l.stach@pengutronix.de \
--cc=laurentiu.palcu@oss.nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=marijn.suijten@somainline.org \
--cc=mperttunen@nvidia.com \
--cc=mripard@kernel.org \
--cc=quic_abhinavk@quicinc.com \
--cc=robdclark@gmail.com \
--cc=ruanjinjie@huawei.com \
--cc=s.hauer@pengutronix.de \
--cc=sean@poorly.run \
--cc=shawnguo@kernel.org \
--cc=thierry.reding@gmail.com \
--cc=tzimmermann@suse.de \
/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).