From: "Luca Weiss" <luca.weiss@fairphone.com>
To: "Luca Weiss" <luca.weiss@fairphone.com>, <linux-arm-msm@vger.kernel.org>
Cc: <~postmarketos/upstreaming@lists.sr.ht>,
"Stanimir Varbanov" <stanimir.varbanov@linaro.org>,
"Andy Gross" <agross@kernel.org>,
"Bjorn Andersson" <bjorn.andersson@linaro.org>,
"Mauro Carvalho Chehab" <mchehab@kernel.org>,
<linux-media@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] media: venus: hfi: Add error message for timeout error
Date: Fri, 25 Mar 2022 08:58:47 +0100 [thread overview]
Message-ID: <CISSESOMBR2Y.2L4TX1ZPPPIT8@otso> (raw)
In-Reply-To: <20220114110226.130380-1-luca.weiss@fairphone.com>
Hi everyone,
any feedback on this patch and the following one?
Regards
Luca
On Fri Jan 14, 2022 at 12:02 PM CET, Luca Weiss wrote:
> This error can appear with wrong configuration and is difficult to find
> as it just returns -ETIMEDOUT with no further message.
>
> Signed-off-by: Luca Weiss <luca.weiss@fairphone.com>
> ---
> drivers/media/platform/qcom/venus/hfi_venus.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/media/platform/qcom/venus/hfi_venus.c b/drivers/media/platform/qcom/venus/hfi_venus.c
> index 3a75a27632fb..9a34662fea38 100644
> --- a/drivers/media/platform/qcom/venus/hfi_venus.c
> +++ b/drivers/media/platform/qcom/venus/hfi_venus.c
> @@ -1583,8 +1583,10 @@ static int venus_suspend_3xx(struct venus_core *core)
> */
> ret = readx_poll_timeout(venus_cpu_and_video_core_idle, hdev, val, val,
> 1500, 100 * 1500);
> - if (ret)
> + if (ret) {
> + dev_err(dev, "wait for cpu and video core idle fail (%d)\n", ret);
> return ret;
> + }
>
> ret = venus_prepare_power_collapse(hdev, false);
> if (ret) {
> --
> 2.34.1
prev parent reply other threads:[~2022-03-25 7:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-14 11:02 [PATCH 1/2] media: venus: hfi: Add error message for timeout error Luca Weiss
2022-01-14 11:02 ` [PATCH 2/2] media: venus: hfi: avoid null dereference in deinit Luca Weiss
2022-03-25 7:58 ` Luca Weiss [this message]
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=CISSESOMBR2Y.2L4TX1ZPPPIT8@otso \
--to=luca.weiss@fairphone.com \
--cc=agross@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=stanimir.varbanov@linaro.org \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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