summaryrefslogtreecommitdiffstats
path: root/drivers/char/genrtc.c
diff options
context:
space:
mode:
authorBen Widawsky <ben@bwidawsk.net>2013-01-18 12:30:33 -0800
committerDaniel Vetter <daniel.vetter@ffwll.ch>2013-01-20 13:11:12 +0100
commit8d2e630899165d413ae8a2adc36846ac0b71bada (patch)
treef2df0bedcdedca4a63ecb40402680d6099f40fa3 /drivers/char/genrtc.c
parent9c61a32d31a55c8c6e590d83ae5645e14fde09f2 (diff)
downloadop-kernel-dev-8d2e630899165d413ae8a2adc36846ac0b71bada.zip
op-kernel-dev-8d2e630899165d413ae8a2adc36846ac0b71bada.tar.gz
drm/i915: Needs_dmar, not
The reasoning behind our code taking two paths depending upon whether or not we may have been configured for IOMMU isn't clear to me. It should always be safe to use the pci mapping functions as they are designed to abstract the decision we were handling in i915. Aside from simpler code, removing another member for the intel_gtt struct is a nice motivation. I ran this by Chris, and he wasn't concerned about the extra kzalloc, and memory references vs. page_to_phys calculation in the case without IOMMU. v2: Update commit message v3: Remove needs_dmar addition from Zhenyu upstream This reverts (and then other stuff) commit 20652097dadd9a7fb4d652f25466299974bc78f9 Author: Zhenyu Wang <zhenyuw@linux.intel.com> Date: Thu Dec 13 23:47:47 2012 +0800 drm/i915: Fix missed needs_dmar setting Reviewed-by: Rodrigo Vivi <rodrigo.vivi@gmail.com> (v2) Cc: Zhenyu Wang <zhenyuw@linux.intel.com> Signed-off-by: Ben Widawsky <ben@bwidawsk.net> [danvet: Squash in follow-up fix to remove the bogus hunk which deleted the dma_mask configuration for gen6+.] Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Diffstat (limited to 'drivers/char/genrtc.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud