From: Daniel Vetter <daniel@ffwll.ch>
To: Paulo Zanoni <przanoni@gmail.com>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
Paulo Zanoni <paulo.r.zanoni@intel.com>
Subject: Re: [PATCH 1/3] drm/i915: hw state readout&check support for cpu_transcoder
Date: Tue, 28 May 2013 11:41:13 +0200 [thread overview]
Message-ID: <20130528094113.GY15743@phenom.ffwll.local> (raw)
In-Reply-To: <CA+gsUGRGqyfGzy5sprn3nJZgVBkHv5BkfXs809R5ma-DjAEN8g@mail.gmail.com>
On Mon, May 27, 2013 at 05:45:53PM -0300, Paulo Zanoni wrote:
> 2013/5/21 Daniel Vetter <daniel.vetter@ffwll.ch>:
> > + pipe_config->cpu_transcoder = crtc->pipe;
> > + tmp = I915_READ(TRANS_DDI_FUNC_CTL(TRANSCODER_EDP));
> > + if (tmp & TRANS_DDI_FUNC_ENABLE) {
> > + enum pipe trans_edp_pipe;
> > + switch (tmp & TRANS_DDI_EDP_INPUT_MASK) {
> > + default:
> > + WARN(1, "unknown pipe linked to edp transcoder\n");
>
> Since there's no "break" we'll assign PIPE_A and then we'll probably
> break pipe A on this case. OTOH this case should never really happen,
> so I'm not sure if we care. So this is an optional bikeshedding.
Generally I prefer to have as little fallback code as possible for such
impossible cases. Avoiding the break makes sure we have at elast a valid
pipe value and so hopefully increase our chances that the following code
survives. No matter what we're pretty much guaranteed to end up with a
black screen.
> Reviewed-by: Paulo Zanoni <paulo.r.zanoni@intel.com>
Thanks for the review, first 2 patches are merged to dinq now.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
prev parent reply other threads:[~2013-05-28 9:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-03 20:11 [PATCH] drm/i915: hw state readout&check support for cpu_transcoder Daniel Vetter
2013-05-10 8:02 ` Daniel Vetter
2013-05-21 22:50 ` [PATCH 1/3] " Daniel Vetter
2013-05-21 22:50 ` [PATCH 2/3] drm/i915: fixup i915_pipe_enabled check in i915_irq.c Daniel Vetter
2013-05-27 20:56 ` Paulo Zanoni
2013-05-21 22:50 ` [PATCH 3/3] drm/i915: add basic pipe config dump support Daniel Vetter
2013-05-27 21:30 ` Paulo Zanoni
2013-05-28 9:11 ` Daniel Vetter
2013-05-28 10:05 ` [PATCH] " Daniel Vetter
2013-05-28 14:17 ` Paulo Zanoni
2013-05-28 14:29 ` Daniel Vetter
2013-05-27 20:45 ` [PATCH 1/3] drm/i915: hw state readout&check support for cpu_transcoder Paulo Zanoni
2013-05-28 9:41 ` Daniel Vetter [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=20130528094113.GY15743@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--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