summaryrefslogtreecommitdiff
path: root/drivers/staging/omapdrm/omap_priv.h
diff options
context:
space:
mode:
authorAndy Gross <andy.gross@ti.com>2011-12-05 19:19:21 -0600
committerGreg Kroah-Hartman <gregkh@suse.de>2011-12-08 15:03:54 -0800
commit71e8831f6407542afd1d8888d3cca13e677034ef (patch)
tree15e531b52349d81137b796b3ba8e292f2a195439 /drivers/staging/omapdrm/omap_priv.h
parente0134715aa136088c649d0d2f833710c7c9e28b0 (diff)
drm/omap: DMM/TILER support for OMAP4+ platform
Dynamic Memory Manager (DMM) is a hardware block in the OMAP4+ processor that contains at least one TILER instance. TILER, or Tiling and Isometric Lightweight Engine for Rotation, provides IOMMU capabilities through the use of a physical address translation table. The TILER also provides zero cost rotation and mirroring. The TILER provides both 1D and 2D access by providing different views or address ranges that can be used to access the physical memory that has been mapped in through the PAT. Access to the 1D view results in linear access to the underlying memory. Access to the 2D views result in tiled access to the underlying memory resulted in increased efficiency. The TILER address space is managed by a tiler container manager (TCM) and allocates the address space through the use of the Simple Tiler Allocation algorithm (SiTA). The purpose of the algorithm is to keep fragmentation of the address space as low as possible. Signed-off-by: Andy Gross <andy.gross@ti.com> Signed-off-by: Rob Clark <rob@ti.com> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
Diffstat (limited to 'drivers/staging/omapdrm/omap_priv.h')
-rw-r--r--drivers/staging/omapdrm/omap_priv.h7
1 files changed, 6 insertions, 1 deletions
diff --git a/drivers/staging/omapdrm/omap_priv.h b/drivers/staging/omapdrm/omap_priv.h
index f482d1edb060..c324709aa9a1 100644
--- a/drivers/staging/omapdrm/omap_priv.h
+++ b/drivers/staging/omapdrm/omap_priv.h
@@ -30,7 +30,7 @@
* detected devices. This should be a good default behavior for most cases,
* but yet there still might be times when you wish to do something different.
*/
-struct omap_drm_platform_data {
+struct omap_kms_platform_data {
int ovl_cnt;
const int *ovl_ids;
int mgr_cnt;
@@ -39,4 +39,9 @@ struct omap_drm_platform_data {
const char **dev_names;
};
+struct omap_drm_platform_data {
+ struct omap_kms_platform_data *kms_pdata;
+ struct omap_dmm_platform_data *dmm_pdata;
+};
+
#endif /* __OMAP_DRM_H__ */