summaryrefslogtreecommitdiffstats
path: root/drivers/gpu/drm/msm/msm_drv.c
Commit message (Collapse)AuthorAgeFilesLines
* WIP: finally turn all interfaces aroundmsm-rebase-masterLucas Stach2013-09-171-59/+10
| | | | Signed-off-by: Lucas Stach <l.stach@pengutronix.de>
* WIP: decouple adreno gpu accessors from msm codeLucas Stach2013-09-171-1/+1
| | | | Signed-off-by: Lucas Stach <l.stach@pengutronix.de>
* WIP: push down hangcheck into adreno_gpuLucas Stach2013-09-171-1/+1
| | | | Signed-off-by: Lucas Stach <l.stach@pengutronix.de>
* WIP: indirect gpu retire through GEM callbackLucas Stach2013-09-171-1/+9
| | | | Signed-off-by: Lucas Stach <l.stach@pengutronix.de>
* WIP: fetch gpu name from base structLucas Stach2013-09-171-2/+2
| | | | Signed-off-by: Lucas Stach <l.stach@pengutronix.de>
* WIP: prune msm_gpu from adreno interfacesLucas Stach2013-09-171-7/+7
| | | | Signed-off-by: Lucas Stach <l.stach@pengutronix.de>
* WIP: adreno: don't call direcly into msm gem function, but use interfaceLucas Stach2013-09-171-1/+50
| | | | Signed-off-by: Lucas Stach <l.stach@pengutronix.de>
* WIP: track adreno context per gpu and independant of drm driverLucas Stach2013-09-171-11/+6
| | | | Signed-off-by: Lucas Stach <l.stach@pengutronix.de>
* drm/msm: add a3xx gpu supportRob Clark2013-08-241-1/+245
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Add initial support for a3xx 3d core. So far, with hardware that I've seen to date, we can have: + zero, one, or two z180 2d cores + a3xx or a2xx 3d core, which share a common CP (the firmware for the CP seems to implement some different PM4 packet types but the basics of cmdstream submission are the same) Which means that the eventual complete "class" hierarchy, once support for all past and present hw is in place, becomes: + msm_gpu + adreno_gpu + a3xx_gpu + a2xx_gpu + z180_gpu This commit splits out the parts that will eventually be common between a2xx/a3xx into adreno_gpu, and the parts that are even common to z180 into msm_gpu. Note that there is no cmdstream validation required. All memory access from the GPU is via IOMMU/MMU. So as long as you don't map silly things to the GPU, there isn't much damage that the GPU can do. Signed-off-by: Rob Clark <robdclark@gmail.com>
* drm/msm: basic KMS driver for snapdragonRob Clark2013-08-241-0/+532
The snapdragon chips have multiple different display controllers, depending on which chip variant/version. (As far as I can tell, current devices have either MDP3 or MDP4, and upcoming devices have MDSS.) And then external to the display controller are HDMI, DSI, etc. blocks which may be shared across devices which have different display controller blocks. To more easily add support for different display controller blocks, the display controller specific bits are split out into a "kms" module, which provides the kms plane/crtc/encoder objects. The external HDMI, DSI, etc. blocks are part encoder, and part connector currently. But I think I will pull in the drm_bridge patches from chromeos tree, and split them into a bridge+connector, with the registers that need to be set in modeset handled by the bridge. This would remove the 'msm_connector' base class. But some things need to be double checked to make sure I could get the correct ON/OFF sequencing.. This patch adds support for mdp4 crtc (including hw cursor), dtv encoder (part of MDP4 block), and hdmi. Signed-off-by: Rob Clark <robdclark@gmail.com>