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
|
|
|
/*
|
|
|
|
|
* Copyright (C) 2013 Red Hat
|
|
|
|
|
* Author: Rob Clark <robdclark@gmail.com>
|
|
|
|
|
*
|
|
|
|
|
* This program is free software; you can redistribute it and/or modify it
|
|
|
|
|
* under the terms of the GNU General Public License version 2 as published by
|
|
|
|
|
* the Free Software Foundation.
|
|
|
|
|
*
|
|
|
|
|
* This program is distributed in the hope that it will be useful, but WITHOUT
|
|
|
|
|
* ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
|
|
|
|
|
* FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for
|
|
|
|
|
* more details.
|
|
|
|
|
*
|
|
|
|
|
* You should have received a copy of the GNU General Public License along with
|
|
|
|
|
* this program. If not, see <http://www.gnu.org/licenses/>.
|
|
|
|
|
*/
|
|
|
|
|
|
|
|
|
|
#ifndef __MSM_DRV_H__
|
|
|
|
|
#define __MSM_DRV_H__
|
|
|
|
|
|
|
|
|
|
#include <linux/kernel.h>
|
|
|
|
|
#include <linux/clk.h>
|
|
|
|
|
#include <linux/cpufreq.h>
|
|
|
|
|
#include <linux/module.h>
|
2014-03-04 03:19:12 +08:00
|
|
|
#include <linux/component.h>
|
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
|
|
|
#include <linux/platform_device.h>
|
|
|
|
|
#include <linux/pm.h>
|
|
|
|
|
#include <linux/pm_runtime.h>
|
|
|
|
|
#include <linux/slab.h>
|
|
|
|
|
#include <linux/list.h>
|
|
|
|
|
#include <linux/iommu.h>
|
|
|
|
|
#include <linux/types.h>
|
|
|
|
|
#include <asm/sizes.h>
|
|
|
|
|
|
|
|
|
|
#ifndef CONFIG_OF
|
|
|
|
|
#include <mach/board.h>
|
|
|
|
|
#include <mach/socinfo.h>
|
|
|
|
|
#include <mach/iommu_domains.h>
|
|
|
|
|
#endif
|
|
|
|
|
|
|
|
|
|
#include <drm/drmP.h>
|
2014-11-09 02:21:06 +08:00
|
|
|
#include <drm/drm_atomic.h>
|
|
|
|
|
#include <drm/drm_atomic_helper.h>
|
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
|
|
|
#include <drm/drm_crtc_helper.h>
|
2014-11-09 02:21:06 +08:00
|
|
|
#include <drm/drm_plane_helper.h>
|
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
|
|
|
#include <drm/drm_fb_helper.h>
|
2013-07-20 00:59:32 +08:00
|
|
|
#include <drm/msm_drm.h>
|
2014-09-23 21:46:53 +08:00
|
|
|
#include <drm/drm_gem.h>
|
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
|
|
|
|
|
|
|
|
struct msm_kms;
|
2013-07-20 00:59:32 +08:00
|
|
|
struct msm_gpu;
|
2013-11-17 01:56:06 +08:00
|
|
|
struct msm_mmu;
|
2014-05-31 02:47:38 +08:00
|
|
|
struct msm_rd_state;
|
2014-05-31 02:49:43 +08:00
|
|
|
struct msm_perf_state;
|
2014-05-31 02:47:38 +08:00
|
|
|
struct msm_gem_submit;
|
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
|
|
|
|
2013-07-20 00:59:32 +08:00
|
|
|
#define NUM_DOMAINS 2 /* one for KMS, then one per gpu core (?) */
|
|
|
|
|
|
|
|
|
|
struct msm_file_private {
|
|
|
|
|
/* currently we don't do anything useful with this.. but when
|
|
|
|
|
* per-context address spaces are supported we'd keep track of
|
|
|
|
|
* the context's page-tables here.
|
|
|
|
|
*/
|
|
|
|
|
int dummy;
|
|
|
|
|
};
|
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
|
|
|
|
|
|
|
|
struct msm_drm_private {
|
|
|
|
|
|
|
|
|
|
struct msm_kms *kms;
|
|
|
|
|
|
2014-03-04 03:19:12 +08:00
|
|
|
/* subordinate devices, if present: */
|
2014-11-05 02:33:14 +08:00
|
|
|
struct platform_device *gpu_pdev;
|
|
|
|
|
|
|
|
|
|
/* possibly this should be in the kms component, but it is
|
|
|
|
|
* shared by both mdp4 and mdp5..
|
|
|
|
|
*/
|
|
|
|
|
struct hdmi *hdmi;
|
2014-03-04 03:19:12 +08:00
|
|
|
|
2013-07-20 00:59:32 +08:00
|
|
|
/* when we have more than one 'msm_gpu' these need to be an array: */
|
|
|
|
|
struct msm_gpu *gpu;
|
|
|
|
|
struct msm_file_private *lastctx;
|
|
|
|
|
|
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
|
|
|
struct drm_fb_helper *fbdev;
|
|
|
|
|
|
2013-07-20 00:59:32 +08:00
|
|
|
uint32_t next_fence, completed_fence;
|
|
|
|
|
wait_queue_head_t fence_event;
|
|
|
|
|
|
2014-05-31 02:47:38 +08:00
|
|
|
struct msm_rd_state *rd;
|
2014-05-31 02:49:43 +08:00
|
|
|
struct msm_perf_state *perf;
|
2014-05-31 02:47:38 +08:00
|
|
|
|
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
|
|
|
/* list of GEM objects: */
|
|
|
|
|
struct list_head inactive_list;
|
|
|
|
|
|
|
|
|
|
struct workqueue_struct *wq;
|
|
|
|
|
|
2013-09-15 02:01:55 +08:00
|
|
|
/* callbacks deferred until bo is inactive: */
|
|
|
|
|
struct list_head fence_cbs;
|
|
|
|
|
|
2013-11-17 01:56:06 +08:00
|
|
|
/* registered MMUs: */
|
|
|
|
|
unsigned int num_mmus;
|
|
|
|
|
struct msm_mmu *mmus[NUM_DOMAINS];
|
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
|
|
|
|
2013-10-09 00:57:48 +08:00
|
|
|
unsigned int num_planes;
|
|
|
|
|
struct drm_plane *planes[8];
|
|
|
|
|
|
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
|
|
|
unsigned int num_crtcs;
|
|
|
|
|
struct drm_crtc *crtcs[8];
|
|
|
|
|
|
|
|
|
|
unsigned int num_encoders;
|
|
|
|
|
struct drm_encoder *encoders[8];
|
|
|
|
|
|
2013-08-31 01:02:15 +08:00
|
|
|
unsigned int num_bridges;
|
|
|
|
|
struct drm_bridge *bridges[8];
|
|
|
|
|
|
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
|
|
|
unsigned int num_connectors;
|
|
|
|
|
struct drm_connector *connectors[8];
|
2013-11-17 01:56:06 +08:00
|
|
|
|
|
|
|
|
/* VRAM carveout, used when no IOMMU: */
|
|
|
|
|
struct {
|
|
|
|
|
unsigned long size;
|
|
|
|
|
dma_addr_t paddr;
|
|
|
|
|
/* NOTE: mm managed at the page level, size is in # of pages
|
|
|
|
|
* and position mm_node->start is in # of pages:
|
|
|
|
|
*/
|
|
|
|
|
struct drm_mm mm;
|
|
|
|
|
} vram;
|
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
|
|
|
};
|
|
|
|
|
|
|
|
|
|
struct msm_format {
|
|
|
|
|
uint32_t pixel_format;
|
|
|
|
|
};
|
|
|
|
|
|
2013-09-15 02:01:55 +08:00
|
|
|
/* callback from wq once fence has passed: */
|
|
|
|
|
struct msm_fence_cb {
|
|
|
|
|
struct work_struct work;
|
|
|
|
|
uint32_t fence;
|
|
|
|
|
void (*func)(struct msm_fence_cb *cb);
|
|
|
|
|
};
|
|
|
|
|
|
|
|
|
|
void __msm_fence_worker(struct work_struct *work);
|
|
|
|
|
|
|
|
|
|
#define INIT_FENCE_CB(_cb, _func) do { \
|
|
|
|
|
INIT_WORK(&(_cb)->work, __msm_fence_worker); \
|
|
|
|
|
(_cb)->func = _func; \
|
|
|
|
|
} while (0)
|
|
|
|
|
|
2014-11-09 02:21:06 +08:00
|
|
|
int msm_atomic_commit(struct drm_device *dev,
|
|
|
|
|
struct drm_atomic_state *state, bool async);
|
|
|
|
|
|
2013-11-17 01:56:06 +08:00
|
|
|
int msm_register_mmu(struct drm_device *dev, struct msm_mmu *mmu);
|
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
|
|
|
|
2013-07-20 00:59:32 +08:00
|
|
|
int msm_wait_fence_interruptable(struct drm_device *dev, uint32_t fence,
|
|
|
|
|
struct timespec *timeout);
|
2014-11-08 07:10:04 +08:00
|
|
|
int msm_queue_fence_cb(struct drm_device *dev,
|
|
|
|
|
struct msm_fence_cb *cb, uint32_t fence);
|
2013-07-20 00:59:32 +08:00
|
|
|
void msm_update_fence(struct drm_device *dev, uint32_t fence);
|
|
|
|
|
|
|
|
|
|
int msm_ioctl_gem_submit(struct drm_device *dev, void *data,
|
|
|
|
|
struct drm_file *file);
|
|
|
|
|
|
2014-11-12 19:38:14 +08:00
|
|
|
int msm_gem_mmap_obj(struct drm_gem_object *obj,
|
|
|
|
|
struct vm_area_struct *vma);
|
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
|
|
|
int msm_gem_mmap(struct file *filp, struct vm_area_struct *vma);
|
|
|
|
|
int msm_gem_fault(struct vm_area_struct *vma, struct vm_fault *vmf);
|
|
|
|
|
uint64_t msm_gem_mmap_offset(struct drm_gem_object *obj);
|
|
|
|
|
int msm_gem_get_iova_locked(struct drm_gem_object *obj, int id,
|
|
|
|
|
uint32_t *iova);
|
|
|
|
|
int msm_gem_get_iova(struct drm_gem_object *obj, int id, uint32_t *iova);
|
2014-11-08 22:13:37 +08:00
|
|
|
uint32_t msm_gem_iova(struct drm_gem_object *obj, int id);
|
2013-09-28 23:28:35 +08:00
|
|
|
struct page **msm_gem_get_pages(struct drm_gem_object *obj);
|
|
|
|
|
void msm_gem_put_pages(struct drm_gem_object *obj);
|
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
|
|
|
void msm_gem_put_iova(struct drm_gem_object *obj, int id);
|
|
|
|
|
int msm_gem_dumb_create(struct drm_file *file, struct drm_device *dev,
|
|
|
|
|
struct drm_mode_create_dumb *args);
|
|
|
|
|
int msm_gem_dumb_map_offset(struct drm_file *file, struct drm_device *dev,
|
|
|
|
|
uint32_t handle, uint64_t *offset);
|
2013-09-28 23:28:35 +08:00
|
|
|
struct sg_table *msm_gem_prime_get_sg_table(struct drm_gem_object *obj);
|
|
|
|
|
void *msm_gem_prime_vmap(struct drm_gem_object *obj);
|
|
|
|
|
void msm_gem_prime_vunmap(struct drm_gem_object *obj, void *vaddr);
|
2014-11-12 19:38:14 +08:00
|
|
|
int msm_gem_prime_mmap(struct drm_gem_object *obj, struct vm_area_struct *vma);
|
2013-09-28 23:28:35 +08:00
|
|
|
struct drm_gem_object *msm_gem_prime_import_sg_table(struct drm_device *dev,
|
2014-01-09 18:03:14 +08:00
|
|
|
struct dma_buf_attachment *attach, struct sg_table *sg);
|
2013-09-28 23:28:35 +08:00
|
|
|
int msm_gem_prime_pin(struct drm_gem_object *obj);
|
|
|
|
|
void msm_gem_prime_unpin(struct drm_gem_object *obj);
|
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
|
|
|
void *msm_gem_vaddr_locked(struct drm_gem_object *obj);
|
|
|
|
|
void *msm_gem_vaddr(struct drm_gem_object *obj);
|
2013-09-15 02:01:55 +08:00
|
|
|
int msm_gem_queue_inactive_cb(struct drm_gem_object *obj,
|
|
|
|
|
struct msm_fence_cb *cb);
|
2013-07-20 00:59:32 +08:00
|
|
|
void msm_gem_move_to_active(struct drm_gem_object *obj,
|
2013-09-02 01:25:09 +08:00
|
|
|
struct msm_gpu *gpu, bool write, uint32_t fence);
|
2013-07-20 00:59:32 +08:00
|
|
|
void msm_gem_move_to_inactive(struct drm_gem_object *obj);
|
|
|
|
|
int msm_gem_cpu_prep(struct drm_gem_object *obj, uint32_t op,
|
|
|
|
|
struct timespec *timeout);
|
|
|
|
|
int msm_gem_cpu_fini(struct drm_gem_object *obj);
|
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
|
|
|
void msm_gem_free_object(struct drm_gem_object *obj);
|
|
|
|
|
int msm_gem_new_handle(struct drm_device *dev, struct drm_file *file,
|
|
|
|
|
uint32_t size, uint32_t flags, uint32_t *handle);
|
|
|
|
|
struct drm_gem_object *msm_gem_new(struct drm_device *dev,
|
|
|
|
|
uint32_t size, uint32_t flags);
|
2013-09-28 23:28:35 +08:00
|
|
|
struct drm_gem_object *msm_gem_import(struct drm_device *dev,
|
|
|
|
|
uint32_t size, struct sg_table *sgt);
|
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
|
|
|
|
2014-11-08 22:13:37 +08:00
|
|
|
int msm_framebuffer_prepare(struct drm_framebuffer *fb, int id);
|
|
|
|
|
void msm_framebuffer_cleanup(struct drm_framebuffer *fb, int id);
|
|
|
|
|
uint32_t msm_framebuffer_iova(struct drm_framebuffer *fb, int id, int plane);
|
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
|
|
|
struct drm_gem_object *msm_framebuffer_bo(struct drm_framebuffer *fb, int plane);
|
|
|
|
|
const struct msm_format *msm_framebuffer_format(struct drm_framebuffer *fb);
|
|
|
|
|
struct drm_framebuffer *msm_framebuffer_init(struct drm_device *dev,
|
|
|
|
|
struct drm_mode_fb_cmd2 *mode_cmd, struct drm_gem_object **bos);
|
|
|
|
|
struct drm_framebuffer *msm_framebuffer_create(struct drm_device *dev,
|
|
|
|
|
struct drm_file *file, struct drm_mode_fb_cmd2 *mode_cmd);
|
|
|
|
|
|
|
|
|
|
struct drm_fb_helper *msm_fbdev_init(struct drm_device *dev);
|
|
|
|
|
|
2013-12-02 01:12:54 +08:00
|
|
|
struct hdmi;
|
2014-11-05 02:33:14 +08:00
|
|
|
int hdmi_modeset_init(struct hdmi *hdmi, struct drm_device *dev,
|
|
|
|
|
struct drm_encoder *encoder);
|
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
|
|
|
void __init hdmi_register(void);
|
|
|
|
|
void __exit hdmi_unregister(void);
|
|
|
|
|
|
|
|
|
|
#ifdef CONFIG_DEBUG_FS
|
|
|
|
|
void msm_gem_describe(struct drm_gem_object *obj, struct seq_file *m);
|
|
|
|
|
void msm_gem_describe_objects(struct list_head *list, struct seq_file *m);
|
|
|
|
|
void msm_framebuffer_describe(struct drm_framebuffer *fb, struct seq_file *m);
|
2014-05-31 02:47:38 +08:00
|
|
|
int msm_debugfs_late_init(struct drm_device *dev);
|
|
|
|
|
int msm_rd_debugfs_init(struct drm_minor *minor);
|
|
|
|
|
void msm_rd_debugfs_cleanup(struct drm_minor *minor);
|
|
|
|
|
void msm_rd_dump_submit(struct msm_gem_submit *submit);
|
2014-05-31 02:49:43 +08:00
|
|
|
int msm_perf_debugfs_init(struct drm_minor *minor);
|
|
|
|
|
void msm_perf_debugfs_cleanup(struct drm_minor *minor);
|
2014-05-31 02:47:38 +08:00
|
|
|
#else
|
|
|
|
|
static inline int msm_debugfs_late_init(struct drm_device *dev) { return 0; }
|
|
|
|
|
static inline void msm_rd_dump_submit(struct msm_gem_submit *submit) {}
|
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
|
|
|
#endif
|
|
|
|
|
|
|
|
|
|
void __iomem *msm_ioremap(struct platform_device *pdev, const char *name,
|
|
|
|
|
const char *dbgname);
|
|
|
|
|
void msm_writel(u32 data, void __iomem *addr);
|
|
|
|
|
u32 msm_readl(const void __iomem *addr);
|
|
|
|
|
|
|
|
|
|
#define DBG(fmt, ...) DRM_DEBUG(fmt"\n", ##__VA_ARGS__)
|
|
|
|
|
#define VERB(fmt, ...) if (0) DRM_DEBUG(fmt"\n", ##__VA_ARGS__)
|
|
|
|
|
|
2013-09-12 05:34:07 +08:00
|
|
|
static inline bool fence_completed(struct drm_device *dev, uint32_t fence)
|
|
|
|
|
{
|
|
|
|
|
struct msm_drm_private *priv = dev->dev_private;
|
|
|
|
|
return priv->completed_fence >= fence;
|
|
|
|
|
}
|
|
|
|
|
|
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
|
|
|
static inline int align_pitch(int width, int bpp)
|
|
|
|
|
{
|
|
|
|
|
int bytespp = (bpp + 7) / 8;
|
|
|
|
|
/* adreno needs pitch aligned to 32 pixels: */
|
|
|
|
|
return bytespp * ALIGN(width, 32);
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
/* for the generated headers: */
|
|
|
|
|
#define INVALID_IDX(idx) ({BUG(); 0;})
|
2013-07-20 00:59:32 +08:00
|
|
|
#define fui(x) ({BUG(); 0;})
|
|
|
|
|
#define util_float_to_half(x) ({BUG(); 0;})
|
|
|
|
|
|
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
|
|
|
|
|
|
|
|
#define FIELD(val, name) (((val) & name ## __MASK) >> name ## __SHIFT)
|
|
|
|
|
|
|
|
|
|
/* for conditionally setting boolean flag(s): */
|
|
|
|
|
#define COND(bool, val) ((bool) ? (val) : 0)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
#endif /* __MSM_DRV_H__ */
|
