#ifndef __DTS_MARVELL_PXA1928_CLOCK_H
#define __DTS_MARVELL_PXA1928_CLOCK_H
/*
* Clock ID values here correspond to the control register offset/4.
*/
/* apb peripherals */
#define PXA1928_CLK_RTC 0x00
#define PXA1928_CLK_TWSI0 0x01
#define PXA1928_CLK_TWSI1 0x02
#define PXA1928_CLK_TWSI2 0x03
#define PXA1928_CLK_TWSI3 0x04
#define PXA1928_CLK_OWIRE 0x05
#define PXA1928_CLK_KPC 0x06
#define PXA1928_CLK_TB_ROTARY 0x07
#define PXA1928_CLK_SW_JTAG 0x08
#define PXA1928_CLK_TIMER1 0x09
#define PXA1928_CLK_UART0 0x0b
#define PXA1928_CLK_UART1 0x0c
#define PXA1928_CLK_UART2 0x0d
#define PXA1928_CLK_GPIO 0x0e
#define PXA1928_CLK_PWM0 0x0f
#define PXA1928_CLK_PWM1 0x10
#define PXA1928_CLK_PWM2 0x11
#define PXA1928_CLK_PWM3 0x12
#define PXA1928_CLK_SSP0 0x13
#define PXA1928_CLK_SSP1 0x14
#define PXA1928_CLK_SSP2 0x15
#define PXA1928_CLK_TWSI4 0x1f
#define PXA1928_CLK_TWSI5 0x20
#define PXA1928_CLK_UART3 0x22
#define PXA1928_CLK_THSENS_GLOB 0x24
#define PXA1928_CLK_THSENS_CPU 0x26
#define PXA1928_CLK_THSENS_VPU 0x27
#define PXA1928_CLK_THSENS_GC 0x28
#define PXA1928_APBC_NR_CLKS 0x30
/* axi peripherals */
#define PXA1928_CLK_SDH0 0x15
#define PXA1928_CLK_SDH1 0x16
#define PXA1928_CLK_USB 0x17
#define PXA1928_CLK_NAND 0x18
#define PXA1928_CLK_DMA 0x19
#define PXA1928_CLK_SDH2 0x3a
#define PXA1928_CLK_SDH3 0x3b
#define PXA1928_CLK_HSIC 0x3e
#define PXA1928_CLK_SDH4 0x57
#define PXA1928_CLK_GC3D 0x5d
#define PXA1928_CLK_GC2D 0x5f
#define PXA1928_APMU_NR_CLKS 0x60
#endif
t.cgi/linux/net-next.git/'>summaryrefslogtreecommitdiff
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>