All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Wilson <chris@chris-wilson.co.uk>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH 1/2] drm/i915: fixed EDID/sink-based bpp clamping
Date: Sat, 1 Jun 2013 18:52:39 +0100	[thread overview]
Message-ID: <20130601175239.GG11399@cantiga.alporthouse.com> (raw)
In-Reply-To: <1370108756-1948-1-git-send-email-daniel.vetter@ffwll.ch>

On Sat, Jun 01, 2013 at 07:45:55PM +0200, Daniel Vetter wrote:
> Since this is run in the compute config stage we need to check
> the new_ pointers, not the current modeset layout. Also there
> was a little logic bug in properly skipping connectors. This has
> been broken when moving the pipe bpp selection in
> 
> commit 4e53c2e010e531b4a014692199e978482d471c7e
> Author: Daniel Vetter <daniel.vetter@ffwll.ch>
> Date:   Wed Mar 27 00:44:58 2013 +0100
> 
>     drm/i915: precompute pipe bpp before touching the hw
> 
> To avoid too much casting switch from drm_ to intel_ types.
> 
> Also add a bit of debug output to help reconstructing what's going
> on.

Baffling. It is really hard to tell what is going on, so perhaps it is
worth investing in some more descriptive names. How about:
  struct drm_display_info *desired = &connector->base.display_info ?
Or some other name? And an indication in the function name at which
stage this is meant to run?
-Chris

-- 
Chris Wilson, Intel Open Source Technology Centre

  parent reply	other threads:[~2013-06-01 17:52 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-01 17:45 [PATCH 1/2] drm/i915: fixed EDID/sink-based bpp clamping Daniel Vetter
2013-06-01 17:45 ` [PATCH 2/2] drm/i915: enable 30bpp for DP outputs Daniel Vetter
2013-06-07  5:51   ` Daniel Vetter
2013-06-07  8:00     ` Chris Wilson
2013-06-07  8:35       ` Daniel Vetter
2013-06-01 17:52 ` Chris Wilson [this message]
2013-06-01 19:10   ` [PATCH 1/2] drm/i915: fixed EDID/sink-based bpp clamping Daniel Vetter
2013-06-01 19:24   ` [PATCH] drm/i915: fix " Daniel Vetter
2013-06-01 21:53   ` Daniel Vetter
2013-06-02 10:09     ` Chris Wilson
2013-06-02 11:22       ` Daniel Vetter
2013-06-02 11:26       ` [PATCH 1/2] drm/i915: refactor sink " Daniel Vetter
2013-06-02 11:26         ` [PATCH 2/2] drm/i915: fix EDID/sink-based " Daniel Vetter
2013-06-03  7:50           ` Chris Wilson
2013-06-04 11:53             ` Daniel Vetter
2013-06-03  9:17         ` [PATCH 1/2] drm/i915: refactor sink " 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=20130601175239.GG11399@cantiga.alporthouse.com \
    --to=chris@chris-wilson.co.uk \
    --cc=daniel.vetter@ffwll.ch \
    --cc=intel-gfx@lists.freedesktop.org \
    /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.