Re: [PATCH 2/2] remoteproc: k3-r5: Fix log levels where appropriate

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Garrett,

Am 26.06.24 um 18:22 schrieb Garrett Giordano:
Driver was logging information as debug. Changed dev_dbg to dev_info
where appropriate.

Signed-off-by: Garrett Giordano <ggiordano@xxxxxxxxxx>
---
  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);
There is no need for this debug message to be in info level.

Regards,
Wadim
/* boot vector need not be programmed for Core1 in LockStep mode */
  	core = kproc->core;




[Index of Archives]     [Linux Sound]     [ALSA Users]     [ALSA Devel]     [Linux Audio Users]     [Linux Media]     [Kernel]     [Photo Sharing]     [Gimp]     [Yosemite News]     [Linux Media]

  Powered by Linux