From: Manasi Navare <manasi.d.navare@intel.com>
To: "Pandiyan, Dhinakaran" <dhinakaran.pandiyan@intel.com>
Cc: "intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"Zanoni, Paulo R" <paulo.r.zanoni@intel.com>,
"Vivi, Rodrigo" <rodrigo.vivi@intel.com>
Subject: Re: [PATCH] drm/i915/cnl: Add information to missing case.
Date: Fri, 16 Jun 2017 14:12:39 -0700 [thread overview]
Message-ID: <20170616211239.GA19665@intel.com> (raw)
In-Reply-To: <1497647857.11681.19.camel@dk-H97M-D3H>
On Fri, Jun 16, 2017 at 08:58:25PM +0000, Pandiyan, Dhinakaran wrote:
> On Fri, 2017-06-16 at 13:20 -0700, Rodrigo Vivi wrote:
> > This missing case could be reached out on missing
> > type or missing voltage.
>
> Should we even reach this far with a missing DDI type?
>
> -DK
>
Yes it is possible that we get into this situation if reading
of the vccio voltage from PORT_COMP_DW3 returns a garbage value
due to some corruption or lets say the type is something that is not
supported on this platform.
> > So let's add a debug
> > message to make our lives easier whenever this
> > might happen.
> >
> > Cc: Paulo Zanoni <paulo.r.zanoni@intel.com>
> > Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
> > ---
> > drivers/gpu/drm/i915/intel_ddi.c | 1 +
> > 1 file changed, 1 insertion(+)
> >
> > diff --git a/drivers/gpu/drm/i915/intel_ddi.c b/drivers/gpu/drm/i915/intel_ddi.c
> > index e66947a..c96c8d0 100644
> > --- a/drivers/gpu/drm/i915/intel_ddi.c
> > +++ b/drivers/gpu/drm/i915/intel_ddi.c
> > @@ -1802,6 +1802,7 @@ static void cnl_ddi_vswing_program(struct drm_i915_private *dev_priv,
> > }
> >
> > if (ddi_translations == NULL) {
> > + DRM_DEBUG_KMS("Missing DDI translation table for type %d with voltage %d\n", type, voltage);
> > MISSING_CASE(voltage);
> > return;
> > }
Like Paulo suggested it would be better to use a switch statement for different vccio voltages
and then have this in the default. What do you think?
Manasi
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-06-16 21:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-16 20:20 [PATCH] drm/i915/cnl: Add information to missing case Rodrigo Vivi
2017-06-16 20:58 ` Pandiyan, Dhinakaran
2017-06-16 21:12 ` Manasi Navare [this message]
2017-06-16 21:21 ` Pandiyan, Dhinakaran
2017-06-16 21:26 ` Vivi, Rodrigo
2017-06-16 21:50 ` Pandiyan, Dhinakaran
2017-06-16 21:54 ` Navare, Manasi D
2017-06-16 22:18 ` Vivi, Rodrigo
2017-06-17 8:31 ` Dhinakaran Pandiyan
2017-06-19 16:43 ` Vivi, Rodrigo
2017-06-19 17:19 ` Navare, Manasi D
2017-06-16 21:35 ` ✓ Fi.CI.BAT: success for " 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=20170616211239.GA19665@intel.com \
--to=manasi.d.navare@intel.com \
--cc=dhinakaran.pandiyan@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=paulo.r.zanoni@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.