[PATCH 0/4] Add VIC support for Tegra124

[Arto Merilainen]

This series adds Video-Image-Compositor (VIC) support for Tegra124. The unit
replaced gr2d engine on T124 and it is effectively used for similar
operations: making simple surface copy and fill operations.

The series consists of four patches: The first patch fixes an issue in the
host1x submit routine which has prevented using same buffer object for
multiple command buffers. The second patch makes a simple improvement to
the firewall to allow implementing address register validator for VIC. The
last two patches in the series make the real modifications to Tegra DRM and
device tree to enable the engine on T124.

The series has been tested on Jetson TK1 by first disabling IOMMU (*),
enabling CMA and running a VIC clear test case that is posted to dri-devel
and linux-tegra mailing lists. The firmware image for VIC is publicly
available as part of Linux For Tegra driver package [0].

[0] https://developer.nvidia.com/linux-tegra

(*) Currently Tegra DRM does not support mapping the host1x command buffers
into kernel address space in case IOMMU is enabled.


Arto Merilainen (4):
  host1x: Store device address to all bufs
  host1x: Pass register value in firewall
  drm/tegra: Add VIC support
  ARM: tegra: Add VIC for Tegra124

 arch/arm/boot/dts/tegra124.dtsi |  11 +
 drivers/gpu/drm/tegra/Makefile  |   3 +-
 drivers/gpu/drm/tegra/drm.c     |   9 +-
 drivers/gpu/drm/tegra/drm.h     |   5 +-
 drivers/gpu/drm/tegra/gr2d.c    |   4 +-
 drivers/gpu/drm/tegra/gr3d.c    |   4 +-
 drivers/gpu/drm/tegra/vic.c     | 593 ++++++++++++++++++++++++++++++++++++++++
 drivers/gpu/drm/tegra/vic.h     | 116 ++++++++
 drivers/gpu/host1x/job.c        |  44 ++-
 include/linux/host1x.h          |   5 +-
 10 files changed, 769 insertions(+), 25 deletions(-)
 create mode 100644 drivers/gpu/drm/tegra/vic.c
 create mode 100644 drivers/gpu/drm/tegra/vic.h

-- 
1.8.1.5

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/