From: Daniel Vetter <daniel@ffwll.ch>
To: Chris Wilson <chris@chris-wilson.co.uk>,
Daniel Vetter <daniel@ffwll.ch>,
intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Avoid fluctuating to UNKNOWN connector status during forced probes
Date: Mon, 22 Jun 2015 14:12:31 +0200 [thread overview]
Message-ID: <20150622121231.GS25769@phenom.ffwll.local> (raw)
In-Reply-To: <20150619132159.GN14386@nuc-i3427.alporthouse.com>
On Fri, Jun 19, 2015 at 02:21:59PM +0100, Chris Wilson wrote:
> > Maybe we instead need a drm helper module option to clamp unknown
> > uncondiotionally to disconnected to allow users to hack around silly
> > userspace?
>
> We have userspace that respects unknown, after it is what the fb_helper
> was copied from. Unknown is unknown, userspace can either treat it as
> potentially connector or potentially disconnected depending on best that
> suites its purposes. So I don't think a global change is sensible.
Well you implement some kind of clamping in i915 drivers. My stance is
that no matter what exact kind of clamping we agree on it should be
implemented in shared code in the probe helpers. And we already have quite
a bit of unknown duct-taping going on in the probe helpers, but it seems
to not be enough. And tbh I'm not sure what more we need short of just
clamping unknown in general.
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-06-22 12:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-04 15:26 [PATCH] drm/i915: Avoid fluctuating to UNKNOWN connector status during forced probes Chris Wilson
2015-06-04 16:28 ` Ville Syrjälä
2015-06-04 20:23 ` Chris Wilson
2015-06-05 7:46 ` Chris Wilson
2015-06-05 20:37 ` shuang.he
2015-06-15 12:29 ` Daniel Vetter
2015-06-15 12:35 ` Chris Wilson
2015-06-15 13:03 ` Daniel Vetter
2015-06-15 13:37 ` Chris Wilson
2015-06-15 15:18 ` Daniel Vetter
2015-06-19 13:21 ` Chris Wilson
2015-06-22 12:12 ` Daniel Vetter [this message]
2015-06-05 11:10 ` shuang.he
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=20150622121231.GS25769@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=chris@chris-wilson.co.uk \
--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