rpmsg: resmgr: Use i2c_adapter to obtain I2C platform device

The I2C platform device is parent for i2c_adapter device and it can be
got from i2c_adapter device "parent" field (adapter->dev.parent)
instead of using HW_MOD.

Change-Id: I663b0a04d85f45d049eee85304d292afb2d9910e
Signed-off-by: Grygorii Strashko <grygorii.strashko@ti.com>
rpmsg: omx: return actual user-provided bytes written in write

The 'write' system call is expected to return the number of bytes
written back to userspace. The rpmsg omx driver adds a small packet
header when sending a message to the remote processor, and is
currently returning this header length as well in the driver's write
fop function. This results in the write call always returning more
bytes than what the user has requested. The header length is now
left out of the bytes returned back.

Change-Id: I7132001fbc6fb34d01913bb3c30f455626c91658
Signed-off-by: Suman Anna <s-anna@ti.com>
rpmsg: kconfig: add a dependency with remoteproc in rpmsg_omx

Due to the use of the rproc_pa_to_da API's in rpmsg_omx, now
this module depends on remoteproc directly. So a dependency
needs to be added in kconfig to avoid breaking the build
when disabling remoteproc driver.

Change-Id: Ife9b3ec20154ddf24cc0f7a5241dd13b08440101
Signed-off-by: Juan Gutierrez <jgutierrez@ti.com>
rpmsg: omx: lower the traces level in driver open, ioctl & release

The dev_info traces in open, connect ioctl and release incur a time
penalty and affect application launch time performances. These have
been converted to dev_dbg traces.

Change-Id: Ie8ffd027c4a96bbb5cbfa634f0d661400da8dc09
Signed-off-by: Suman Anna <s-anna@ti.com>
rpmsg: use dev_dbg for channel creation/deletion messages

The number of rpmsg channels is decently high enough during
both the initialization and tear-up/recovery of the remote
processor to effect overall boot time. The trace level of this
print is therefore reduced to improves the overall image init
time. It also helps with the runtime performance of usecases as
they have to create and delete a channel.

Change-Id: I96c293d990bc41f1a9dcd6710ef1388fa2ce2cec
Signed-off-by: Subramaniam C.A <subramaniam.ca@ti.com>
Signed-off-by: Suman Anna <s-anna@ti.com>
rpmsg: fix device definitions in rpmsg client drivers

The rpmsg client drivers - rpmsg_omx, rpmsg_resmgr and the rpmsg
sample drivers - rpmsg_client_sample & rpmsg_server_sample, are
all defining the supported devices incorrectly as a 'platform'
device.

The devices these drivers support should all be 'rpmsg' devices,
and the device id tables declared by these drivers has been
corrected accordingly.

Change-Id: Ib1a0f0de5ffad48fe52937730e90a3254265a2f6
Reported-by: Xavier Boudet <x-boudet@ti.com>
Signed-off-by: Suman Anna <s-anna@ti.com>