From: "Luca Weiss" <luca.weiss@fairphone.com>
To: "Vikash Garodia" <quic_vgarodia@quicinc.com>,
"Dikshita Agarwal" <quic_dikshita@quicinc.com>,
"Konrad Dybcio" <konradybcio@kernel.org>,
<linux-arm-msm@vger.kernel.org>
Subject: Re: Venus probe issues on SM6350 SoC
Date: Tue, 01 Apr 2025 11:40:08 +0200 [thread overview]
Message-ID: <D8V7BAC36W6I.127OOFAEB4N63@fairphone.com> (raw)
In-Reply-To: <9edeecac-008a-ed28-a029-9fe2278c12c4@quicinc.com>
On Tue Apr 1, 2025 at 11:21 AM CEST, Vikash Garodia wrote:
>
> On 4/1/2025 1:12 PM, Luca Weiss wrote:
>> On Tue Apr 1, 2025 at 8:55 AM CEST, Vikash Garodia wrote:
>>>
>>>
>>> On 4/1/2025 11:47 AM, Vikash Garodia wrote:
>>>> Hi Luca,
>>>>
>>>> On 3/28/2025 8:52 PM, Luca Weiss wrote:
>>>>> Hi all, and Vikash and Dikshita,
>>>>>
>>>>> Konrad Dybcio was suggesting I write an email here, maybe someone has a
>>>>> good idea what I can try.
>>>>>
>>>>> I've been working on bringup for SM6350/SM7225 ("lagoon") for the
>>>>> Fairphone 4 smartphone but have been stuck on getting Venus working for
>>>>> a long time (~January 2022). Essentially, whatever I try probe fails
>>>>> with the following error:
>>>>>
>>>>> [ 41.939451] qcom-venus aa00000.video-codec: non legacy binding
>>>>> [ 42.162105] qcom-venus aa00000.video-codec: wait for cpu and video core idle fail (-110)
>>>>> [ 42.167037] qcom-venus aa00000.video-codec: probe with driver qcom-venus failed with error -110
>>>>>
>>>>> I've double checked the videocc driver against downstream, the videocc
>>>>> GDSCs and their flags, compared dts bits, checked basic driver bits but
>>>>> I couldn't find anything to get further than this.
>>>>>
>>>>> For driver / compatible, it doesn't seem to matter if I use sm8250 or
>>>>> sc7280 compatible or actually the struct I created for sm6350.
>>>>>
>>>>> I'll attach the log with some extra debug prints below.
>>>>>
>>>>> My git branch for reference: https://github.com/z3ntu/linux/commits/sm6350-6.14.y-wip-venus/
>>>>>
>>>>> I didn't try the new Iris driver yet, mostly because as far as I can
>>>>> tell, VPU_VERSION_IRIS2_1 is not yet supported there, just IRIS2
>>>>> (sm8250) and IRIS3 (sm8550). But I'm also happy to try something there.
>>>> The good part if IRIS2_1 configuration have firmware support with gen2 HFIs.
>>>> Since you are wiling to give a try, let me or Dikshita share the firmware with
>>>> you in a short while, and with that, you can directly try SM6350 with IRIS
>>>> driver. Given that we have already validated SC7280 with gen2 (downstream
>>>> version of IRIS though), i am quite hopeful that SM6350 can be up with iris.
>>>> FYI, iris is having just the h264 decoder at this point with RFC patches posted
>>>> for VP9 and H265 decoder.
>>> Pls try with below firmware bins on IRIS driver. We can debug from there. Hope
>>> you have the access to download the binary.
>>>
>>> https://git.codelinaro.org/clo/linux-kernel/linux-firmware/-/commit/56035bf6edac7eb4d2867528c598eb646ee68651
>>
>> Hi Vikash,
>>
>> Thanks for sharing these binaries!
>>
>> I've signed them with sectools for my device and tried them first with
>> the venus driver.
>>
>> There it looks like the firmware doesn't load at all:
>> [ 44.798028] qcom-venus aa00000.video-codec: fail to load video firmware
>> [ 44.800367] qcom-venus aa00000.video-codec: probe with driver qcom-venus failed with error -22
>>
>> Then with iris driver and qcom,sm8250-venus compatible while it does
>> seem to complete the probe function (I see a print I've added in
>> iris_probe before the last "return 0;"), the phone crashes.
> The approach to update the SM8250 platform data to bringup looks good. Could you
> share the boot crash stack as well ?
Hi Vikash,
Unfortunately there's no log in dmesg when this happens, the phone just
freezes, I'm not sure right now whether it reboots into ramdump mode then.
But also for ramdump I haven't yet used the tools to debug such a crash,
so that wouldn't help me too much right now.
I can also try later to try and find what part of the code triggers
this, by adding some prints around the files, maybe that reveals a bit
of what's happening there.
Regards
Luca
prev parent reply other threads:[~2025-04-01 9:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6P5iXJOUxv3jsPGI11XbeZOagg2ht2Ws-WbN2HjXSFC_xeFgWyGM3a9T6y30gmys3KSxJF9Tv3f7jAehZ6AlOQ==@protonmail.internalid>
2025-03-28 15:22 ` Venus probe issues on SM6350 SoC Luca Weiss
2025-03-28 16:39 ` Bryan O'Donoghue
2025-03-31 6:43 ` Luca Weiss
2025-03-31 9:47 ` Bryan O'Donoghue
2025-04-01 7:28 ` Luca Weiss
2025-04-01 6:17 ` Vikash Garodia
2025-04-01 6:55 ` Vikash Garodia
2025-04-01 7:42 ` Luca Weiss
2025-04-01 9:21 ` Vikash Garodia
2025-04-01 9:40 ` Luca Weiss [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=D8V7BAC36W6I.127OOFAEB4N63@fairphone.com \
--to=luca.weiss@fairphone.com \
--cc=konradybcio@kernel.org \
--cc=linux-arm-msm@vger.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