All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stanimir Varbanov <stanimir.varbanov@linaro.org>
To: dikshita@codeaurora.org
Cc: linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-msm@vger.kernel.org, vgarodia@codeaurora.org
Subject: Re: [PATCH v3 7/7] media: venus: Set buffer to FW based on FW min count requirement.
Date: Tue, 3 Aug 2021 11:00:32 +0300	[thread overview]
Message-ID: <253417f1-579a-0a57-388b-7fb07fd83d9c@linaro.org> (raw)
In-Reply-To: <6c8f0d013be8ba6d276afe04d6e0c840@codeaurora.org>



On 8/2/21 10:50 AM, dikshita@codeaurora.org wrote:
>>> req->count_min = inst->fw_min_cnt;
>>> +
>>> +    ret = hfi_plat->bufreq(&params, inst->session_type, buftype, req);
>>> +    if (buftype == HFI_BUFFER_OUTPUT || buftype == HFI_BUFFER_OUTPUT2)
>>
>> ^^^^
>>
>>> +        if (inst->fw_min_cnt != req->count_min)
>>> +            inst->fw_min_cnt = req->count_min;
>>> +    return ret;
>>>  }
>>
>> Also in regards to inst->fw_min_cnt, can we pass fw_min_cnt as input to
>> get_bufreq via 'req' structure, i.e.
>>
>> req.count_min = inst->fw_min_cnt;
>>
>> ret = venus_helper_get_bufreq(inst, type, &req);
>>
>> inst->fw_min_cnt = req.count_min
>>
>> ?
>>
> Sorry, I didn't get it, How is this different from the current
> implementation?

The difference is that platform_get_bufreq() will not modify any of
'struct venus_inst' members, i.e. platform_get_bufreq() is not supposed
to change anything from input 'inst' argument.

-- 
regards,
Stan

  reply	other threads:[~2021-08-03  8:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-14  7:01 [PATCH v3 0/7] media: venus: Enable venus support on sc7280 Dikshita Agarwal
2021-07-14  7:01 ` [PATCH v3 1/7] venus: firmware: enable no tz fw loading for sc7280 Dikshita Agarwal
2021-07-14  7:01 ` [PATCH v3 2/7] media: venus: core: Add sc7280 DT compatible and resource data Dikshita Agarwal
2021-07-14  7:01 ` [PATCH v3 3/7] media: venus: Add num_vpp_pipes to resource structure Dikshita Agarwal
2021-07-14  7:01 ` [PATCH v3 4/7] media: venus: hfi: Skip AON register programming for V6 1pipe Dikshita Agarwal
2021-07-14  7:01 ` [PATCH v3 5/7] venus: vdec: set work route to fw Dikshita Agarwal
2021-07-14  7:01 ` [PATCH v3 6/7] media: venus: helpers: update NUM_MBS macro calculation Dikshita Agarwal
2021-07-14  7:01 ` [PATCH v3 7/7] media: venus: Set buffer to FW based on FW min count requirement Dikshita Agarwal
2021-07-28 14:53   ` Stanimir Varbanov
2021-08-02  7:50     ` dikshita
2021-08-03  8:00       ` Stanimir Varbanov [this message]
2021-07-28  9:52 ` [PATCH v3 0/7] media: venus: Enable venus support on sc7280 Stanimir Varbanov

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=253417f1-579a-0a57-388b-7fb07fd83d9c@linaro.org \
    --to=stanimir.varbanov@linaro.org \
    --cc=dikshita@codeaurora.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.