Georgi Djakov 05309830e1 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>
2019-12-16 09:25:23 +02:00
2019-12-15 12:27:31 -08:00
2019-12-13 14:27:19 -08:00
2019-12-09 10:36:44 -08:00
2019-12-14 12:51:57 -08:00
2019-12-12 19:00:36 +01:00
2019-12-09 10:36:44 -08:00
2019-12-09 18:55:03 +01:00
2019-12-13 14:24:54 -08:00
2019-12-09 11:48:21 -08:00
2019-12-13 14:40:38 -08:00
2019-12-09 13:49:25 -05:00
2019-10-29 04:43:29 -06:00
2019-12-14 11:13:54 -08:00
2019-12-15 15:16:08 -08:00

Linux kernel
============

There are several guides for kernel developers and users. These guides can
be rendered in a number of formats, like HTML and PDF. Please read
Documentation/admin-guide/README.rst first.

In order to build the documentation, use ``make htmldocs`` or
``make pdfdocs``.  The formatted documentation can also be read online at:

    https://www.kernel.org/doc/html/latest/

There are various text files in the Documentation/ subdirectory,
several of them using the Restructured Text markup notation.

Please read the Documentation/process/changes.rst file, as it contains the
requirements for building and running the kernel, and information about
the problems which may result by upgrading your kernel.
Description
No description provided
Readme 5.7 GiB
Languages
C 97.6%
Assembly 1%
Shell 0.5%
Python 0.3%
Makefile 0.3%