public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: mansur@codeaurora.org
To: Stephen Boyd <swboyd@chromium.org>
Cc: linux-media@vger.kernel.org, stanimir.varbanov@linaro.org,
	linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
	vgarodia@codeaurora.org
Subject: Re: [PATCH 2/2] venus: core: vote for video-mem icc path and change avg, peak bw
Date: Thu, 17 Sep 2020 07:14:55 +0530	[thread overview]
Message-ID: <30ad67bf36be40c6a2b395962f8e918f@codeaurora.org> (raw)
In-Reply-To: <159959029779.454335.10674172341529908104@swboyd.mtv.corp.google.com>

> On 2020-09-09 00:08, Stephen Boyd wrote:
>> Quoting Mansur Alisha Shaik (2020-09-07 20:44:38)
>>> Currently we are voting for venus0-ebi path during buffer processing
>>> with an average bandwidth of all the instances and unvoting during
>>> session release.
>>> 
>>> While video streaming when we try to do XO-SD using the command
>>> "echo mem > /sys/power/state command" , device is not entering
>>> to suspend state and from interconnect summary seeing votes for 
>>> venus0-ebi
>>> 
>>> Corrected this by voting for venus0-ebi path in venus_runtime_resume
>> 
>> venus_runtime_resume() please so we know it's a function.
Changed to function like notation and RESEND v2
https://lore.kernel.org/patchwork/project/lkml/list/?series=463283
>> 
>>> and unvote during venus_runtime_suspend.
>> 
>> venus_runtime_suspend().
>> 
>>> 
>>> Signed-off-by: Mansur Alisha Shaik <mansur@codeaurora.org>
>>> ---
>> 
>> Any Fixes: tag?
Added the Fixes tag
>> 
>>>  drivers/media/platform/qcom/venus/core.c | 10 +++++++++-
>>>  1 file changed, 9 insertions(+), 1 deletion(-)
>>> 
>>> diff --git a/drivers/media/platform/qcom/venus/core.c 
>>> b/drivers/media/platform/qcom/venus/core.c
>>> index 4857bbd..79d8600 100644
>>> --- a/drivers/media/platform/qcom/venus/core.c
>>> +++ b/drivers/media/platform/qcom/venus/core.c
>>> @@ -373,6 +373,10 @@ static __maybe_unused int 
>>> venus_runtime_suspend(struct device *dev)
>>>         if (ret)
>>>                 return ret;
>>> 
>>> +       ret = icc_set_bw(core->video_path, 0, 0);
>>> +       if (ret)
>>> +               return ret;
>>> +
>>>         return ret;
>>>  }
>>> 
>>> @@ -382,7 +386,11 @@ static __maybe_unused int 
>>> venus_runtime_resume(struct device *dev)
>>>         const struct venus_pm_ops *pm_ops = core->pm_ops;
>>>         int ret;
>>> 
>>> -       ret = icc_set_bw(core->cpucfg_path, 0, kbps_to_icc(1000));
>>> +       ret = icc_set_bw(core->video_path, kbps_to_icc(20000), 0);
>> 
>> This also shows that the arguments to icc_set_bw() we're backwards? 
>> Can
>> that be fixed in another patch instead of putting it in this one?
posted as another patch set.
https://lore.kernel.org/patchwork/project/lkml/list/?series=463283

      reply	other threads:[~2020-09-17  1:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-08  3:44 [PATCH 2/2] venus: core: vote for video-mem icc path and change avg, peak bw Mansur Alisha Shaik
2020-09-08 18:38 ` Stephen Boyd
2020-09-17  1:44   ` mansur [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=30ad67bf36be40c6a2b395962f8e918f@codeaurora.org \
    --to=mansur@codeaurora.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=stanimir.varbanov@linaro.org \
    --cc=swboyd@chromium.org \
    --cc=vgarodia@codeaurora.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