From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915/vlv: assert and de-assert sideband reset at boot and resume v3
Date: Wed, 21 May 2014 11:11:15 -0700 [thread overview]
Message-ID: <20140521111115.5b667246@jbarnes-desktop> (raw)
In-Reply-To: <20140521175403.GS27580@intel.com>
And to answer more specifically...
On Wed, 21 May 2014 20:54:03 +0300
Ville Syrjälä <ville.syrjala@linux.intel.com> wrote:
> > + __vlv_set_power_well(dev_priv, PUNIT_POWER_WELL_DPIO_CMN_BC,
> > + false);
> > + __vlv_set_power_well(dev_priv, PUNIT_POWER_WELL_DPIO_CMN_BC,
> > + true);
>
> Hmm. I wonder how the power well hack in intel_uncore_sanitize() ties in
> with this. We should definitely rip that out regardless.
Yeah we can rip that out. That's just an ungate, and it assumes the
BIOS has already done the reset toggle for us.
> Another thing I'm wodering is did the BIOS/hw really power on the
> common lane, or did we do that outselves? If the latter, then I wonder
> if we simply do that too early. Or more precisely do we need to make
> sure the cri clock and/or refclock are enabled before we power on the
> common lane?
Depends on the platform. It looks like the right thing happens at boot
time on most machines (i.e. the BIOS does a full toggle which causes a
reset), but on suspend/resume it's up to us. And of course on machines
without video init at boot time, we need to do it ourselves as well.
I don't think the cri or refclk is required at this point, at least not
if the docs we have are correct (the PHY reset is supposed to be the
very first thing).
> And third is that do we need to enable the TX wells before the CMN
> well? Currently we do the opposite which could also explain why this
> CMN well toggle fixes things.
I don't think that matters, but we should ask the PHY guys. The lack
of symmetry between the gate and ungate bothers me too.
--
Jesse Barnes, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2014-05-21 18:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-19 23:16 [PATCH] drm/i915/vlv: assert and de-assert sideband reset at boot and resume v2 Jesse Barnes
2014-05-20 18:09 ` [PATCH] drm/i915/vlv: assert and de-assert sideband reset at boot and resume v3 Jesse Barnes
2014-05-21 17:54 ` Ville Syrjälä
2014-05-21 18:06 ` Jesse Barnes
2014-05-21 18:11 ` Jesse Barnes [this message]
2014-05-21 18:43 ` Ville Syrjälä
2014-05-22 6:51 ` Imre Deak
2014-05-22 8:10 ` Ville Syrjälä
2014-05-22 15:43 ` Jesse Barnes
2014-05-23 19:50 ` Jesse Barnes
2014-05-20 18:10 ` [PATCH] drm/i915/vlv: assert and de-assert sideband reset at boot and resume v2 Jesse Barnes
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=20140521111115.5b667246@jbarnes-desktop \
--to=jbarnes@virtuousgeek.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=ville.syrjala@linux.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