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-26 23:44:06 +07:00
|
|
|
ccflags-y := -Iinclude/drm -Idrivers/gpu/drm/msm
|
|
|
|
ifeq (, $(findstring -W,$(EXTRA_CFLAGS)))
|
|
|
|
ccflags-y += -Werror
|
|
|
|
endif
|
|
|
|
|
|
|
|
msm-y := \
|
2014-09-06 00:06:37 +07:00
|
|
|
adreno/adreno_device.o \
|
2013-07-19 23:59:32 +07:00
|
|
|
adreno/adreno_gpu.o \
|
|
|
|
adreno/a3xx_gpu.o \
|
2014-09-09 02:40:16 +07:00
|
|
|
adreno/a4xx_gpu.o \
|
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-26 23:44:06 +07:00
|
|
|
hdmi/hdmi.o \
|
2013-12-12 02:44:02 +07:00
|
|
|
hdmi/hdmi_audio.o \
|
2013-08-31 00:02:15 +07:00
|
|
|
hdmi/hdmi_bridge.o \
|
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-26 23:44:06 +07:00
|
|
|
hdmi/hdmi_connector.o \
|
|
|
|
hdmi/hdmi_i2c.o \
|
|
|
|
hdmi/hdmi_phy_8960.o \
|
|
|
|
hdmi/hdmi_phy_8x60.o \
|
2013-12-02 00:12:54 +07:00
|
|
|
hdmi/hdmi_phy_8x74.o \
|
2013-12-01 02:58:23 +07:00
|
|
|
mdp/mdp_format.o \
|
2013-12-01 05:24:22 +07:00
|
|
|
mdp/mdp_kms.o \
|
2013-12-01 00:37:42 +07:00
|
|
|
mdp/mdp4/mdp4_crtc.o \
|
|
|
|
mdp/mdp4/mdp4_dtv_encoder.o \
|
2014-08-02 00:08:11 +07:00
|
|
|
mdp/mdp4/mdp4_lcdc_encoder.o \
|
|
|
|
mdp/mdp4/mdp4_lvds_connector.o \
|
2013-12-01 00:37:42 +07:00
|
|
|
mdp/mdp4/mdp4_irq.o \
|
|
|
|
mdp/mdp4/mdp4_kms.o \
|
|
|
|
mdp/mdp4/mdp4_plane.o \
|
2014-11-19 00:49:48 +07:00
|
|
|
mdp/mdp5/mdp5_cfg.o \
|
2014-11-19 00:49:49 +07:00
|
|
|
mdp/mdp5/mdp5_ctl.o \
|
drm/msm: add mdp5/apq8x74
Add support for the new MDP5 display controller block. The mapping
between parts of the display controller and KMS is:
plane -> PIPE{RGBn,VIGn} \
crtc -> LM (layer mixer) |-> MDP "device"
encoder -> INTF /
connector -> HDMI/DSI/eDP/etc --> other device(s)
Unlike MDP4, it appears we can get by with a single encoder, rather
than needing a different implementation for DTV, DSI, etc. (Ie. the
register interface is same, just different bases.)
Also unlike MDP4, all the IRQs for other blocks (HDMI, DSI, etc) are
routed through MDP.
And finally, MDP5 has this "Shared Memory Pool" (called "SMP"), from
which blocks need to be allocated to the active pipes based on fetch
stride.
Signed-off-by: Rob Clark <robdclark@gmail.com>
2013-12-01 05:51:47 +07:00
|
|
|
mdp/mdp5/mdp5_crtc.o \
|
|
|
|
mdp/mdp5/mdp5_encoder.o \
|
|
|
|
mdp/mdp5/mdp5_irq.o \
|
|
|
|
mdp/mdp5/mdp5_kms.o \
|
|
|
|
mdp/mdp5/mdp5_plane.o \
|
|
|
|
mdp/mdp5/mdp5_smp.o \
|
2014-11-09 01:21:06 +07:00
|
|
|
msm_atomic.o \
|
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-26 23:44:06 +07:00
|
|
|
msm_drv.o \
|
|
|
|
msm_fb.o \
|
2013-07-19 23:59:32 +07:00
|
|
|
msm_gem.o \
|
2013-09-28 22:28:35 +07:00
|
|
|
msm_gem_prime.o \
|
2013-07-19 23:59:32 +07:00
|
|
|
msm_gem_submit.o \
|
|
|
|
msm_gpu.o \
|
2013-11-17 00:56:06 +07:00
|
|
|
msm_iommu.o \
|
2014-05-31 01:49:43 +07:00
|
|
|
msm_perf.o \
|
2014-05-31 01:47:38 +07:00
|
|
|
msm_rd.o \
|
2013-07-19 23:59:32 +07:00
|
|
|
msm_ringbuffer.o
|
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-26 23:44:06 +07:00
|
|
|
|
|
|
|
msm-$(CONFIG_DRM_MSM_FBDEV) += msm_fbdev.o
|
2014-08-02 00:08:11 +07:00
|
|
|
msm-$(CONFIG_COMMON_CLK) += mdp/mdp4/mdp4_lvds_pll.o
|
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-26 23:44:06 +07:00
|
|
|
|
|
|
|
obj-$(CONFIG_DRM_MSM) += msm.o
|