intel-gfx.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Jani Nikula <jani.nikula@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v2] drm/i915/dsi: skip gpio element execution when not supported
Date: Thu, 4 Feb 2016 19:48:20 +0200	[thread overview]
Message-ID: <20160204174820.GW23290@intel.com> (raw)
In-Reply-To: <87k2mktmp5.fsf@intel.com>

On Thu, Feb 04, 2016 at 07:22:30PM +0200, Jani Nikula wrote:
> On Thu, 04 Feb 2016, Ville Syrjälä <ville.syrjala@linux.intel.com> wrote:
> > On Thu, Feb 04, 2016 at 07:10:42PM +0200, Jani Nikula wrote:
> >> On Thu, 04 Feb 2016, Ville Syrjälä <ville.syrjala@linux.intel.com> wrote:
> >> > On Thu, Feb 04, 2016 at 06:52:47PM +0200, Jani Nikula wrote:
> >> >> Skip v3 gpio element because the support is not there, and skip gpio
> >> >> element on non-vlv because the sideband code is vlv specific.
> >> >> 
> >> >> v2: the gpio stuff is currently only supported on vlv (Ville)
> >> >> 
> >> >> Cc: drm-intel-fixes@lists.freedesktop.org
> >> >> Fixes: 2a33d93486f2 ("drm/i915/bios: add support for MIPI sequence block v3")
> >> >> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
> >> >> ---
> >> >>  drivers/gpu/drm/i915/intel_dsi_panel_vbt.c | 13 +++++++++++++
> >> >>  1 file changed, 13 insertions(+)
> >> >> 
> >> >> diff --git a/drivers/gpu/drm/i915/intel_dsi_panel_vbt.c b/drivers/gpu/drm/i915/intel_dsi_panel_vbt.c
> >> >> index f4d303ee538b..bcc083db7632 100644
> >> >> --- a/drivers/gpu/drm/i915/intel_dsi_panel_vbt.c
> >> >> +++ b/drivers/gpu/drm/i915/intel_dsi_panel_vbt.c
> >> >> @@ -205,6 +205,9 @@ static const u8 *mipi_exec_gpio(struct intel_dsi *intel_dsi, const u8 *data)
> >> >>  	struct drm_device *dev = intel_dsi->base.base.dev;
> >> >>  	struct drm_i915_private *dev_priv = dev->dev_private;
> >> >>  
> >> >> +	if (dev_priv->vbt.dsi.seq_version >= 3)
> >> >> +		data++;
> >> >> +
> >> >
> >> > So here we handle v3
> >> >
> >> >>  	gpio = *data++;
> >> >>  
> >> >>  	/* pull up/down */
> >> >> @@ -215,6 +218,16 @@ static const u8 *mipi_exec_gpio(struct intel_dsi *intel_dsi, const u8 *data)
> >> >>  		goto out;
> >> >>  	}
> >> >>  
> >> >> +	if (!IS_VALLEYVIEW(dev_priv)) {
> >> >> +		DRM_DEBUG_KMS("GPIO element not supported on this platform\n");
> >> >> +		goto out;
> >> >> +	}
> >> >> +
> >> >> +	if (dev_priv->vbt.dsi.seq_version >= 3) {
> >> >> +		DRM_DEBUG_KMS("GPIO element v3 not supported\n");
> >> >> +		goto out;
> >> >> +	}
> >> >
> >> > but here we say it's not supported. Is there more missing?
> >> 
> >> The whole point of doing it this way is to support *skipping* v3 in a
> >> graceful manner. If I bailed out at the top, I'd have to duplicate the
> >> knowledge about the length of the element.
> >
> > Hmm, right. But the question still stands; what more is missing for
> > actual v3 support?
> 
> That's the ugly patch #8...?

Ah, right it's the randomly (?) chosen gpio pin blocks split thing.

> 
> > From what I saw in the spec, the new byte is there just for Windows.
> > Which in itself is an utter fail on part of the spec. There's no good
> > reason why Windows and Linux should do things differently because that
> > will probably mean putting Linux on some random machine that came with
> > Windows won't work :(
> 
> There's no disagreement here. Ugly specs lead to ugly implementations.
> 
> BR,
> Jani.
> 
> 
> 
> -- 
> Jani Nikula, Intel Open Source Technology Center

-- 
Ville Syrjälä
Intel OTC
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2016-02-04 17:48 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-04 10:50 [PATCH 0/8] drm/i915/dsi: i2c/gpio Jani Nikula
2016-02-04 10:50 ` [PATCH 1/8] drm/i915/dsi: defend gpio table against out of bounds access Jani Nikula
2016-02-04 15:40   ` Ville Syrjälä
2016-02-04 10:50 ` [PATCH 2/8] drm/i915/dsi: don't pass arbitrary data to sideband Jani Nikula
2016-02-04 15:41   ` Ville Syrjälä
2016-02-04 16:56     ` Jani Nikula
2016-02-04 10:50 ` [PATCH 3/8] drm/i915: Adding the parsing logic for the i2c element Jani Nikula
2016-02-04 15:28   ` Ville Syrjälä
2016-02-04 16:21     ` Jani Nikula
2016-02-04 16:36       ` Ville Syrjälä
2016-02-15 16:48         ` Daniel Vetter
2016-02-04 10:50 ` [PATCH 4/8] drm/i915/dsi: skip gpio element execution when not supported Jani Nikula
2016-02-04 15:36   ` Ville Syrjälä
2016-02-04 16:52   ` [PATCH v2] " Jani Nikula
2016-02-04 17:05     ` Ville Syrjälä
2016-02-04 17:10       ` Jani Nikula
2016-02-04 17:12         ` Jani Nikula
2016-02-04 17:18         ` Ville Syrjälä
2016-02-04 17:22           ` Jani Nikula
2016-02-04 17:48             ` Ville Syrjälä [this message]
2016-02-04 17:49     ` Ville Syrjälä
2016-02-04 18:39       ` Jani Nikula
2016-02-04 10:50 ` [PATCH 5/8] drm/i915: put the IOSF port defines in numerical order Jani Nikula
2016-02-04 16:05   ` Ville Syrjälä
2016-02-04 10:50 ` [PATCH 6/8] drm/i915/vlv: drop unused vlv_gps_core_read/write functions Jani Nikula
2016-02-04 16:12   ` Ville Syrjälä
2016-02-04 16:57     ` Jani Nikula
2016-02-04 10:50 ` [PATCH 7/8] drm/i915: Extend gpio read/write to other cores Jani Nikula
2016-02-04 15:39   ` Ville Syrjälä
2016-02-04 16:55   ` [PATCH v5] " Jani Nikula
2016-02-04 17:03     ` Ville Syrjälä
2016-02-04 17:14       ` Jani Nikula
2016-02-04 10:50 ` [PATCH 8/8] drm/i915/dsi: Added the generic gpio sequence support and gpio table Jani Nikula
2016-02-04 17:51   ` Ville Syrjälä
2016-02-04 12:46 ` ✓ Fi.CI.BAT: success for drm/i915/dsi: i2c/gpio Patchwork
2016-02-05  7:31 ` ✗ Fi.CI.BAT: failure for drm/i915/dsi: i2c/gpio (rev3) Patchwork

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=20160204174820.GW23290@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jani.nikula@intel.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;
as well as URLs for NNTP newsgroup(s).