From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: "Pandiyan, Dhinakaran" <dhinakaran.pandiyan@intel.com>
Cc: "Nikula, Jani" <jani.nikula@intel.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH] drm/i915: Show debugfs dpcd read failure directly
Date: Mon, 20 Aug 2018 17:13:47 -0700 [thread overview]
Message-ID: <20180821001347.GB9160@intel.com> (raw)
In-Reply-To: <45c05d4cdd5cd132d91a1e2cc517443c257323da.camel@intel.com>
On Mon, Aug 20, 2018 at 12:10:08PM -0700, Pandiyan, Dhinakaran wrote:
>
>
> On Mon, 2018-08-20 at 10:15 +0300, Jani Nikula wrote:
> > On Fri, 20 Jul 2018, Rodrigo Vivi <rodrigo.vivi@intel.com> wrote:
> > > Instead of using a backchannel if some dpcd read failed we
> > > can show that directly on debugfs output.
> > >
> > > We are not returning an error because we might still want
> > > to know if sub-sequent reads works, but we shouldn't
> > > need to check 2 places to see why reg is not on the list.
> >
> > Should we just nuke this debugfs and use the aux chardev interface to
> > dpcd instead?
>
> Given that this debugfs does not print decoded information, I think, it
> offers very little benefit over direct reads. We also print some DPCD's
> in dmesg, so I'm in favour of killing it. Don't see the file being used
> in IGTs either.
>
> Your comment also reminds about the IGT tool that Tarun started writing
> for reading DPCD.
There might be people out there using this for debug. So we should first
be able to do this in some place like IGT:
https://patchwork.freedesktop.org/series/48470/ ?
then we remove. But that discussion might take a while. So I'd like
to move with this fix here now and remove dpcd_show completely when
we create some infrastructure on IGT.
>
> -DK
>
>
> >
> > BR,
> > Jani.
> >
> > >
> > > Cc: Jani Nikula <jani.nikula@intel.com>
> > > Cc: Dhinakaran Pandiyan <dhinakaran.pandiyan@intel.com>
> > > Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
> > > ---
> > > drivers/gpu/drm/i915/i915_debugfs.c | 4 ++--
> > > 1 file changed, 2 insertions(+), 2 deletions(-)
> > >
> > > diff --git a/drivers/gpu/drm/i915/i915_debugfs.c
> > > b/drivers/gpu/drm/i915/i915_debugfs.c
> > > index 59dc0610ea44..5d8da4e8c444 100644
> > > --- a/drivers/gpu/drm/i915/i915_debugfs.c
> > > +++ b/drivers/gpu/drm/i915/i915_debugfs.c
> > > @@ -4846,8 +4846,8 @@ static int i915_dpcd_show(struct seq_file *m,
> > > void *data)
> > >
> > > err = drm_dp_dpcd_read(&intel_dp->aux, b->offset,
> > > buf, size);
> > > if (err <= 0) {
> > > - DRM_ERROR("dpcd read (%zu bytes at %u)
> > > failed (%zd)\n",
> > > - size, b->offset, err);
> > > + seq_printf(m, "dpcd read (%zu bytes at %u)
> > > failed (%zd)\n",
> > > + size, b->offset, err);
> > > continue;
> > > }
> >
> >
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2018-08-21 0:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-20 17:41 [PATCH] drm/i915: Show debugfs dpcd read failure directly Rodrigo Vivi
2018-07-20 19:16 ` ✓ Fi.CI.BAT: success for " Patchwork
2018-07-20 21:38 ` [PATCH] " Dhinakaran Pandiyan
2018-07-21 17:44 ` ✓ Fi.CI.IGT: success for " Patchwork
2018-07-28 16:05 ` [PATCH] " Chris Wilson
2018-08-20 7:15 ` Jani Nikula
2018-08-20 19:10 ` Pandiyan, Dhinakaran
2018-08-21 0:13 ` Rodrigo Vivi [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=20180821001347.GB9160@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=dhinakaran.pandiyan@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@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;
as well as URLs for NNTP newsgroup(s).