From: Thomas Hellstrom <thomas@shipmail.org>
To: Thomas Hellstrom <thellstrom@vmware.com>
Cc: airlied@redhat.com, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH][next] drm/vmwgfx: Let SVGA_REG_NUM_DISPLAYS decide output connectivity
Date: Mon, 20 Dec 2010 12:55:23 +0100 [thread overview]
Message-ID: <4D0F442B.5050902@shipmail.org> (raw)
In-Reply-To: <1292509344-4165-1-git-send-email-thellstrom@vmware.com>
Dave,
Please don't apply this patch. We're looking at another solution.
/Thomas
On 12/16/2010 03:22 PM, Thomas Hellstrom wrote:
> Makes the user able to determine the number of connected outputs from
> the VMware GUI.
>
> Signed-off-by: Thomas Hellstrom<thellstrom@vmware.com>
> ---
> drivers/gpu/drm/vmwgfx/vmwgfx_ldu.c | 13 ++++++++++---
> 1 files changed, 10 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/gpu/drm/vmwgfx/vmwgfx_ldu.c b/drivers/gpu/drm/vmwgfx/vmwgfx_ldu.c
> index 29113c9..335c91c 100644
> --- a/drivers/gpu/drm/vmwgfx/vmwgfx_ldu.c
> +++ b/drivers/gpu/drm/vmwgfx/vmwgfx_ldu.c
> @@ -340,9 +340,16 @@ static enum drm_connector_status
> vmw_ldu_connector_detect(struct drm_connector *connector,
> bool force)
> {
> - if (vmw_connector_to_ldu(connector)->pref_active)
> - return connector_status_connected;
> - return connector_status_disconnected;
> + uint32_t num_displays;
> + struct drm_device *dev = connector->dev;
> + struct vmw_private *dev_priv = vmw_priv(dev);
> +
> + mutex_lock(&dev_priv->hw_mutex);
> + num_displays = vmw_read(dev_priv, SVGA_REG_NUM_DISPLAYS);
> + mutex_unlock(&dev_priv->hw_mutex);
> +
> + return ((vmw_connector_to_ldu(connector)->base.unit< num_displays) ?
> + connector_status_connected : connector_status_disconnected);
> }
>
> static struct drm_display_mode vmw_ldu_connector_builtin[] = {
>
prev parent reply other threads:[~2010-12-20 11:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-16 14:22 [PATCH][next] drm/vmwgfx: Let SVGA_REG_NUM_DISPLAYS decide output connectivity Thomas Hellstrom
2010-12-20 11:55 ` Thomas Hellstrom [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=4D0F442B.5050902@shipmail.org \
--to=thomas@shipmail.org \
--cc=airlied@redhat.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=thellstrom@vmware.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