From: Andrew Davis <afd@ti.com>
To: Garrett Giordano <ggiordano@phytec.com>, <andersson@kernel.org>,
<mathieu.poirier@linaro.org>, <w.egorov@phytec.de>
Cc: <linux-remoteproc@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <upstream@lists.phytec.de>
Subject: Re: [PATCH v2] remoteproc: k3-dsp: Fix log levels where appropriate
Date: Wed, 3 Jul 2024 12:15:14 -0500 [thread overview]
Message-ID: <4f4698d6-1594-4aca-bf2f-5b7e3229a50f@ti.com> (raw)
In-Reply-To: <20240626191438.490524-1-ggiordano@phytec.com>
On 6/26/24 2:14 PM, Garrett Giordano wrote:
> Driver was logging information as errors. Changed dev_err to dev_dbg
> where appropriate.
>
> Signed-off-by: Garrett Giordano <ggiordano@phytec.com>
> ---
Acked-by: Andrew Davis <afd@ti.com>
> -v2
> - Change from dev_info to dev_dbg
> - Drop k3-r5 PATCH
> ---
> drivers/remoteproc/ti_k3_dsp_remoteproc.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/remoteproc/ti_k3_dsp_remoteproc.c b/drivers/remoteproc/ti_k3_dsp_remoteproc.c
> index 3555b535b168..a22d41689a7d 100644
> --- a/drivers/remoteproc/ti_k3_dsp_remoteproc.c
> +++ b/drivers/remoteproc/ti_k3_dsp_remoteproc.c
> @@ -327,7 +327,7 @@ static int k3_dsp_rproc_start(struct rproc *rproc)
> goto put_mbox;
> }
>
> - dev_err(dev, "booting DSP core using boot addr = 0x%x\n", boot_addr);
> + dev_dbg(dev, "booting DSP core using boot addr = 0x%x\n", boot_addr);
> ret = ti_sci_proc_set_config(kproc->tsp, boot_addr, 0, 0);
> if (ret)
> goto put_mbox;
> --
> 2.25.1
>
>
next prev parent reply other threads:[~2024-07-03 17:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-26 19:14 [PATCH v2] remoteproc: k3-dsp: Fix log levels where appropriate Garrett Giordano
2024-07-03 17:15 ` Andrew Davis [this message]
2024-07-04 15:44 ` Mathieu Poirier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4f4698d6-1594-4aca-bf2f-5b7e3229a50f@ti.com \
--to=afd@ti.com \
--cc=andersson@kernel.org \
--cc=ggiordano@phytec.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=upstream@lists.phytec.de \
--cc=w.egorov@phytec.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox