From: Aravind Iddamsetty <aravind.iddamsetty@linux.intel.com>
To: Raag Jadav <raag.jadav@intel.com>,
lucas.demarchi@intel.com, rodrigo.vivi@intel.com,
anshuman.gupta@intel.com, badal.nilawar@intel.com,
riana.tauro@intel.com
Cc: intel-xe@lists.freedesktop.org
Subject: Re: [PATCH v1] drm/xe/pcode: stop logging mailbox status as error
Date: Thu, 6 Mar 2025 10:08:07 +0530 [thread overview]
Message-ID: <29d173b4-4cac-4765-a13e-8723b44f5270@linux.intel.com> (raw)
In-Reply-To: <20250304061727.452100-1-raag.jadav@intel.com>
On 04-03-2025 11:47, Raag Jadav wrote:
Hi Raag,
> Since we're expecting many platform specific mailbox commands that
> might not be widely supported, stop logging them as errors. With this
> we can avoid unnecessary platform checks and use the return value of
> mailbox without enraging CI.
are you saying there are cases where we send a command that is not supported
on a particular platform?
Thanks,
Aravind.
>
> Signed-off-by: Raag Jadav <raag.jadav@intel.com>
> ---
> drivers/gpu/drm/xe/xe_pcode.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/xe/xe_pcode.c b/drivers/gpu/drm/xe/xe_pcode.c
> index 9333ce776a6e..280f69119ff1 100644
> --- a/drivers/gpu/drm/xe/xe_pcode.c
> +++ b/drivers/gpu/drm/xe/xe_pcode.c
> @@ -46,7 +46,7 @@ static int pcode_mailbox_status(struct xe_tile *tile)
>
> err = xe_mmio_read32(&tile->mmio, PCODE_MAILBOX) & PCODE_ERROR_MASK;
> if (err) {
> - drm_err(&tile_to_xe(tile)->drm, "PCODE Mailbox failed: %d %s", err,
> + drm_dbg(&tile_to_xe(tile)->drm, "PCODE Mailbox failed: %d %s", err,
> err_decode[err].str ?: "Unknown");
> return err_decode[err].errno ?: -EPROTO;
> }
next prev parent reply other threads:[~2025-03-06 4:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-04 6:17 [PATCH v1] drm/xe/pcode: stop logging mailbox status as error Raag Jadav
2025-03-04 7:00 ` ✓ CI.Patch_applied: success for " Patchwork
2025-03-04 7:00 ` ✓ CI.checkpatch: " Patchwork
2025-03-04 7:02 ` ✓ CI.KUnit: " Patchwork
2025-03-04 7:18 ` ✓ CI.Build: " Patchwork
2025-03-04 7:20 ` ✓ CI.Hooks: " Patchwork
2025-03-04 7:22 ` ✓ CI.checksparse: " Patchwork
2025-03-04 7:40 ` ✓ Xe.CI.BAT: " Patchwork
2025-03-04 8:41 ` ✗ Xe.CI.Full: failure " Patchwork
2025-03-06 4:38 ` Aravind Iddamsetty [this message]
2025-03-06 8:57 ` [PATCH v1] " Raag Jadav
2025-03-06 9:47 ` Aravind Iddamsetty
2025-03-06 10:44 ` Raag Jadav
2025-03-06 16:13 ` Rodrigo Vivi
2025-03-06 18:11 ` Raag Jadav
2025-03-06 19:19 ` Raag Jadav
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=29d173b4-4cac-4765-a13e-8723b44f5270@linux.intel.com \
--to=aravind.iddamsetty@linux.intel.com \
--cc=anshuman.gupta@intel.com \
--cc=badal.nilawar@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=lucas.demarchi@intel.com \
--cc=raag.jadav@intel.com \
--cc=riana.tauro@intel.com \
--cc=rodrigo.vivi@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