From: Jani Nikula <jani.nikula@linux.intel.com>
To: Guchun Chen <guchun.chen@amd.com>,
amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
alexander.deucher@amd.com, hawking.zhang@amd.com,
dmitry.baryshkov@linaro.org, spasswolf@web.de
Cc: Guchun Chen <guchun.chen@amd.com>
Subject: Re: [PATCH 2/2] drm/probe_helper: warning on poll_enabled for issue catching
Date: Wed, 08 Mar 2023 15:06:57 +0200 [thread overview]
Message-ID: <87o7p3bde6.fsf@intel.com> (raw)
In-Reply-To: <20230308121718.2586933-1-guchun.chen@amd.com>
On Wed, 08 Mar 2023, Guchun Chen <guchun.chen@amd.com> wrote:
> In order to catch issues in other drivers to ensure proper call
> sequence of polling function.
>
> Bug: https://gitlab.freedesktop.org/drm/amd/-/issues/2411
> Fixes: a4e771729a51("drm/probe_helper: sort out poll_running vs poll_enabled")
How does an additional warning "fix" anything?
> Reported-by: Bert Karwatzki <spasswolf@web.de>
> Suggested-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
> Signed-off-by: Guchun Chen <guchun.chen@amd.com>
> ---
> drivers/gpu/drm/drm_probe_helper.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/gpu/drm/drm_probe_helper.c b/drivers/gpu/drm/drm_probe_helper.c
> index 8127be134c39..85e0e80d4a52 100644
> --- a/drivers/gpu/drm/drm_probe_helper.c
> +++ b/drivers/gpu/drm/drm_probe_helper.c
> @@ -852,6 +852,8 @@ EXPORT_SYMBOL(drm_kms_helper_is_poll_worker);
> */
> void drm_kms_helper_poll_disable(struct drm_device *dev)
> {
> + WARN_ON(!dev->mode_config.poll_enabled);
drm_WARN_ON() please.
> +
> if (dev->mode_config.poll_running)
> drm_kms_helper_disable_hpd(dev);
--
Jani Nikula, Intel Open Source Graphics Center
next prev parent reply other threads:[~2023-03-08 13:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-08 12:17 [PATCH 2/2] drm/probe_helper: warning on poll_enabled for issue catching Guchun Chen
2023-03-08 13:06 ` Jani Nikula [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-03-09 5:48 Guchun Chen
2023-03-09 8:49 ` Dmitry Baryshkov
2023-03-09 13:08 ` Chen, Guchun
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=87o7p3bde6.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=guchun.chen@amd.com \
--cc=hawking.zhang@amd.com \
--cc=spasswolf@web.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