drm/msm: basic KMS driver for snapdragon
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>
2013-06-27 00:44:06 +08:00
|
|
|
|
|
|
|
config DRM_MSM
|
|
|
|
tristate "MSM DRM"
|
|
|
|
depends on DRM
|
2014-01-08 05:55:06 +08:00
|
|
|
depends on MSM_IOMMU
|
2014-01-31 04:45:05 +08:00
|
|
|
depends on ARCH_MSM8960 || (ARM && COMPILE_TEST)
|
drm/msm: basic KMS driver for snapdragon
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>
2013-06-27 00:44:06 +08:00
|
|
|
select DRM_KMS_HELPER
|
|
|
|
select SHMEM
|
|
|
|
select TMPFS
|
|
|
|
default y
|
|
|
|
help
|
|
|
|
DRM/KMS driver for MSM/snapdragon.
|
|
|
|
|
|
|
|
config DRM_MSM_FBDEV
|
|
|
|
bool "Enable legacy fbdev support for MSM modesetting driver"
|
|
|
|
depends on DRM_MSM
|
2013-10-08 23:44:47 +08:00
|
|
|
select DRM_KMS_FB_HELPER
|
drm/msm: basic KMS driver for snapdragon
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>
2013-06-27 00:44:06 +08:00
|
|
|
select FB_SYS_FILLRECT
|
|
|
|
select FB_SYS_COPYAREA
|
|
|
|
select FB_SYS_IMAGEBLIT
|
|
|
|
select FB_SYS_FOPS
|
|
|
|
default y
|
|
|
|
help
|
|
|
|
Choose this option if you have a need for the legacy fbdev
|
|
|
|
support. Note that this support also provide the linux console
|
|
|
|
support on top of the MSM modesetting driver.
|
|
|
|
|
|
|
|
config DRM_MSM_REGISTER_LOGGING
|
|
|
|
bool "MSM DRM register logging"
|
|
|
|
depends on DRM_MSM
|
|
|
|
default n
|
|
|
|
help
|
|
|
|
Compile in support for logging register reads/writes in a format
|
|
|
|
that can be parsed by envytools demsm tool. If enabled, register
|
|
|
|
logging can be switched on via msm.reglog=y module param.
|