All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>,
	Mukesh <mukeshx.arora@intel.com>
Subject: Re: [PATCH v2] drm/i915/hsw: Add display Audio codec disable sequence for Haswell
Date: Thu, 5 Sep 2013 14:33:20 +0300	[thread overview]
Message-ID: <20130905113320.GY11428@intel.com> (raw)
In-Reply-To: <CAKMK7uEQEdXys-aeeD7Dy_FgLODeAF+fS-_jR_7Ch5_KekZ-Yw@mail.gmail.com>

On Wed, Sep 04, 2013 at 08:50:13PM +0200, Daniel Vetter wrote:
> On Fri, Aug 30, 2013 at 1:50 AM,  <mengdong.lin@intel.com> wrote:
> > +       /* Wait for 2 vertical blanks */
> > +       intel_wait_for_vblank(dev, pipe);
> > +       intel_wait_for_vblank(dev, pipe);
> > +
> > +       /* Disable audio PD. This is optional as per Bspec.  */
> > +       temp = I915_READ(HSW_AUD_PIN_ELD_CP_VLD);
> > +       temp &= ~(AUDIO_OUTPUT_ENABLE_A << (pipe * 4));
> > +       I915_WRITE(HSW_AUD_PIN_ELD_CP_VLD, temp);
> 
> If this is optional do we really need the two vblank waits above?
> Adding them just for fun when we generally try to rip out as many
> vblank waits as possible from the modeset code isn't all that great
> ...

One idea I had for these kinds of vblank waits (there also one required
for IPS for instance) is that we might just sample a vblank counter
after the first step, then at the latest point we can, we'd wait for the
frame counter to have passed the sampled vaoue + whatever extra is
needed. That might allow us to do other stuff in parallel while the
required number of vblanks will elapese.

-- 
Ville Syrjälä
Intel OTC

  reply	other threads:[~2013-09-05 11:33 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-29 23:50 [PATCH v2] drm/i915/hsw: Add display Audio codec disable sequence for Haswell mengdong.lin
2013-09-04 17:02 ` Ben Widawsky
2013-09-23  6:35   ` Lin, Mengdong
2013-09-04 18:50 ` Daniel Vetter
2013-09-05 11:33   ` Ville Syrjälä [this message]
2013-09-05 11:45     ` Daniel Vetter
2013-09-05 12:21       ` Ville Syrjälä
2013-09-05 12:27         ` Daniel Vetter
2013-09-23  8:52   ` Lin, Mengdong
2013-09-23  8:57     ` Daniel Vetter
2013-09-23  9:13       ` Lin, Mengdong

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=20130905113320.GY11428@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=daniel@ffwll.ch \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=mukeshx.arora@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.