summaryrefslogtreecommitdiff
path: root/drivers/interconnect/internal.h
diff options
context:
space:
mode:
authorGeorgi Djakov <georgi.djakov@linaro.org>2019-11-28 16:18:17 +0200
committerGeorgi Djakov <georgi.djakov@linaro.org>2019-12-16 09:25:23 +0200
commit05309830e1f869f939e283576dd3684313390062 (patch)
tree4f4f6e0539d361c7f804b4c9262245fac623c4da /drivers/interconnect/internal.h
parentdd018a9cf9108f9c7d924f6fe09aed745e78a67e (diff)
interconnect: Add a name to struct icc_path
When debugging interconnect things, it turned out that saving the path name and including it in the traces is quite useful, especially for devices with multiple paths. For the path name we use the one specified in DT, or if we use platform data, the name is based on the source and destination node names. Suggested-by: Bjorn Andersson <bjorn.andersson@linaro.org> Reviewed-by: Bjorn Andersson <bjorn.andersson@linaro.org> Signed-off-by: Georgi Djakov <georgi.djakov@linaro.org>
Diffstat (limited to 'drivers/interconnect/internal.h')
-rw-r--r--drivers/interconnect/internal.h2
1 files changed, 2 insertions, 0 deletions
diff --git a/drivers/interconnect/internal.h b/drivers/interconnect/internal.h
index 5853e8faf223..bf18cb7239df 100644
--- a/drivers/interconnect/internal.h
+++ b/drivers/interconnect/internal.h
@@ -29,10 +29,12 @@ struct icc_req {
/**
* struct icc_path - interconnect path structure
+ * @name: a string name of the path (useful for ftrace)
* @num_nodes: number of hops (nodes)
* @reqs: array of the requests applicable to this path of nodes
*/
struct icc_path {
+ const char *name;
size_t num_nodes;
struct icc_req reqs[];
};