ResMgr: Use NameMap for connections and disconnections
authorFernando Guzman Lugo <fernando.lugo@ti.com>
Wed, 7 Mar 2012 22:07:03 +0000 (16:07 -0600)
committerSuman Anna <s-anna@ti.com>
Wed, 23 May 2012 10:01:06 +0000 (05:01 -0500)
commit0602e42d22a05783795e5bfccb683848bba662bf
tree7fe0e6797072d43b688a7a7098f2b2152903d1b9
parent82c520971f30800979bbb3c1fcd01fadfb8e8a8d
ResMgr: Use NameMap for connections and disconnections

The ResMgr channel is not created by default on the host-side
using a fixed channel anymore. Use the NameMap framework to
create the service end-point on the host-side.

NOTE: The NameMap framework is intended for publishing the
services that the slave processor provides, and ResMgr is
really a server (or a service providing resource management)
on the host-side. There is currently no framework for publishing
services from the host-side to the remote-side. The above
usage of NameMap allows the resource manager driver to be
created dynamically, and this needs to be revisited later
in the context of service publishing from any processor to
another.

Signed-off-by: Fernando Guzman Lugo <fernando.lugo@ti.com>
Signed-off-by: Juan Gutierrez <jgutierrez@ti.com>
Signed-off-by: Suman Anna <s-anna@ti.com>
src/ti/resmgr/IpcResource.c
src/ti/resmgr/_IpcResource.h