From: "Taylor, Clinton A" <clinton.a.taylor@intel.com>
To: "Intel-gfx@lists.freedesktop.org"
<Intel-gfx@lists.freedesktop.org>,
"Pottumuttu, Sai Teja" <sai.teja.pottumuttu@intel.com>
Subject: Re: [PATCH] drm/i915/display/dp: Reduce log level for SOURCE OUI write failures
Date: Wed, 16 Oct 2024 19:42:32 +0000 [thread overview]
Message-ID: <c8e19680d2dd8f5e432127faf0cc9c32622bedc5.camel@intel.com> (raw)
In-Reply-To: <85919a8b-0027-4a40-8be0-69be8582d70e@intel.com>
On Fri, 2024-10-11 at 12:34 +0530, Pottumuttu, Sai Teja wrote:
> On 11-10-2024 03:00, Taylor, Clinton A wrote:
> > On Wed, 2024-10-09 at 22:32 +0530, Pottumuttu, Sai Teja wrote:
> > > On 05-10-2024 02:38, Clint Taylor wrote:
> > > > 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");
> > > >
> > > Just had one small question here, I think NAK is one case, but in case
> > > of other errors/failures (EINVAL, ENOMEM) would we still want to reduce
> > > the log level?
> > If EINVAL or ENOMEM occurs there will be plenty of other failures earlier and later
> > that
> > will be logged. This function returns void so we don't handle any failure for
> > SourceOUI
> > write anyway. This just prevents noise in the dmesg log from known devices that NAK
> > this
> > particular DPCD operation. The other option would be to list all known devices that
> > return
> > NAK and filter them via a DCPD quirk.
> >
> > -Clint
> Ok, in that case, should we also consider decreasing the log level of
> read failure a little above?
Read response should never be NAK'd by the Sink device.
-Clint
> >
> > > Thanks,
> > > Sai Teja
> > >
> > > > intel_dp->last_oui_write = jiffies;
> > > > }
next prev parent reply other threads:[~2024-10-16 19:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-04 21:08 [PATCH] drm/i915/display/dp: Reduce log level for SOURCE OUI write failures Clint Taylor
2024-10-08 1:51 ` ✗ Fi.CI.BAT: failure for " 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 [this message]
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=c8e19680d2dd8f5e432127faf0cc9c32622bedc5.camel@intel.com \
--to=clinton.a.taylor@intel.com \
--cc=Intel-gfx@lists.freedesktop.org \
--cc=sai.teja.pottumuttu@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