#ifndef _ACI_H_ #define _ACI_H_ #define ACI_REG_COMMAND 0 /* write register offset */ #define ACI_REG_STATUS 1 /* read register offset */ #define ACI_REG_BUSY 2 /* busy register offset */ #define ACI_REG_RDS 2 /* PCM20: RDS register offset */ #define ACI_MINTIME 500 /* ACI time out limit */ #define ACI_SET_MUTE 0x0d #define ACI_SET_POWERAMP 0x0f #define ACI_SET_TUNERMUTE 0xa3 #define ACI_SET_TUNERMONO 0xa4 #define ACI_SET_IDE 0xd0 #define ACI_SET_WSS 0xd1 #define ACI_SET_SOLOMODE 0xd2 #define ACI_SET_PREAMP 0x03 #define ACI_GET_PREAMP 0x21 #define ACI_WRITE_TUNE 0xa7 #define ACI_READ_TUNERSTEREO 0xa8 #define ACI_READ_TUNERSTATION 0xa9 #define ACI_READ_VERSION 0xf1 #define ACI_READ_IDCODE 0xf2 #define ACI_INIT 0xff #define ACI_STATUS 0xf0 #define ACI_S_GENERAL 0x00 #define ACI_ERROR_OP 0xdf /* ACI Mixer */ /* These are the values for the right channel GET registers. Add an offset of 0x01 for the left channel register. (left=right+0x01) */ #define ACI_GET_MASTER 0x03 #define ACI_GET_MIC 0x05 #define ACI_GET_LINE 0x07 #define ACI_GET_CD 0x09 #define ACI_GET_SYNTH 0x0b #define ACI_GET_PCM 0x0d #define ACI_GET_LINE1 0x10 /* Radio on PCM20 */ #define ACI_GET_LINE2 0x12 #define ACI_GET_EQ1 0x22 /* from Bass ... */ #define ACI_GET_EQ2 0x24 #define ACI_GET_EQ3 0x26 #define ACI_GET_EQ4 0x28 #define ACI_GET_EQ5 0x2a #define ACI_GET_EQ6 0x2c #define ACI_GET_EQ7 0x2e /* ... to Treble */ /* And these are the values for the right channel SET registers. For left channel access you have to add an offset of 0x08. MASTER is an exception, which needs an offset of 0x01 */ #define ACI_SET_MASTER 0x00 #define ACI_SET_MIC 0x30 #define ACI_SET_LINE 0x31 #define ACI_SET_CD 0x34 #define ACI_SET_SYNTH 0x33 #define ACI_SET_PCM 0x32 #define ACI_SET_LINE1 0x35 /* Radio on PCM20 */ #define ACI_SET_LINE2 0x36 #define ACI_SET_EQ1 0x40 /* from Bass ... */ #define ACI_SET_EQ2 0x41 #define ACI_SET_EQ3 0x42 #define ACI_SET_EQ4 0x43 #define ACI_SET_EQ5 0x44 #define ACI_SET_EQ6 0x45 #define ACI_SET_EQ7 0x46 /* ... to Treble */ struct snd_miro_aci { unsigned long aci_port; int aci_vendor; int aci_product; int aci_version; int aci_amp; int aci_preamp; int aci_solomode; struct mutex aci_mutex; }; int snd_aci_cmd(struct snd_miro_aci *aci, int write1, int write2, int write3); struct snd_miro_aci *snd_aci_get_aci(void); #endif /* _ACI_H_ */
path: root/include/uapi/rdma/hfi/Kbuild
diff options
context:
space:
mode:
authorLinus Torvalds <torvalds@linux-foundation.org>2017-01-29 13:50:06 -0800
committerLinus Torvalds <torvalds@linux-foundation.org>2017-01-29 13:50:06 -0800
commit39cb2c9a316e77f6dfba96c543e55b6672d5a37e (patch)
tree98fe974ee4e20121253de7f61fc8d01bdb3821c1 /include/uapi/rdma/hfi/Kbuild
parent2c5d9555d6d937966d79d4c6529a5f7b9206e405 (diff)
drm/i915: Check for NULL i915_vma in intel_unpin_fb_obj()
I've seen this trigger twice now, where the i915_gem_object_to_ggtt() call in intel_unpin_fb_obj() returns NULL, resulting in an oops immediately afterwards as the (inlined) call to i915_vma_unpin_fence() tries to dereference it. It seems to be some race condition where the object is going away at shutdown time, since both times happened when shutting down the X server. The call chains were different: - VT ioctl(KDSETMODE, KD_TEXT): intel_cleanup_plane_fb+0x5b/0xa0 [i915] drm_atomic_helper_cleanup_planes+0x6f/0x90 [drm_kms_helper] intel_atomic_commit_tail+0x749/0xfe0 [i915] intel_atomic_commit+0x3cb/0x4f0 [i915] drm_atomic_commit+0x4b/0x50 [drm] restore_fbdev_mode+0x14c/0x2a0 [drm_kms_helper] drm_fb_helper_restore_fbdev_mode_unlocked+0x34/0x80 [drm_kms_helper] drm_fb_helper_set_par+0x2d/0x60 [drm_kms_helper] intel_fbdev_set_par+0x18/0x70 [i915] fb_set_var+0x236/0x460 fbcon_blank+0x30f/0x350 do_unblank_screen+0xd2/0x1a0 vt_ioctl+0x507/0x12a0 tty_ioctl+0x355/0xc30 do_vfs_ioctl+0xa3/0x5e0 SyS_ioctl+0x79/0x90 entry_SYSCALL_64_fastpath+0x13/0x94 - i915 unpin_work workqueue: intel_unpin_work_fn+0x58/0x140 [i915] process_one_work+0x1f1/0x480 worker_thread+0x48/0x4d0 kthread+0x101/0x140 and this patch purely papers over the issue by adding a NULL pointer check and a WARN_ON_ONCE() to avoid the oops that would then generally make the machine unresponsive. Other callers of i915_gem_object_to_ggtt() seem to also check for the returned pointer being NULL and warn about it, so this clearly has happened before in other places. [ Reported it originally to the i915 developers on Jan 8, applying the ugly workaround on my own now after triggering the problem for the second time with no feedback. This is likely to be the same bug reported as https://bugs.freedesktop.org/show_bug.cgi?id=98829 https://bugs.freedesktop.org/show_bug.cgi?id=99134 which has a patch for the underlying problem, but it hasn't gotten to me, so I'm applying the workaround. ] Cc: Daniel Vetter <daniel.vetter@intel.com> Cc: Jani Nikula <jani.nikula@linux.intel.com> Cc: Ville Syrjälä <ville.syrjala@linux.intel.com> Cc: Chris Wilson <chris@chris-wilson.co.uk> Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com> Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com> Cc: Imre Deak <imre.deak@intel.com> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'include/uapi/rdma/hfi/Kbuild')