From: Clint Taylor <clinton.a.taylor@intel.com>
To: Intel-gfx@lists.freedesktop.org
Subject: [PATCH] drm/i915/display/dp: Reduce log level for SOURCE OUI write failures
Date: Fri, 4 Oct 2024 14:08:16 -0700 [thread overview]
Message-ID: <20241004210816.3976058-1-clinton.a.taylor@intel.com> (raw)
Some devices NAK DPCD writes to the SOURCE OUI (0x300) DPCD registers.
Reduce the log level priority to prevent dmesg noise for these devices.
Signed-off-by: Clint Taylor <clinton.a.taylor@intel.com>
---
drivers/gpu/drm/i915/display/intel_dp.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/i915/display/intel_dp.c b/drivers/gpu/drm/i915/display/intel_dp.c
index fbb096be02ad..9920ec1f9c53 100644
--- a/drivers/gpu/drm/i915/display/intel_dp.c
+++ b/drivers/gpu/drm/i915/display/intel_dp.c
@@ -3418,7 +3418,7 @@ intel_edp_init_source_oui(struct intel_dp *intel_dp, bool careful)
}
if (drm_dp_dpcd_write(&intel_dp->aux, DP_SOURCE_OUI, oui, sizeof(oui)) < 0)
- drm_err(&i915->drm, "Failed to write source OUI\n");
+ drm_info(&i915->drm, "Failed to write source OUI\n");
intel_dp->last_oui_write = jiffies;
}
--
2.25.1
next reply other threads:[~2024-10-04 21:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-04 21:08 Clint Taylor [this message]
2024-10-08 1:51 ` ✗ Fi.CI.BAT: failure for drm/i915/display/dp: Reduce log level for SOURCE OUI write failures Patchwork
2024-10-09 17:02 ` [PATCH] " Pottumuttu, Sai Teja
2024-10-10 21:30 ` Taylor, Clinton A
2024-10-11 7:04 ` Pottumuttu, Sai Teja
2024-10-16 19:42 ` Taylor, Clinton A
2024-10-17 6:46 ` Pottumuttu, Sai Teja
2024-10-29 16:33 ` ✓ Fi.CI.BAT: success for drm/i915/display/dp: Reduce log level for SOURCE OUI write failures (rev2) Patchwork
2024-10-30 0:10 ` ✗ Fi.CI.IGT: failure " Patchwork
2024-10-30 0:26 ` Matt Roper
2024-10-30 21:50 ` Patchwork
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=20241004210816.3976058-1-clinton.a.taylor@intel.com \
--to=clinton.a.taylor@intel.com \
--cc=Intel-gfx@lists.freedesktop.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