From: Daniel Vetter <daniel@ffwll.ch>
To: Damien Lespiau <damien.lespiau@intel.com>
Cc: Daniel Vetter <daniel.vetter@intel.com>,
intel-gfx <intel-gfx@lists.freedesktop.org>
Subject: Re: [v3] drm/i915: Detect if MIPI panel based on VBT and initialize only if present
Date: Tue, 27 May 2014 19:05:15 +0200 [thread overview]
Message-ID: <20140527170515.GF14841@phenom.ffwll.local> (raw)
In-Reply-To: <20140527143544.GB27337@strange.amr.corp.intel.com>
On Tue, May 27, 2014 at 03:35:44PM +0100, Damien Lespiau wrote:
> On Tue, May 27, 2014 at 05:31:42PM +0300, Ville Syrjälä wrote:
> > On Tue, May 27, 2014 at 03:17:15PM +0100, Damien Lespiau wrote:
> > > Sorry to be such a bore but:
> > >
> > > On Tue, May 27, 2014 at 07:33:59PM +0530, Shobhit Kumar wrote:
> > > > --- a/drivers/gpu/drm/i915/intel_dsi.c
> > > > +++ b/drivers/gpu/drm/i915/intel_dsi.c
> > > > @@ -660,6 +660,10 @@ bool intel_dsi_init(struct drm_device *dev)
> > > >
> > > > DRM_DEBUG_KMS("\n");
> > > >
> > > > + /* There is no detection method for MIPI so rely on VBT */
> > > > + if (!dev_priv->vbt.has_mipi)
> > > > + return false;
> > > > +
> > >
> > > Huum, if we can intel_dsi_init() on VLV, but we don't have a MIPI panel,
> > > shouldn't return true here? ie. "intel_dsi_init() was successful, we
> > > just don't have a MIPI panel.
> >
> > Why does it even have a return value? Either it added the
> > connector and encoder or it didn't.
>
> That's even better. I guess we can have a patch on top once this one has
> landed.
dp_init has this since edp init can fail and that decides what we will do
with it occasionally. But that's about it wrt reasons for a return value
for a encoder init function. Please remove.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
next prev parent reply other threads:[~2014-05-27 17:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-23 16:09 [PATCH] drm/i915: Detect if MIPI panel based on VBT and initialize only if present Shobhit Kumar
2014-05-27 11:32 ` Damien Lespiau
2014-05-27 12:10 ` Kumar, Shobhit
2014-05-27 12:27 ` Damien Lespiau
2014-05-27 11:40 ` Daniel Vetter
2014-05-27 11:43 ` Kumar, Shobhit
2014-05-27 12:56 ` [v2] " Shobhit Kumar
2014-05-27 13:18 ` Damien Lespiau
2014-05-27 14:03 ` [v3] " Shobhit Kumar
2014-05-27 14:17 ` Damien Lespiau
2014-05-27 14:31 ` Ville Syrjälä
2014-05-27 14:35 ` Damien Lespiau
2014-05-27 17:05 ` Daniel Vetter [this message]
2014-05-27 14:31 ` Kumar, Shobhit
2014-05-27 17:10 ` 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=20140527170515.GF14841@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=damien.lespiau@intel.com \
--cc=daniel.vetter@intel.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox