From: Bryan O'Donoghue <bod@kernel.org>
To: Vikash Garodia <quic_vgarodia@quicinc.com>,
Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Cc: Stanimir Varbanov <stanimir.k.varbanov@gmail.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
linux-media@vger.kernel.org, linux-arm-msm@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Johan Hovold <johan+linaro@kernel.org>
Subject: Re: [PATCH 0/8] Reup: SM8350 and SC8280XP venus support
Date: Fri, 4 Apr 2025 10:02:47 +0100 [thread overview]
Message-ID: <70891a99-d2ca-4fd3-a88d-2f66a9a78f66@kernel.org> (raw)
In-Reply-To: <1dd6e03d-09be-4853-741a-4fb47b7619a0@quicinc.com>
On 04/04/2025 06:24, Vikash Garodia wrote:
>>> How different is this from sm8250 which is already enabled on iris driver ?
>> As far as I remember, SM8250 support in Iris did not reach
>> feature-parity yet. So in my opinion it is fine to add new platforms to
>> the Venus driver, that will later migrate to the Iris driver.
> I would say, from decoder side all codecs are there now on Iris. H264 merged,
> while h265 and VP9 dec are posted as RFC, there is one compliance failure which
> is under debug to post them as regular patches.
> If we are mainly looking for decode usecases, then we should be on Iris.
> Preference would be to stay on Iris, otherwise we would have that extra ask to
> port it later from venus to iris.
Right now venus represents 9/20 - 45% of the patches being churned for
sc8280xp.
https://github.com/jhovold/linux/tree/wip/sc8280xp-6.14-rc7
This is a good debate to have, however my memory of what we collectively
agreed both in public and private was to continue to merge new silicon
<= HFI6XX into venus unless and until iris hit feature parity for HFI6XX
and to continue with venus at that point for < HFI6XX.
So merging sc8280xp - HFI6XX is consistent with our agreement, the right
thing to do for our users and a big win in terms of technical debt
reduction.
I will post an update to this series ASAP.
---
bod
next prev parent reply other threads:[~2025-04-04 9:02 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-04 13:07 [PATCH 0/8] Reup: SM8350 and SC8280XP venus support Bryan O'Donoghue
2025-03-04 13:07 ` [PATCH 1/8] media: dt-bindings: Document SC8280XP/SM8350 Venus Bryan O'Donoghue
2025-03-04 14:00 ` Krzysztof Kozlowski
2025-03-04 16:48 ` Bryan O'Donoghue
2025-03-05 3:36 ` Vikash Garodia
2025-03-04 13:07 ` [PATCH 2/8] media: venus: core: Remove trailing commas from of match entries Bryan O'Donoghue
2025-03-04 13:07 ` [PATCH 3/8] media: venus: hfi_venus: Support only updating certain bits with presets Bryan O'Donoghue
2025-03-04 13:07 ` [PATCH 4/8] media: platform: venus: Add optional LLCC path Bryan O'Donoghue
2025-03-08 17:44 ` Konrad Dybcio
2025-03-04 13:07 ` [PATCH 5/8] media: venus: core: Add SM8350 resource struct Bryan O'Donoghue
2025-03-04 20:54 ` Dmitry Baryshkov
2025-03-04 13:07 ` [PATCH 6/8] media: venus: core: Add SC8280XP " Bryan O'Donoghue
2025-03-04 20:54 ` Dmitry Baryshkov
2025-03-04 13:07 ` [PATCH 7/8] arm64: dts: qcom: sc8280xp: Add Venus Bryan O'Donoghue
2025-03-04 14:02 ` Krzysztof Kozlowski
2025-03-04 16:41 ` Konrad Dybcio
2025-03-04 16:49 ` Bryan O'Donoghue
2025-03-04 16:50 ` Konrad Dybcio
2025-03-04 20:55 ` Dmitry Baryshkov
2025-03-04 13:07 ` [PATCH 8/8] arm64: dts: qcom: sc8280xp-x13s: Enable Venus Bryan O'Donoghue
2025-03-05 3:19 ` [PATCH 0/8] Reup: SM8350 and SC8280XP venus support Vikash Garodia
2025-03-05 9:37 ` Bryan O'Donoghue
2025-04-03 16:58 ` Dmitry Baryshkov
2025-04-04 5:24 ` Vikash Garodia
2025-04-04 9:02 ` Bryan O'Donoghue [this message]
2025-04-04 10:33 ` Vikash Garodia
2025-05-27 10:53 ` Johan Hovold
2025-05-28 14:15 ` Dmitry Baryshkov
2025-04-05 14:48 ` Dmitry Baryshkov
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=70891a99-d2ca-4fd3-a88d-2f66a9a78f66@kernel.org \
--to=bod@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=johan+linaro@kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.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_vgarodia@quicinc.com \
--cc=robh@kernel.org \
--cc=stanimir.k.varbanov@gmail.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 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.