From: Stanimir Varbanov <stanimir.k.varbanov@gmail.com>
To: Konrad Dybcio <konrad.dybcio@linaro.org>,
Dikshita Agarwal <quic_dikshita@quicinc.com>,
linux-media@vger.kernel.org, quic_vgarodia@quicinc.com,
agross@kernel.org, andersson@kernel.org, mchehab@kernel.org
Cc: linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH] venus: replace arrary index with enum for supported formats
Date: Fri, 26 May 2023 01:12:43 +0300 [thread overview]
Message-ID: <42b9a661-a050-4cd3-16bf-b4af88745383@gmail.com> (raw)
In-Reply-To: <0f7a33c1-f894-adfe-94d7-89296893128f@linaro.org>
Hi Konrad,
On 23.05.23 г. 11:02 ч., Konrad Dybcio wrote:
>
>
> On 22.05.2023 08:17, Dikshita Agarwal wrote:
>> Use enums to list supported formats for encoder and decoder
>> instead of array index which was a error prone design.
>>
>> Signed-off-by: Dikshita Agarwal <quic_dikshita@quicinc.com>
>> ---
> Thanks a lot.
>
> Reviewed-by: Konrad Dybcio <konrad.dybcio@linaro.org>
>
>> drivers/media/platform/qcom/venus/core.h | 16 ++++++++
>> drivers/media/platform/qcom/venus/vdec.c | 63 +++++++++++++++++++-------------
>> drivers/media/platform/qcom/venus/venc.c | 31 +++++++++-------
>> 3 files changed, 72 insertions(+), 38 deletions(-)
>>
>> diff --git a/drivers/media/platform/qcom/venus/core.h b/drivers/media/platform/qcom/venus/core.h
>> index 12a42fb..e988ed4 100644
>> --- a/drivers/media/platform/qcom/venus/core.h
>> +++ b/drivers/media/platform/qcom/venus/core.h
>> @@ -83,6 +83,22 @@ struct venus_resources {
>> const char *fwname;
>> };
>>
>> +enum venus_fmt {
>> + VENUS_FMT_NV12 = 0,
>> + VENUS_FMT_QC08C = 1,
>> + VENUS_FMT_QC10C = 2,
>> + VENUS_FMT_H264 = 3,
>> + VENUS_FMT_VP8 = 4,
>> + VENUS_FMT_VP9 = 5,
>> + VENUS_FMT_HEVC = 6,
>> + VENUS_FMT_VC1_ANNEX_G = 7,
>> + VENUS_FMT_VC1_ANNEX_L = 8,
>> + VENUS_FMT_MPEG4 = 9,
>> + VENUS_FMT_MPEG2 = 10,
>> + VENUS_FMT_H263 = 11,
>> + VENUS_FMT_XVID = 12,
> Nit: I don't think the '= n' is necessary here, as it doesn't
> map to anything in hw/fw (or does it?)
IMO, the numbers could help when debugging to avoid counting.
>
> Konrad
--
regards,
Stan
prev parent reply other threads:[~2023-05-25 22:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-22 6:17 Dikshita Agarwal
2023-05-23 8:02 ` Konrad Dybcio
2023-05-24 4:53 ` Dikshita Agarwal
2023-05-25 22:12 ` Stanimir Varbanov [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=42b9a661-a050-4cd3-16bf-b4af88745383@gmail.com \
--to=stanimir.k.varbanov@gmail.com \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=konrad.dybcio@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=quic_dikshita@quicinc.com \
--cc=quic_vgarodia@quicinc.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®