public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Paulo Zanoni <przanoni@gmail.com>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
	intel-gfx@lists.freedesktop.org, "Zanoni,
	Paulo R" <paulo.r.zanoni@intel.com>
Subject: Re: [PATCH] drm/i915: Enable DP audio for Haswell
Date: Mon, 19 Nov 2012 18:05:08 +0100	[thread overview]
Message-ID: <s5hsj855xrv.wl%tiwai@suse.de> (raw)
In-Reply-To: <CA+gsUGRucnMmvGWURtTQPeCefTL+hs9dQ3mLo+fiWn9-3CntTw@mail.gmail.com>

At Mon, 19 Nov 2012 15:01:59 -0200,
Paulo Zanoni wrote:
> 
> Hi
> 
> drivers/gpu/drm/i915/intel_ddi.c: In function ‘intel_ddi_mode_set’:
> drivers/gpu/drm/i915/intel_ddi.c:672:7: error: ‘intel_hdmi’ undeclared
> (first use in this function)
> drivers/gpu/drm/i915/intel_ddi.c:672:7: note: each undeclared
> identifier is reported only once for each function it appears in
> make[4]: ** [drivers/gpu/drm/i915/intel_ddi.o] Erro 1

Doh, sorry, I posted a version before refreshing.
Will submit the right one soon.

> 2012/11/16 Takashi Iwai <tiwai@suse.de>:
> > This patch adds the missing code to send ELD for Haswell DisplayPort,
> > based on Xingchao's original patch.
> >
> > A test was performed with HSW-D machine and NEC EA232Wmi DP monitor.
> >
> > Cc: Xingchao Wang <xingchao.wang@intel.com>
> > Signed-off-by: Takashi Iwai <tiwai@suse.de>
> > ---
> >  drivers/gpu/drm/i915/intel_ddi.c | 9 +++++++++
> >  1 file changed, 9 insertions(+)
> >
> > diff --git a/drivers/gpu/drm/i915/intel_ddi.c b/drivers/gpu/drm/i915/intel_ddi.c
> > index 58f50eb..d8dbd99 100644
> > --- a/drivers/gpu/drm/i915/intel_ddi.c
> > +++ b/drivers/gpu/drm/i915/intel_ddi.c
> > @@ -669,6 +669,15 @@ static void intel_ddi_mode_set(struct drm_encoder *encoder,
> >                         break;
> >                 }
> >
> > +               if (intel_hdmi->has_audio) {
> 
> Replacing it with intel_dp->has_audio makes it look correct.
> 
> You could also try to "unify" the 2 "has_audio" checks of this
> function into one single check at the end of the function.

Yes.  A more refactoring is possible, but I left it as is from the
safety side.


thanks,

Takashi

> > +                       DRM_DEBUG_DRIVER("DP audio on pipe %c on DDI\n",
> > +                                        pipe_name(intel_crtc->pipe));
> > +
> > +                       /* write eld */
> > +                       DRM_DEBUG_DRIVER("DP audio: write eld information\n");
> > +                       intel_write_eld(encoder, adjusted_mode);
> > +               }
> > +
> >                 intel_dp_init_link_config(intel_dp);
> >
> >         } else if (type == INTEL_OUTPUT_HDMI) {
> > --
> > 1.8.0
> >
> > _______________________________________________
> > Intel-gfx mailing list
> > Intel-gfx@lists.freedesktop.org
> > http://lists.freedesktop.org/mailman/listinfo/intel-gfx
> 
> 
> 
> -- 
> Paulo Zanoni
> 
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

      reply	other threads:[~2012-11-19 17:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-16 14:48 [PATCH] drm/i915: Enable DP audio for Haswell Takashi Iwai
2012-11-19 17:01 ` Paulo Zanoni
2012-11-19 17:05   ` Takashi Iwai [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=s5hsj855xrv.wl%tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=daniel.vetter@ffwll.ch \
    --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