From: "Nilawar, Badal" <badal.nilawar@intel.com>
To: Karthik Poosa <karthik.poosa@intel.com>,
<intel-xe@lists.freedesktop.org>
Cc: <anshuman.gupta@intel.com>, <vinay.belgaumkar@intel.com>,
<ashutosh.dixit@intel.com>, <rodrigo.vivi@intel.com>
Subject: Re: [PATCH v2] drm/xe/hwmon: Fix WRITE_I1 param from u32 to u16
Date: Tue, 27 Aug 2024 16:42:29 +0530 [thread overview]
Message-ID: <57df9581-2125-4044-9804-4bb4bf5c68d6@intel.com> (raw)
In-Reply-To: <20240826133633.129853-1-karthik.poosa@intel.com>
On 26-08-2024 19:06, Karthik Poosa wrote:
> WRITE_I1 sub command of POWER_SETUP pcode command takes param of u16
> instead u32. Corrected it.
> Without this pcode may return illegal sub command errorsCould you please rephrase the commit message. May be like this "The
WRITE_I1 sub-command of the POWER_SETUP pcode command accepts a u16
parameter instead of u32. This change prevents potential illegal
sub-command errors."
Regards,
Badal
>
> v2: Mask uval instead of changing the prototype. (Badal)
>
> Signed-off-by: Karthik Poosa <karthik.poosa@intel.com>
> Fixes: 92d44a422d0d ("drm/xe/hwmon: Expose card reactive critical power")
> ---
> drivers/gpu/drm/xe/xe_hwmon.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/xe/xe_hwmon.c b/drivers/gpu/drm/xe/xe_hwmon.c
> index 832ea81faeee..1faeca70900e 100644
> --- a/drivers/gpu/drm/xe/xe_hwmon.c
> +++ b/drivers/gpu/drm/xe/xe_hwmon.c
> @@ -450,7 +450,7 @@ static int xe_hwmon_pcode_write_i1(struct xe_gt *gt, u32 uval)
> {
> return xe_pcode_write(gt, PCODE_MBOX(PCODE_POWER_SETUP,
> POWER_SETUP_SUBCOMMAND_WRITE_I1, 0),
> - uval);
> + (uval & POWER_SETUP_I1_DATA_MASK));
> }
>
> static int xe_hwmon_power_curr_crit_read(struct xe_hwmon *hwmon, int channel,
prev parent reply other threads:[~2024-08-27 11:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-26 13:36 [PATCH v2] drm/xe/hwmon: Fix WRITE_I1 param from u32 to u16 Karthik Poosa
2024-08-26 13:40 ` ✓ CI.Patch_applied: success for " Patchwork
2024-08-26 13:40 ` ✓ CI.checkpatch: " Patchwork
2024-08-26 13:41 ` ✓ CI.KUnit: " Patchwork
2024-08-26 13:53 ` ✓ CI.Build: " Patchwork
2024-08-26 13:55 ` ✓ CI.Hooks: " Patchwork
2024-08-26 13:56 ` ✓ CI.checksparse: " Patchwork
2024-08-26 14:16 ` ✓ CI.BAT: " Patchwork
2024-08-26 17:54 ` ✗ CI.FULL: failure " Patchwork
2024-08-27 11:12 ` Nilawar, Badal [this message]
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=57df9581-2125-4044-9804-4bb4bf5c68d6@intel.com \
--to=badal.nilawar@intel.com \
--cc=anshuman.gupta@intel.com \
--cc=ashutosh.dixit@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=karthik.poosa@intel.com \
--cc=rodrigo.vivi@intel.com \
--cc=vinay.belgaumkar@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