From: "Ghimiray, Himal Prasad" <himal.prasad.ghimiray@intel.com>
To: Michal Wajdeczko <michal.wajdeczko@intel.com>,
<intel-xe@lists.freedesktop.org>
Subject: Re: [PATCH] drm/xe: Prefer USEC_PER_SEC over MICRO
Date: Tue, 11 Mar 2025 20:04:45 +0530 [thread overview]
Message-ID: <9eeda900-be06-4cba-9cb1-28285e6846c9@intel.com> (raw)
In-Reply-To: <20250311140115.2042-1-michal.wajdeczko@intel.com>
On 11-03-2025 19:31, Michal Wajdeczko wrote:
> It will be easier to understand the meaning of the flr_timeout
> value if the USEC_PER_SEC macro is used in the expression.
>
> Signed-off-by: Michal Wajdeczko <michal.wajdeczko@intel.com>
> ---
> drivers/gpu/drm/xe/xe_device.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/xe/xe_device.c b/drivers/gpu/drm/xe/xe_device.c
> index 5d79b439dd62..7d32d5c6538f 100644
> --- a/drivers/gpu/drm/xe/xe_device.c
> +++ b/drivers/gpu/drm/xe/xe_device.c
> @@ -522,7 +522,7 @@ static bool xe_driver_flr_disabled(struct xe_device *xe)
> */
> static void __xe_driver_flr(struct xe_device *xe)
> {
> - const unsigned int flr_timeout = 3 * MICRO; /* specs recommend a 3s wait */
> + const unsigned int flr_timeout = 3 * USEC_PER_SEC; /* specs recommend a 3s wait */
Reviewed-by: Himal Prasad Ghimiray <himal.prasad.ghimiray@intel.com>
> struct xe_mmio *mmio = xe_root_tile_mmio(xe);
> int ret;
>
next prev parent reply other threads:[~2025-03-11 14:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-11 14:01 [PATCH] drm/xe: Prefer USEC_PER_SEC over MICRO Michal Wajdeczko
2025-03-11 14:34 ` Ghimiray, Himal Prasad [this message]
2025-03-11 16:12 ` ✓ CI.Patch_applied: success for " Patchwork
2025-03-11 16:13 ` ✓ CI.checkpatch: " Patchwork
2025-03-11 16:14 ` ✓ CI.KUnit: " Patchwork
2025-03-11 16:31 ` ✓ CI.Build: " Patchwork
2025-03-11 16:33 ` ✓ CI.Hooks: " Patchwork
2025-03-11 16:34 ` ✓ CI.checksparse: " Patchwork
2025-03-11 16:56 ` ✓ Xe.CI.BAT: " Patchwork
2025-03-12 9:02 ` ✗ Xe.CI.Full: failure " Patchwork
2025-03-12 10:23 ` Michal Wajdeczko
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=9eeda900-be06-4cba-9cb1-28285e6846c9@intel.com \
--to=himal.prasad.ghimiray@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=michal.wajdeczko@intel.com \
/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