From: Bryan O'Donoghue <bod@kernel.org>
To: Kirill Ermolitskiy <00vopoj00@gmail.com>
Cc: linux-media@vger.kernel.org, vikash.garodia@oss.qualcomm.com,
dikshita.agarwal@oss.qualcomm.com, linux-arm-msm@vger.kernel.org
Subject: Re: venus: encoder job execution hard-resets SoC on SM7325 (sc7280-compatible) — extensive analysis, need wrapper/GDSC insight
Date: Mon, 20 Jul 2026 20:36:11 +0100 [thread overview]
Message-ID: <f4041aba-ccbb-4126-a65b-a385e882949e@kernel.org> (raw)
In-Reply-To: <CADRRrN23tWrKKnPDdsO_61QQd790z2W+2ejZ-s1iZkJh+=oHhw@mail.gmail.com>
On 20/07/2026 17:28, Kirill Ermolitskiy wrote:
> Tested forcing all venus_opp_table entries to rpmhpd_opp_turbo_l1
> (verified via /sys/firmware/devicetree) — encoder still hard-resets
> identically at first frame. So if it's an operating-point failure,
> it's not the CX vote via required-opps; possibly a different rail
> (MX/MMCX?) or something the OPP framework doesn't reach on kodiak.
>
> ---
> Del'aRun
In which case let's try constraining the pixel and non-pixel IOVAs.
Give this a go
https://patch.msgid.link/20260601041336.9497-2-daniel@quora.org
* Adapted to the appropriate dtsi obvs.
---
bod
next prev parent reply other threads:[~2026-07-20 19:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <MOR1FYP_9xkM8GfpziB5D4Q3H5XLHq6MowZkeFMhI_49wkvgOVxXHbtJYMHHnToR_DOz2HU3N102cMMRPNWfLA==@protonmail.internalid>
2026-07-20 12:22 ` venus: encoder job execution hard-resets SoC on SM7325 (sc7280-compatible) — extensive analysis, need wrapper/GDSC insight Kirill Ermolitskiy
2026-07-20 12:55 ` Bryan O'Donoghue
2026-07-20 16:28 ` Kirill Ermolitskiy
2026-07-20 19:36 ` Bryan O'Donoghue [this message]
2026-07-20 20:41 ` Kirill Ermolitskiy
2026-07-20 21:31 ` Bryan O'Donoghue
2026-07-20 21:38 ` Kirill Ermolitskiy
2026-07-20 21:48 ` Kirill Ermolitskiy
2026-07-20 22:01 ` Dmitry Baryshkov
2026-07-20 23:03 ` Kirill Ermolitskiy
2026-07-20 23:22 ` Bryan O'Donoghue
2026-07-21 8:37 ` Kirill Ermolitskiy
2026-07-21 11:14 ` Vikash Garodia
2026-07-21 13:21 ` Kirill Ermolitskiy
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=f4041aba-ccbb-4126-a65b-a385e882949e@kernel.org \
--to=bod@kernel.org \
--cc=00vopoj00@gmail.com \
--cc=dikshita.agarwal@oss.qualcomm.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=vikash.garodia@oss.qualcomm.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