All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Wilson <chris@chris-wilson.co.uk>
To: Simon Farnsworth <simon.farnsworth@onelan.co.uk>,
	Keith Packard <keithp@keithp.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v2] drm/i915: Enable SDVO hotplug interrupts for HDMI and DVI
Date: Tue, 20 Sep 2011 12:27:54 +0100	[thread overview]
Message-ID: <aefc95$1ftmrb@orsmga001.jf.intel.com> (raw)
In-Reply-To: <1316515500-16832-1-git-send-email-simon.farnsworth@onelan.co.uk>

On Tue, 20 Sep 2011 11:45:00 +0100, Simon Farnsworth <simon.farnsworth@onelan.co.uk> wrote:
> I was seeing a nasty 5 frame glitch every 10 seconds, caused by the
> poll for connection on DVI attached by SDVO.
> 
> As my SDVO DVI supports hotplug detect interrupts, the fix is to
> enable them, and hook them in to the various bits of driver
> infrastructure so that they work reliably.
> 
> With lots of help from Adam Jackson <ajax@redhat.com> on IRC.
> 
> Signed-off-by: Simon Farnsworth <simon.farnsworth@onelan.co.uk>
> ---
> Changes from first version:
> 
>  * Don't call intel_sdvo_supports_hotplug twice - pick up the setting
>    in connector->polled instead (suggested by Keith Packard in review).
> 
>  * Change subject prefix to drm/i915
> 
>  drivers/gpu/drm/i915/intel_drv.h  |    3 --
>  drivers/gpu/drm/i915/intel_sdvo.c |   65 ++++++++++++++++---------------------
>  2 files changed, 28 insertions(+), 40 deletions(-)
> 
> diff --git a/drivers/gpu/drm/i915/intel_drv.h b/drivers/gpu/drm/i915/intel_drv.h
> index 7b330e7..94bb596 100644
> --- a/drivers/gpu/drm/i915/intel_drv.h
> +++ b/drivers/gpu/drm/i915/intel_drv.h
> @@ -336,9 +336,6 @@ extern void intel_release_load_detect_pipe(struct intel_encoder *intel_encoder,
>  					   struct drm_connector *connector,
>  					   struct intel_load_detect_pipe *old);
>  
> -extern struct drm_connector* intel_sdvo_find(struct drm_device *dev, int sdvoB);
> -extern int intel_sdvo_supports_hotplug(struct drm_connector *connector);
> -extern void intel_sdvo_set_hotplug(struct drm_connector *connector, int enable);
>  extern void intelfb_restore(void);
>  extern void intel_crtc_fb_gamma_set(struct drm_crtc *crtc, u16 red, u16 green,
>  				    u16 blue, int regno);
> diff --git a/drivers/gpu/drm/i915/intel_sdvo.c b/drivers/gpu/drm/i915/intel_sdvo.c
> index 30fe554..ebce2a5 100644
> --- a/drivers/gpu/drm/i915/intel_sdvo.c
> +++ b/drivers/gpu/drm/i915/intel_sdvo.c
> @@ -1208,74 +1208,55 @@ static bool intel_sdvo_get_capabilities(struct intel_sdvo *intel_sdvo, struct in
>  	return true;
>  }
>  
> -/* No use! */
> -#if 0
> -struct drm_connector* intel_sdvo_find(struct drm_device *dev, int sdvoB)
> +struct drm_connector* intel_sdvo_find_connector(struct intel_sdvo *sdvo)
>  {
>  	struct drm_connector *connector = NULL;
>  	struct intel_sdvo *iout = NULL;
> -	struct intel_sdvo *sdvo;
> +	struct drm_device *dev;
> +
> +	dev = sdvo->base.base.dev;
>  
>  	/* find the sdvo connector */
>  	list_for_each_entry(connector, &dev->mode_config.connector_list, head) {
> -		iout = to_intel_sdvo(connector);
> -
> -		if (iout->type != INTEL_OUTPUT_SDVO)
> -			continue;
> -
> -		sdvo = iout->dev_priv;
> -
> -		if (sdvo->sdvo_reg == SDVOB && sdvoB)
> -			return connector;
> +		iout = intel_attached_sdvo(connector);
>  
> -		if (sdvo->sdvo_reg == SDVOC && !sdvoB)
> +		if (iout == sdvo)

Let's kill iout as it an ugly name and just do
  if (intel_attached_encoder(connector) == &sdvo->base)
     return connector;
instead

>  			return connector;
> -
>  	}
>  
>  	return NULL;
>  }
>  
> -int intel_sdvo_supports_hotplug(struct drm_connector *connector)
> +static int intel_sdvo_supports_hotplug(struct intel_sdvo *intel_sdvo)
>  {
>  	u8 response[2];
> -	u8 status;
> -	struct intel_sdvo *intel_sdvo;
> -	DRM_DEBUG_KMS("\n");
> -
> -	if (!connector)
> -		return 0;
> -
> -	intel_sdvo = to_intel_sdvo(connector);
>  
>  	return intel_sdvo_get_value(intel_sdvo, SDVO_CMD_GET_HOT_PLUG_SUPPORT,
>  				    &response, 2) && response[0];
>  }
>  
> -void intel_sdvo_set_hotplug(struct drm_connector *connector, int on)
> +static void intel_sdvo_set_hotplug(struct intel_sdvo *intel_sdvo)

We don't set here, so perhaps intel_sdvo_enable_hotplug()? And make it
take the connector so that we don't need the trivial function later, we
only incur the extra pointer dance during init.

>  {
>  	u8 response[2];
>  	u8 status;
> -	struct intel_sdvo *intel_sdvo = to_intel_sdvo(connector);
>  
>  	intel_sdvo_write_cmd(intel_sdvo, SDVO_CMD_GET_ACTIVE_HOT_PLUG, NULL, 0);
>  	intel_sdvo_read_response(intel_sdvo, &response, 2);
>  
> -	if (on) {
> -		intel_sdvo_write_cmd(intel_sdvo, SDVO_CMD_GET_HOT_PLUG_SUPPORT, NULL, 0);
> -		status = intel_sdvo_read_response(intel_sdvo, &response, 2);
> +	intel_sdvo_write_cmd(intel_sdvo, SDVO_CMD_GET_HOT_PLUG_SUPPORT, NULL, 0);
> +	status = intel_sdvo_read_response(intel_sdvo, &response, 2);
>  
> -		intel_sdvo_write_cmd(intel_sdvo, SDVO_CMD_SET_ACTIVE_HOT_PLUG, &response, 2);
> -	} else {
> -		response[0] = 0;
> -		response[1] = 0;
> -		intel_sdvo_write_cmd(intel_sdvo, SDVO_CMD_SET_ACTIVE_HOT_PLUG, &response, 2);
> -	}
> +	intel_sdvo_write_cmd(intel_sdvo, SDVO_CMD_SET_ACTIVE_HOT_PLUG, &response, 2);
>  
>  	intel_sdvo_write_cmd(intel_sdvo, SDVO_CMD_GET_ACTIVE_HOT_PLUG, NULL, 0);
>  	intel_sdvo_read_response(intel_sdvo, &response, 2);
>  }
> -#endif
> +
> +void intel_sdvo_do_hotplug(struct intel_encoder *encoder)

Should be static, but anyways I'd recommend just skipping this helper.

Couldn't spot anything wrong with the logic, so just style nitpicking.
I'll have to fix the Ubuntu snafu that's preventing my one machine with
a hotpluggable SDVO device from booting before I can test. Also need to
find someone with the SDVO specs to see if there are any known caveats. :|
-Chris

-- 
Chris Wilson, Intel Open Source Technology Centre

  reply	other threads:[~2011-09-20 11:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-20 10:45 [PATCH v2] drm/i915: Enable SDVO hotplug interrupts for HDMI and DVI Simon Farnsworth
2011-09-20 11:27 ` Chris Wilson [this message]
2011-09-20 12:46   ` Simon Farnsworth

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='aefc95$1ftmrb@orsmga001.jf.intel.com' \
    --to=chris@chris-wilson.co.uk \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=keithp@keithp.com \
    --cc=simon.farnsworth@onelan.co.uk \
    /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.