From: "Lazar, Lijo" <lijo.lazar@amd.com>
To: Evan Quan <evan.quan@amd.com>,
gregkh@linuxfoundation.org, rafael@kernel.org, lenb@kernel.org,
johannes@sipsolutions.net, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
alexander.deucher@amd.com, andrew@lunn.ch, rdunlap@infradead.org,
quic_jjohnson@quicinc.com, horms@kernel.org
Cc: linux-doc@vger.kernel.org, netdev@vger.kernel.org,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
amd-gfx@lists.freedesktop.org, linux-acpi@vger.kernel.org,
Mario Limonciello <mario.limonciello@amd.com>
Subject: Re: [V9 7/9] drm/amd/pm: add flood detection for wbrf events
Date: Fri, 18 Aug 2023 15:19:17 +0530 [thread overview]
Message-ID: <42901855-c620-e08d-f0b6-6dcb03eb9ba0@amd.com> (raw)
In-Reply-To: <20230818032619.3341234-8-evan.quan@amd.com>
On 8/18/2023 8:56 AM, Evan Quan wrote:
> To protect PMFW from being overloaded.
>
> Signed-off-by: Evan Quan <evan.quan@amd.com>
> Reviewed-by: Mario Limonciello <mario.limonciello@amd.com>
> ---
> drivers/gpu/drm/amd/pm/swsmu/amdgpu_smu.c | 31 +++++++++++++++----
> drivers/gpu/drm/amd/pm/swsmu/inc/amdgpu_smu.h | 7 +++++
> 2 files changed, 32 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/gpu/drm/amd/pm/swsmu/amdgpu_smu.c b/drivers/gpu/drm/amd/pm/swsmu/amdgpu_smu.c
> index 704442ce1da3..6c8bcdc17a15 100644
> --- a/drivers/gpu/drm/amd/pm/swsmu/amdgpu_smu.c
> +++ b/drivers/gpu/drm/amd/pm/swsmu/amdgpu_smu.c
> @@ -1318,7 +1318,8 @@ static int smu_wbrf_event_handler(struct notifier_block *nb,
>
> switch (action) {
> case WBRF_CHANGED:
> - smu_wbrf_handle_exclusion_ranges(smu);
> + schedule_delayed_work(&smu->wbrf_delayed_work,
> + msecs_to_jiffies(SMU_WBRF_EVENT_HANDLING_PACE));
> break;
> default:
> return NOTIFY_DONE;
> @@ -1327,6 +1328,21 @@ static int smu_wbrf_event_handler(struct notifier_block *nb,
> return NOTIFY_OK;
> }
>
> +/**
> + * smu_wbrf_delayed_work_handler - callback on delayed work timer expired
> + *
> + * @work: struct work_struct pointer
> + *
> + * Flood is over and driver will consume the latest exclusion ranges.
> + */
> +static void smu_wbrf_delayed_work_handler(struct work_struct *work)
> +{
> + struct smu_context *smu =
> + container_of(work, struct smu_context, wbrf_delayed_work.work);
> +
> + smu_wbrf_handle_exclusion_ranges(smu);
> +}
> +
> /**
> * smu_wbrf_support_check - check wbrf support
> *
> @@ -1357,12 +1373,14 @@ static void smu_wbrf_support_check(struct smu_context *smu)
> */
> static int smu_wbrf_init(struct smu_context *smu)
> {
> - struct amdgpu_device *adev = smu->adev;
> int ret;
>
> if (!smu->wbrf_supported)
> return 0;
>
> + INIT_DELAYED_WORK(&smu->wbrf_delayed_work,
> + smu_wbrf_delayed_work_handler);
> +
This is one-time and can be part of sw_init.
Thanks,
Lijo
> smu->wbrf_notifier.notifier_call = smu_wbrf_event_handler;
> ret = wbrf_register_notifier(&smu->wbrf_notifier);
> if (ret)
> @@ -1373,11 +1391,10 @@ static int smu_wbrf_init(struct smu_context *smu)
> * before our driver loaded. To make sure our driver
> * is awared of those exclusion ranges.
> */
> - ret = smu_wbrf_handle_exclusion_ranges(smu);
> - if (ret)
> - dev_err(adev->dev, "Failed to handle wbrf exclusion ranges\n");
> + schedule_delayed_work(&smu->wbrf_delayed_work,
> + msecs_to_jiffies(SMU_WBRF_EVENT_HANDLING_PACE));
>
> - return ret;
> + return 0;
> }
>
> /**
> @@ -1393,6 +1410,8 @@ static void smu_wbrf_fini(struct smu_context *smu)
> return;
>
> wbrf_unregister_notifier(&smu->wbrf_notifier);
> +
> + cancel_delayed_work_sync(&smu->wbrf_delayed_work);
> }
>
> static int smu_smc_hw_setup(struct smu_context *smu)
> diff --git a/drivers/gpu/drm/amd/pm/swsmu/inc/amdgpu_smu.h b/drivers/gpu/drm/amd/pm/swsmu/inc/amdgpu_smu.h
> index 244297979f92..4d5cb1b511e5 100644
> --- a/drivers/gpu/drm/amd/pm/swsmu/inc/amdgpu_smu.h
> +++ b/drivers/gpu/drm/amd/pm/swsmu/inc/amdgpu_smu.h
> @@ -480,6 +480,12 @@ struct stb_context {
>
> #define WORKLOAD_POLICY_MAX 7
>
> +/*
> + * Configure wbrf event handling pace as there can be only one
> + * event processed every SMU_WBRF_EVENT_HANDLING_PACE ms.
> + */
> +#define SMU_WBRF_EVENT_HANDLING_PACE 10
> +
> struct smu_context
> {
> struct amdgpu_device *adev;
> @@ -581,6 +587,7 @@ struct smu_context
> /* data structures for wbrf feature support */
> bool wbrf_supported;
> struct notifier_block wbrf_notifier;
> + struct delayed_work wbrf_delayed_work;
> };
>
> struct i2c_adapter;
next prev parent reply other threads:[~2023-08-18 9:50 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-18 3:26 [V9 0/9] Enable Wifi RFI interference mitigation feature support Evan Quan
2023-08-18 3:26 ` [V9 1/9] drivers core: Add support for Wifi band RF mitigations Evan Quan
2023-08-18 16:41 ` Rafael J. Wysocki
2023-08-18 21:24 ` Greg KH
2023-08-18 22:49 ` Limonciello, Mario
2023-08-19 10:50 ` Greg KH
2023-08-22 3:13 ` Limonciello, Mario
2023-08-22 6:39 ` Greg KH
2023-08-23 7:53 ` Kalle Valo
2023-08-23 8:15 ` Greg KH
2023-08-18 3:26 ` [V9 2/9] drivers core: add ACPI based WBRF mechanism introduced by AMD Evan Quan
2023-08-18 17:41 ` Rafael J. Wysocki
2023-08-18 3:26 ` [V9 3/9] cfg80211: expose nl80211_chan_width_to_mhz for wide sharing Evan Quan
2023-08-18 3:26 ` [V9 4/9] wifi: mac80211: Add support for WBRF features Evan Quan
2023-08-21 9:44 ` Johannes Berg
2023-08-25 8:47 ` Quan, Evan
2023-08-18 3:26 ` [V9 5/9] drm/amd/pm: update driver_if and ppsmc headers for coming wbrf feature Evan Quan
2023-08-18 3:26 ` [V9 6/9] drm/amd/pm: setup the framework to support Wifi RFI mitigation feature Evan Quan
2023-08-18 9:12 ` Lazar, Lijo
2023-08-25 8:48 ` Quan, Evan
2023-08-18 3:26 ` [V9 7/9] drm/amd/pm: add flood detection for wbrf events Evan Quan
2023-08-18 9:49 ` Lazar, Lijo [this message]
2023-08-18 3:26 ` [V9 8/9] drm/amd/pm: enable Wifi RFI mitigation feature support for SMU13.0.0 Evan Quan
2023-08-18 9:54 ` Lazar, Lijo
2023-08-18 3:26 ` [V9 9/9] drm/amd/pm: enable Wifi RFI mitigation feature support for SMU13.0.7 Evan Quan
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=42901855-c620-e08d-f0b6-6dcb03eb9ba0@amd.com \
--to=lijo.lazar@amd.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=evan.quan@amd.com \
--cc=gregkh@linuxfoundation.org \
--cc=horms@kernel.org \
--cc=johannes@sipsolutions.net \
--cc=kuba@kernel.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=quic_jjohnson@quicinc.com \
--cc=rafael@kernel.org \
--cc=rdunlap@infradead.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