From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Paulo Zanoni <przanoni@gmail.com>
Cc: intel-gfx@lists.freedesktop.org, Paulo Zanoni <paulo.r.zanoni@intel.com>
Subject: Re: [PATCH] drm/i915: VGA also requires the power well
Date: Thu, 6 Jun 2013 17:47:20 +0300 [thread overview]
Message-ID: <20130606144720.GN5004@intel.com> (raw)
In-Reply-To: <CA+gsUGRos29Ua=SFMJSnMkhZ9A=aY6DqFjESHZHPCVj-45BhmA@mail.gmail.com>
On Thu, Jun 06, 2013 at 11:35:15AM -0300, Paulo Zanoni wrote:
> 2013/6/6 Ville Syrjälä <ville.syrjala@linux.intel.com>:
> > On Wed, Jun 05, 2013 at 06:05:51PM -0300, Paulo Zanoni wrote:
> >> From: Paulo Zanoni <paulo.r.zanoni@intel.com>
> >>
> >> So add a power domain and check for it before we try to read
> >> VGA_CONTROL.
> >>
> >> This fixes unclaimed register messages that happen on suspend/resume.
> >>
> >> Signed-off-by: Paulo Zanoni <paulo.r.zanoni@intel.com>
> >> ---
> >> drivers/gpu/drm/i915/i915_drv.h | 1 +
> >> drivers/gpu/drm/i915/intel_display.c | 3 +++
> >> drivers/gpu/drm/i915/intel_pm.c | 1 +
> >> 3 files changed, 5 insertions(+)
> >>
> >> diff --git a/drivers/gpu/drm/i915/i915_drv.h b/drivers/gpu/drm/i915/i915_drv.h
> >> index 46b1f70..d51ce13 100644
> >> --- a/drivers/gpu/drm/i915/i915_drv.h
> >> +++ b/drivers/gpu/drm/i915/i915_drv.h
> >> @@ -89,6 +89,7 @@ enum port {
> >> #define port_name(p) ((p) + 'A')
> >>
> >> enum intel_display_power_domain {
> >> + POWER_DOMAIN_VGA,
> >> POWER_DOMAIN_PIPE_A,
> >> POWER_DOMAIN_PIPE_B,
> >> POWER_DOMAIN_PIPE_C,
> >> diff --git a/drivers/gpu/drm/i915/intel_display.c b/drivers/gpu/drm/i915/intel_display.c
> >> index 4c8fcec..3719d99 100644
> >> --- a/drivers/gpu/drm/i915/intel_display.c
> >> +++ b/drivers/gpu/drm/i915/intel_display.c
> >> @@ -9950,6 +9950,9 @@ void i915_redisable_vga(struct drm_device *dev)
> >> struct drm_i915_private *dev_priv = dev->dev_private;
> >> u32 vga_reg = i915_vgacntrl_reg(dev);
> >>
> >> + if (!intel_display_power_enabled(dev, POWER_DOMAIN_VGA))
> >> + return;
> >> +
> >
> > So it looks like you're essentially making intel_redisable_vga() a nop
> > for HSW.
>
> It's not a nop for HSW, it's only a nop if the power well is disabled,
> which means VGA is disabled, so it's a nop if VGA is disabled. But if
> you look at the current function it's also a nop if VGA is disabled.
> So we're keeping the same behavior, but checking the power well before
> checking vga_reg.
>
> VGA mode requires the power well to be enabled, we can be sure that if
> the power well is disabled, then VGA is disabled, so you don't need to
> do the check for VGA_DISP_DISABLE.
Rigth, but intel_display_power_enabled() only checks the driver power
well register. If BIOS can leave VGA enabled, then I guess it could've
left the power well on too. So I'm thinking we should check for that
rather than the what the driver requested.
--
Ville Syrjälä
Intel OTC
next prev parent reply other threads:[~2013-06-06 14:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-05 21:05 [PATCH] drm/i915: VGA also requires the power well Paulo Zanoni
2013-06-06 8:38 ` Ville Syrjälä
2013-06-06 14:35 ` Paulo Zanoni
2013-06-06 14:47 ` Ville Syrjälä [this message]
2013-08-02 17:17 ` Paulo Zanoni
2013-08-02 17:17 ` Paulo Zanoni
2013-08-04 19:49 ` Daniel Vetter
2013-08-12 18:06 ` Zanoni, Paulo R
2013-08-14 14:41 ` Daniel Vetter
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=20130606144720.GN5004@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=paulo.r.zanoni@intel.com \
--cc=przanoni@gmail.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