[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20240626162203.3484272-2-ggiordano@phytec.com>
Date: Wed, 26 Jun 2024 09:22:03 -0700
From: Garrett Giordano <ggiordano@...tec.com>
To: andersson@...nel.org,
mathieu.poirier@...aro.org,
w.egorov@...tec.de
Cc: linux-remoteproc@...r.kernel.org,
linux-kernel@...r.kernel.org,
upstream@...ts.phytec.de
Subject: [PATCH 2/2] remoteproc: k3-r5: Fix log levels where appropriate
Driver was logging information as debug. Changed dev_dbg to dev_info
where appropriate.
Signed-off-by: Garrett Giordano <ggiordano@...tec.com>
---
drivers/remoteproc/ti_k3_r5_remoteproc.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/remoteproc/ti_k3_r5_remoteproc.c b/drivers/remoteproc/ti_k3_r5_remoteproc.c
index 50e486bcfa10..5821b6517063 100644
--- a/drivers/remoteproc/ti_k3_r5_remoteproc.c
+++ b/drivers/remoteproc/ti_k3_r5_remoteproc.c
@@ -558,7 +558,7 @@ static int k3_r5_rproc_start(struct rproc *rproc)
boot_addr = rproc->bootaddr;
/* TODO: add boot_addr sanity checking */
- dev_dbg(dev, "booting R5F core using boot addr = 0x%x\n", boot_addr);
+ dev_info(dev, "booting R5F core using boot addr = 0x%x\n", boot_addr);
/* boot vector need not be programmed for Core1 in LockStep mode */
core = kproc->core;
--
2.25.1
Powered by blists - more mailing lists