rpmsg: use dynamic_hex_dump for hex dump traces
authorAnna, Suman <s-anna@ti.com>
Fri, 12 Aug 2016 23:42:27 +0000 (18:42 -0500)
committerBjorn Andersson <bjorn.andersson@linaro.org>
Sat, 13 Aug 2016 04:26:21 +0000 (21:26 -0700)
commit211e3a93e5b5933e64ddfb299eee462ac7c7d500
tree4cfcfde8ac4e2136bf7d27d9468e011e6e024e7f
parent0963679c0c30269c17d5891081cf0896f7d92c4b
rpmsg: use dynamic_hex_dump for hex dump traces

There are couple of print_hex_dump traces used in rpmsg code which
prints the actual byte messages being transferred between host and
the remote processors. These traces are quiet verbose and affects
performance, if the appropriate trace level is enabled. These hex
dumps are needed rather rarely, but are quite useful when debugging
complex IPC corner cases. So, this patch switches these hex dump
traces to use the dynamic_hex_dump() API.

The hex dump traces are also enabled only when CONFIG_DYNAMIC_DEBUG
is enabled. This switch allows flexibility of controlling these
traces through dynamic debug, instead of removing them completely.

Signed-off-by: Suman Anna <s-anna@ti.com>
Signed-off-by: Bjorn Andersson <bjorn.andersson@linaro.org>
drivers/rpmsg/virtio_rpmsg_bus.c