From: Viken Dadhaniya <quic_vdadhani@quicinc.com>
To: Konrad Dybcio <konrad.dybcio@linaro.org>, <andersson@kernel.org>,
<srinivas.kandagatla@linaro.org>, <linux-arm-msm@vger.kernel.org>,
<alsa-devel@alsa-project.org>, <linux-kernel@vger.kernel.org>
Cc: <quic_msavaliy@quicinc.com>, <quic_vtanuku@quicinc.com>,
<quic_anupkulk@quicinc.com>, <quic_cchiluve@quicinc.com>
Subject: Re: [PATCH v1] slimbus: qcom-ngd-ctrl: Reduce auto suspend delay
Date: Fri, 8 Mar 2024 18:13:30 +0530 [thread overview]
Message-ID: <0fe1374b-318b-4dea-94fc-596c665eab53@quicinc.com> (raw)
In-Reply-To: <d784e46d-974d-4bf3-a2d3-491e7ad19701@linaro.org>
On 3/6/2024 2:46 AM, Konrad Dybcio wrote:
>
>
> On 3/4/24 14:50, Viken Dadhaniya wrote:
>> Currently we have auto suspend delay of 1s which is
>> very high and it takes long time to driver for runtime
>> suspend after use case is done.
>>
>> Hence to optimize runtime PM ops, reduce auto suspend
>> delay to 100ms.
>>
>> Signed-off-by: Viken Dadhaniya <quic_vdadhani@quicinc.com>
>> ---
>
> What determines 1s to be high and 100ms to be low enough? Could
> you share some more reasoning?
Right now we don't have exact number which can quantify either power or
performance. But we are following small window so as to not keep timer
running longer while having resources like Clock ON. Theoretically and
testing wise, this is not creating any side effect too.
>
>> drivers/slimbus/qcom-ngd-ctrl.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/slimbus/qcom-ngd-ctrl.c
>> b/drivers/slimbus/qcom-ngd-ctrl.c
>> index efeba8275a66..5de45a0e3da5 100644
>> --- a/drivers/slimbus/qcom-ngd-ctrl.c
>> +++ b/drivers/slimbus/qcom-ngd-ctrl.c
>> @@ -81,7 +81,7 @@
>> #define SLIM_USR_MC_DISCONNECT_PORT 0x2E
>> #define SLIM_USR_MC_REPEAT_CHANGE_VALUE 0x0
>> -#define QCOM_SLIM_NGD_AUTOSUSPEND MSEC_PER_SEC
>> +#define QCOM_SLIM_NGD_AUTOSUSPEND (MSEC_PER_SEC / 10)
>
> This could be a good opportunity to inline this value..
Updated in v2.
>
> Konrad
prev parent reply other threads:[~2024-03-08 12:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-04 13:50 Viken Dadhaniya
2024-03-05 21:16 ` Konrad Dybcio
2024-03-08 12:43 ` Viken Dadhaniya [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=0fe1374b-318b-4dea-94fc-596c665eab53@quicinc.com \
--to=quic_vdadhani@quicinc.com \
--cc=alsa-devel@alsa-project.org \
--cc=andersson@kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_anupkulk@quicinc.com \
--cc=quic_cchiluve@quicinc.com \
--cc=quic_msavaliy@quicinc.com \
--cc=quic_vtanuku@quicinc.com \
--cc=srinivas.kandagatla@linaro.org \
/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®