From: Daniel Vetter <daniel@ffwll.ch>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 1/2] drm/i915: make backlight functions take a connector v3
Date: Fri, 11 Oct 2013 23:31:10 +0200 [thread overview]
Message-ID: <20131011213110.GJ8303@phenom.ffwll.local> (raw)
In-Reply-To: <1381516314-6007-1-git-send-email-jbarnes@virtuousgeek.org>
On Fri, Oct 11, 2013 at 11:31:53AM -0700, Jesse Barnes wrote:
[snip]
> static int intel_panel_get_brightness(struct backlight_device *bd)
> {
> - struct drm_device *dev = bl_get_data(bd);
> - return intel_panel_get_backlight(dev);
> + struct intel_connector *connector = bl_get_data(bd);
> + struct drm_device *dev = connector->base.dev;
> + enum pipe pipe;
> + int ret = 0;
> +
> + mutex_lock(&dev->mode_config.mutex);
> + pipe = intel_get_pipe_from_connector(connector);
> + mutex_unlock(&dev->mode_config.mutex);
> + if (pipe == INVALID_PIPE) {
> + ret = 0;
> + goto out_unlock;
> + }
> +
> + ret = intel_panel_get_backlight(connector->base.dev, pipe);
> +out_unlock:
> + mutex_unlock(&dev->mode_config.mutex);
I see mutex_unlock(&dev->mode_config.mutex) twice here. I think you've
just volunteered yourselve for some testcases ;-)
Ideas:
- Make sure all lvds/edp connectors are enabled and bash on all backlight
interfaces (with igt_fork it's easy to do that concurrently).
- Race the above with output changes: dpms on/off and changing the crtc
around.
- Race the above with system suspend for bonus points (can be completely
stitched together from igt helpers).
Cheers, Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
next prev parent reply other threads:[~2013-10-11 21:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-11 18:31 [PATCH 1/2] drm/i915: make backlight functions take a connector v3 Jesse Barnes
2013-10-11 18:31 ` [PATCH 2/2] drm/i915/vlv: use per-pipe backlight controls v2 Jesse Barnes
2013-10-11 21:31 ` Daniel Vetter [this message]
2013-10-11 21:34 ` [PATCH 1/2] drm/i915: make backlight functions take a connector v3 Jesse Barnes
2013-10-11 23:19 ` Jesse Barnes
2013-10-11 23:55 ` Daniel Vetter
2013-10-12 0:06 ` Daniel Vetter
[not found] ` <22791_1381536398_5258928E_22791_19022_1_CAKMK7uGtNCujq7PEoyJzke6w=y2qcsopa4mvSCLsiWtf72z7AA@mail.gmail.com>
2013-10-13 19:54 ` intel-drm-nightly broken on 835GM Thomas Richter
2013-10-14 8:23 ` [PATCH 1/2] drm/i915: make backlight functions take a connector v3 Daniel Vetter
2013-10-11 21:46 ` [PATCH] drm/i915: make backlight functions take a connector v4 Jesse Barnes
2013-10-11 22:44 ` Jesse Barnes
2013-10-14 18:03 ` [PATCH] drm/i915: make backlight functions take a connector v5 Jesse Barnes
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=20131011213110.GJ8303@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jbarnes@virtuousgeek.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