[Intel-gfx] [PATCH v2 5/5] drm/i915/opregion: update cadl based on actually active outputs

[kbuild test robot]

Hi,

[auto build test WARNING on drm-intel/for-linux-next]
[also build test WARNING on next-20160609]
[cannot apply to v4.7-rc3]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]

url:    https://github.com/0day-ci/linux/commits/Jani-Nikula/drm-i915-opregion-proper-handling-of-DIDL-and-CADL/20160613-173347
base:   git://anongit.freedesktop.org/drm-intel for-linux-next
config: x86_64-rhel (attached as .config)
compiler: gcc-4.9 (Debian 4.9.3-14) 4.9.3
reproduce:
        # save the attached .config to linux build tree
        make ARCH=x86_64 

All warnings (new ones prefixed by >>):

   drivers/gpu/drm/i915/intel_display.c: In function 'intel_atomic_commit':
>> drivers/gpu/drm/i915/intel_display.c:13836:29: warning: passing argument 1 of 'intel_opregion_update_cadl' from incompatible pointer type
     intel_opregion_update_cadl(dev);
                                ^
   In file included from drivers/gpu/drm/i915/intel_drv.h:32:0,
                    from drivers/gpu/drm/i915/intel_display.c:36:
   drivers/gpu/drm/i915/i915_drv.h:3666:13: note: expected 'struct drm_i915_private *' but argument is of type 'struct drm_device *'
    extern void intel_opregion_update_cadl(struct drm_i915_private *dev_priv);
                ^

vim +/intel_opregion_update_cadl +13836 drivers/gpu/drm/i915/intel_display.c

 13820	
 13821			if (put_domains[i])
 13822				modeset_put_power_domains(dev_priv, put_domains[i]);
 13823	
 13824			intel_modeset_verify_crtc(crtc, old_crtc_state, crtc->state);
 13825		}
 13826	
 13827		if (intel_state->modeset)
 13828			intel_display_power_put(dev_priv, POWER_DOMAIN_MODESET);
 13829	
 13830		mutex_lock(&dev->struct_mutex);
 13831		drm_atomic_helper_cleanup_planes(dev, state);
 13832		mutex_unlock(&dev->struct_mutex);
 13833	
 13834		drm_atomic_state_free(state);
 13835	
 13836		intel_opregion_update_cadl(dev);
 13837	
 13838		/* As one of the primary mmio accessors, KMS has a high likelihood
 13839		 * of triggering bugs in unclaimed access. After we finish
 13840		 * modesetting, see if an error has been flagged, and if so
 13841		 * enable debugging for the next modeset - and hope we catch
 13842		 * the culprit.
 13843		 *
 13844		 * XXX note that we assume display power is on at this point.

---
0-DAY kernel test infrastructure                Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all                   Intel Corporation
-------------- next part --------------
A non-text attachment was scrubbed...
Name: .config.gz
Type: application/octet-stream
Size: 37214 bytes
Desc: not available
URL: <https://lists.freedesktop.org/archives/intel-gfx/attachments/20160613/06b973a6/attachment-0001.obj>