From: Jani Nikula <jani.nikula@linux.intel.com>
To: Paulo Zanoni <przanoni@gmail.com>, intel-gfx@lists.freedesktop.org
Cc: Paulo Zanoni <paulo.r.zanoni@intel.com>
Subject: Re: [PATCH] drm/i915: use the correct encoder type when comparing
Date: Fri, 10 Aug 2012 16:27:23 +0300 [thread overview]
Message-ID: <874noakhc4.fsf@intel.com> (raw)
In-Reply-To: <1344603910-4518-1-git-send-email-przanoni@gmail.com>
On Fri, 10 Aug 2012, Paulo Zanoni <przanoni@gmail.com> wrote:
> From: Paulo Zanoni <paulo.r.zanoni@intel.com>
>
> - intel_encoder->type is INTEL_OUTPUT_SOMETHING
> - drm_encoder->encoder_type is DRM_MODE_ENCODER_SOMETHING
>
> Here we're using intel_encoder, so compare the oranges against
> oranges. While at it, rename the variable to "intel_encoder" so we
> keep our naming standards used everywhere.
intel_display.c still has plenty of 'struct intel_encoder *encoder'...
Reviewed-by: Jani Nikula <jani.nikula@intel.com>
> Luckily this was not a bug because both DRM_MODE_ENCODER_DAC and
> INTEL_OUTPUT_ANALOG are defined as 1. This is the only case where the
> drm definition matches the intel definition.
>
> Signed-off-by: Paulo Zanoni <paulo.r.zanoni@intel.com>
> ---
> drivers/gpu/drm/i915/intel_display.c | 12 ++++++------
> 1 file changed, 6 insertions(+), 6 deletions(-)
>
> This was not tested, just compiled :)
>
> diff --git a/drivers/gpu/drm/i915/intel_display.c b/drivers/gpu/drm/i915/intel_display.c
> index 2e1f28f..ea19a72 100644
> --- a/drivers/gpu/drm/i915/intel_display.c
> +++ b/drivers/gpu/drm/i915/intel_display.c
> @@ -2837,13 +2837,13 @@ static void intel_crtc_wait_for_pending_flips(struct drm_crtc *crtc)
> static bool intel_crtc_driving_pch(struct drm_crtc *crtc)
> {
> struct drm_device *dev = crtc->dev;
> - struct intel_encoder *encoder;
> + struct intel_encoder *intel_encoder;
>
> /*
> * If there's a non-PCH eDP on this crtc, it must be DP_A, and that
> * must be driven by its own crtc; no sharing is possible.
> */
> - for_each_encoder_on_crtc(dev, crtc, encoder) {
> + for_each_encoder_on_crtc(dev, crtc, intel_encoder) {
>
> /* On Haswell, LPT PCH handles the VGA connection via FDI, and Haswell
> * CPU handles all others */
> @@ -2851,19 +2851,19 @@ static bool intel_crtc_driving_pch(struct drm_crtc *crtc)
> /* It is still unclear how this will work on PPT, so throw up a warning */
> WARN_ON(!HAS_PCH_LPT(dev));
>
> - if (encoder->type == DRM_MODE_ENCODER_DAC) {
> + if (intel_encoder->type == INTEL_OUTPUT_ANALOG) {
> DRM_DEBUG_KMS("Haswell detected DAC encoder, assuming is PCH\n");
> return true;
> } else {
> DRM_DEBUG_KMS("Haswell detected encoder %d, assuming is CPU\n",
> - encoder->type);
> + intel_encoder->type);
> return false;
> }
> }
>
> - switch (encoder->type) {
> + switch (intel_encoder->type) {
> case INTEL_OUTPUT_EDP:
> - if (!intel_encoder_is_pch_edp(&encoder->base))
> + if (!intel_encoder_is_pch_edp(&intel_encoder->base))
> return false;
> continue;
> }
> --
> 1.7.11.2
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2012-08-10 13:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-10 13:05 [PATCH] drm/i915: use the correct encoder type when comparing Paulo Zanoni
2012-08-10 13:27 ` Jani Nikula [this message]
2012-08-10 16:34 ` 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=874noakhc4.fsf@intel.com \
--to=jani.nikula@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