diff options
| author | Chris Wilson <chris@chris-wilson.co.uk> | 2013-10-13 12:56:31 +0100 |
|---|---|---|
| committer | Daniel Vetter <daniel.vetter@ffwll.ch> | 2013-10-14 10:02:36 +0200 |
| commit | 540b5d02766863c561afe9f9d56ce0425022a731 (patch) | |
| tree | 5793a09cf473595f4f759b8d63b1bbff46aa0ba5 /drivers/gpu/drm/i915/intel_opregion.c | |
| parent | 391f75e2bf13f105d9e4a120736ccdd8e3bc638b (diff) | |
| download | linux-stable-540b5d02766863c561afe9f9d56ce0425022a731.tar.gz linux-stable-540b5d02766863c561afe9f9d56ce0425022a731.tar.bz2 linux-stable-540b5d02766863c561afe9f9d56ce0425022a731.zip | |
drm/i915: Add breadcrumbs for why the backlight is being set
At the moment we have 3 paths that lead to actually_set_backlight(),
from modesetting, ACPI/OpRegion requests and our very own
intel_backlight interface, and we have no way of distinguishing them in
the debug log. So add a debug breadcrumb to explain the source of the
backlight changes.
Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Diffstat (limited to 'drivers/gpu/drm/i915/intel_opregion.c')
| -rw-r--r-- | drivers/gpu/drm/i915/intel_opregion.c | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/drivers/gpu/drm/i915/intel_opregion.c b/drivers/gpu/drm/i915/intel_opregion.c index 904464023c8f..b82050c96f3e 100644 --- a/drivers/gpu/drm/i915/intel_opregion.c +++ b/drivers/gpu/drm/i915/intel_opregion.c @@ -407,6 +407,7 @@ static u32 asle_set_backlight(struct drm_device *dev, u32 bclp) if (bclp > 255) return ASLC_BACKLIGHT_FAILED; + DRM_DEBUG_KMS("updating opregion backlight %d/255\n", bclp); intel_panel_set_backlight(dev, bclp, 255); iowrite32(DIV_ROUND_UP(bclp * 100, 255) | ASLE_CBLV_VALID, &asle->cblv); |