From: Vishnu Reddy <busanna.reddy@oss.qualcomm.com>
To: Renjiang Han <renjiang.han@oss.qualcomm.com>,
Vikash Garodia <vikash.garodia@oss.qualcomm.com>,
Dikshita Agarwal <dikshita.agarwal@oss.qualcomm.com>,
Abhinav Kumar <abhinav.kumar@linux.dev>,
Bryan O'Donoghue <bod@kernel.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
linux-arm-msm@vger.kernel.org,
Wangao Wang <wangao.wang@oss.qualcomm.com>
Subject: Re: [PATCH] media: qcom: iris: add firmware debug logging support
Date: Wed, 2 Sep 2026 09:45:24 +0530 [thread overview]
Message-ID: <594345ef-4e64-4932-590f-02dfd6d96349@oss.qualcomm.com> (raw)
In-Reply-To: <c169738e-33b0-4e06-8c9f-587f5c1afc46@oss.qualcomm.com>
On 9/2/2026 9:32 AM, Renjiang Han wrote:
>
> On 9/1/2026 12:13 PM, Vishnu Reddy wrote:
>> Setting the firmware log level to 0x0000003f may cause hardware response
>> timeouts due to excessive serial logging. HW_RESPONSE_TIMEOUT_VALUE should
>> be increased accordingly.
> Yes, but this patch is for fw log feature, response timeout value is
> performance issue.
> I think we'd better use another patch to fix it. What do you think of it?
>
It's better to include it in this patch, since this change can directly trigger
response timeouts when high FW log levels are enabled.
next prev parent reply other threads:[~2026-09-02 4:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-15 16:25 Renjiang Han
2026-08-17 6:02 ` Vishnu Reddy
2026-08-24 10:05 ` Renjiang Han
2026-08-31 6:39 ` Renjiang Han
2026-09-01 4:13 ` Vishnu Reddy
2026-09-02 4:02 ` Renjiang Han
2026-09-02 4:15 ` Vishnu Reddy [this message]
2026-09-02 4:30 ` Renjiang Han
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=594345ef-4e64-4932-590f-02dfd6d96349@oss.qualcomm.com \
--to=busanna.reddy@oss.qualcomm.com \
--cc=abhinav.kumar@linux.dev \
--cc=bod@kernel.org \
--cc=dikshita.agarwal@oss.qualcomm.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=renjiang.han@oss.qualcomm.com \
--cc=vikash.garodia@oss.qualcomm.com \
--cc=wangao.wang@oss.qualcomm.com \
/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
all inboxes | Powered by JetHome®