From: Dave Airlie <airlied@gmail.com>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: DRI Development <dri-devel@lists.freedesktop.org>
Subject: Re: [PATCH] drm/crtc-helper: don't disable disconnected outputs
Date: Tue, 25 Jun 2013 11:09:44 +1000 [thread overview]
Message-ID: <CAPM=9tyLiOJQaCLN3OGedsONtTrP98i_k6PEKrJRKZ9MP90yMA@mail.gmail.com> (raw)
In-Reply-To: <1371328919-16967-1-git-send-email-daniel.vetter@ffwll.ch>
On Sun, Jun 16, 2013 at 6:41 AM, Daniel Vetter <daniel.vetter@ffwll.ch> wrote:
> This has originally been added in
>
> commit a3a0544b2c84e1d7a2022b558ecf66d8c6a8dd93
> Author: Dave Airlie <airlied@redhat.com>
> Date: Mon Aug 31 15:16:30 2009 +1000
>
> drm/kms: add explicit encoder disable function and detach harder.
>
> I think it's the wrong thing to do for a few reasons:
> - It's policy in the kernel. Userspace gets hotplug events when an
> output disconnects, and it can inquire about all the routing that is
> already set up. If userspace wants to disable a disconnected output
> it can simply do so itself.
> - The reason for adding it given in the commit message was to improve
> use of shared encoders. But the disable_unused_functions call only
> happens after the modeset has been completed, so it won't help too
> much in making the modest succeed.
> - We (at least in drm/i915, but iirc all other drivers work the same)
> ensure that if the user accidentally yanks the cable and then
> replugs, the same configuration will keep on working without any
> userspace actions required. For most outputs that's the case by
> default, and DP can have the same semantics with a simple re-train
> handler fired off from the hpd replug event. This breaks it since if
> the user is unlucky and hits the mouse, resulting in a panning of
> e.g. the integrated panel that modeset might kill the accidentally
> yanked output. Which isn't too great.
>
> i915 has applied this behaviour change as part of the bit modeset
> review, thus far without resulting in an angry crowd with pitchforks:
>
The reason is that i915 hardware is nearly impossible to ever set
something up that could trigger this on. You don't have
shared encoders in places that could affect this from what I can see.
I know this will break the radeon card I have that I wrote this for
originally, where if you alternate hotplugging a tv-out
and vga that share the same encoder it won't work. I can probably drag
that card out of whatever hole if fell into,
but the given justifications have give me no confidence that this
patch just isn't reverting the original commit without
fixing anything else.
I suspect I was testing hotplugging at fbcon not using X also.
Dave.
next prev parent reply other threads:[~2013-06-25 1:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-14 22:13 [PATCH 0/6] fb refcount and crtc helper patches Daniel Vetter
2013-06-14 22:13 ` [PATCH 1/6] drm/crtc-helpers: Enforce sane set_config api Daniel Vetter
2013-06-14 22:13 ` [PATCH 2/6] drm/crtc-helper: no need to check for fb->depth/bpp Daniel Vetter
2013-06-14 22:13 ` [PATCH 3/6] drm/crtc-helper: explicit DPMS on after modeset Daniel Vetter
2013-06-15 20:41 ` [PATCH] " Daniel Vetter
2013-06-14 22:13 ` [PATCH 4/6] drm/crtc-helper: don't disable disconnected outputs Daniel Vetter
2013-06-15 20:41 ` [PATCH] " Daniel Vetter
2013-06-25 1:09 ` Dave Airlie [this message]
2013-06-25 9:29 ` Daniel Vetter
2013-06-14 22:13 ` [PATCH 5/6] drm: check that ->set_config properly updates the fb Daniel Vetter
2013-06-14 22:13 ` [PATCH 6/6] drm: fix fb leak in setcrtc 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='CAPM=9tyLiOJQaCLN3OGedsONtTrP98i_k6PEKrJRKZ9MP90yMA@mail.gmail.com' \
--to=airlied@gmail.com \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@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;
as well as URLs for NNTP newsgroup(s).