From 24e5fde444ff273fed2bdd6b176be3ea68d851cb Mon Sep 17 00:00:00 2001
From: Aditya Atluri <Aditya.Atluri@amd.com>
Date: Mon, 29 Aug 2016 15:38:04 -0500
Subject: [PATCH] added docs to how to use hipModuleLaunchKernel

Change-Id: I626241552c69cdae56501371374ca8f2c6776c85
---
 docs/markdown/hip_porting_driver_api.md | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/docs/markdown/hip_porting_driver_api.md b/docs/markdown/hip_porting_driver_api.md
index 0566e452bd..758b0672c1 100644
--- a/docs/markdown/hip_porting_driver_api.md
+++ b/docs/markdown/hip_porting_driver_api.md
@@ -115,6 +115,9 @@ addresses from a single unified pool.  Thus addresses may be shared between cont
 unlike the original CUDA definition a new context does not create a new address space for
 the device.   
 
+#### Using hipModuleLaunchKernel
+`hipModuleLaunchKernel` is `cuLaunchKernel` in HIP world. It takes the same arguments as `cuLaunchKernel`. The argument `kernelParams` is not fully implemented for HCC. The workaround for it is, to use platform specific macros for each target. Or, `extra` argument can be used which works on both the platforms.
+
 #### Additional Information
 HCC allocates staging buffers (used for unpinned copies) on a per-device basis.