From: Suzuki K Poulose Date: Mon, 10 Jul 2023 06:24:59 +0000 (+0530) Subject: coresight: platform: acpi: Ignore the absence of graph X-Git-Tag: v6.6.17~4035^2~28^2~10 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=3a2888aa1f962c55ca36119aebe67355c7bf54e4;p=platform%2Fkernel%2Flinux-rpi.git coresight: platform: acpi: Ignore the absence of graph Some components may not have graph connections for describing the trace path. e.g., ETE, where it could directly use the per CPU TRBE. Ignore the absence of graph connections Signed-off-by: Suzuki K Poulose Signed-off-by: Anshuman Khandual Link: https://lore.kernel.org/r/20230710062500.45147-6-anshuman.khandual@arm.com --- diff --git a/drivers/hwtracing/coresight/coresight-platform.c b/drivers/hwtracing/coresight/coresight-platform.c index 27ca22c..7d7b641 100644 --- a/drivers/hwtracing/coresight/coresight-platform.c +++ b/drivers/hwtracing/coresight/coresight-platform.c @@ -667,8 +667,12 @@ static int acpi_coresight_parse_graph(struct device *dev, struct coresight_connection *new_conn; graph = acpi_get_coresight_graph(adev); + /* + * There are no graph connections, which is fine for some components. + * e.g., ETE + */ if (!graph) - return -ENOENT; + return 0; nlinks = graph->package.elements[2].integer.value; if (!nlinks)