Linux ARM-MSM sub-architecture
 help / color / mirror / Atom feed
From: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
To: Marc Gonzalez <mgonzalez@freebox.fr>,
	Vikash Garodia <quic_vgarodia@quicinc.com>,
	Stanimir Varbanov <stanimir.k.varbanov@gmail.com>,
	Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
	Konrad Dybcio <konrad.dybcio@linaro.org>
Cc: linux-media <linux-media@vger.kernel.org>,
	MSM <linux-arm-msm@vger.kernel.org>,
	Bjorn Andersson <andersson@kernel.org>,
	Jeffrey Hugo <quic_jhugo@quicinc.com>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	Pierre-Hugues Husson <phh@phh.me>,
	Marijn Suijten <marijn.suijten@somainline.org>
Subject: Re: [RFC WIP PATCH] venus: add qcom,no-low-power property
Date: Thu, 11 Apr 2024 10:02:28 +0100	[thread overview]
Message-ID: <b93ff9ea-367c-4382-bce2-4c8fa95cb849@linaro.org> (raw)
In-Reply-To: <bd49cfcd-13d2-4e4f-bc9d-c491558e5af7@linaro.org>

On 10/04/2024 14:14, Bryan O'Donoghue wrote:
> On 10/04/2024 13:23, Marc Gonzalez wrote:
>> FWIW, I get the same behavior with 854x480 and 2560x1440:
>>
>> 1) If mpv runs with '--length=N' (play only part of the file)
>> then mpv exits cleanly, with no kernel messages.
> 
> On -next ?
> 
> I think you mentioned before you were doing your work on an older kernel 
> and forward porting patches ?
> 
>> 2) If mpv plays the entire file, then mpv hangs at the end
>> (needs CTRL-C to exit) and driver prints to kernel:
>> [68643.935888] qcom-venus cc00000.video-codec: session error: event 
>> id:1001 (deadb000), session id:79d42000
>> [68643.935995] qcom-venus-decoder cc00000.video-codec:video-decoder: 
>> dec: event : 1001
> 
> Hmm
> 
> #define HFI_ERR_SESSION_FATAL                0x1001
> 
> Something is causing the firmware to return this packet to you.
> 
> Probably worth tracing the last five messages sent by the firmware prior 
> to that to see if we can root-cause.
> 
> ---
> bod

BTW I think you've found two bugs here

1. When we receive a fatal error from firmware we don't "bug out"
    properly. So we hang forever waiting for more events which
    won't come.
    We should fix the handling of SESSION_FATAL to => termination.
    Clearly after HFI_ERR_SESSION_FATAL we should be completely done
    not hanging around waiting for additional inputs.

2. Why do we get a fatal error for the session ?
    Are we continuing to send commands to the firmware after
    termination maybe - so is there a incongruous context
    between firmware and Linux ?

I don't think either is a blocker specifically for your DTS submission 
so I think you should go ahead with your DTS stuff.

Also though, I think 1) we don't exit properly on HFI_ERR_SESSION_FATAL 
and 2) we should root-cause why HFI_ERR_SESSION_FATAL is generated at all.

---
bod

  parent reply	other threads:[~2024-04-11  9:02 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-19 17:18 [RFC WIP PATCH] venus: add qcom,no-low-power property Marc Gonzalez
2024-02-19 17:28 ` Konrad Dybcio
2024-02-19 17:44   ` Dmitry Baryshkov
2024-02-19 19:24     ` Bryan O'Donoghue
2024-02-20 10:56       ` Marc Gonzalez
2024-02-20 11:21         ` Bryan O'Donoghue
2024-02-20 11:37           ` Krzysztof Kozlowski
2024-02-20 12:34             ` Marc Gonzalez
2024-02-20 13:27               ` Krzysztof Kozlowski
2024-02-20 13:53                 ` Vikash Garodia
2024-02-20 14:45                   ` Marc Gonzalez
2024-02-23 13:48                     ` Vikash Garodia
2024-02-26 13:09                       ` Marc Gonzalez
2024-02-26 14:30                         ` Vikash Garodia
2024-02-26 15:55                           ` Marc Gonzalez
2024-02-27  6:55                             ` Vikash Garodia
2024-02-27 16:11                               ` Marc Gonzalez
2024-02-29 15:32                                 ` Vikash Garodia
2024-02-29 16:24                                   ` Marc Gonzalez
2024-02-29 16:47                                     ` Jeffrey Hugo
2024-03-12 18:39                                     ` Konrad Dybcio
2024-04-10 10:24                                       ` Vikash Garodia
2024-04-08 15:39                                   ` Marc Gonzalez
2024-04-09 11:27                                     ` Bryan O'Donoghue
2024-04-09 14:09                                       ` Marc Gonzalez
2024-04-09 16:53                                       ` Marc Gonzalez
2024-04-10  8:17                                         ` Bryan O'Donoghue
2024-04-10 10:34                                           ` Vikash Garodia
2024-04-10 12:23                                           ` Marc Gonzalez
2024-04-10 13:14                                             ` Bryan O'Donoghue
2024-04-10 13:18                                               ` Marc Gonzalez
2024-04-10 13:29                                                 ` Bryan O'Donoghue
2024-04-10 13:31                                                   ` Bryan O'Donoghue
2024-04-11  9:02                                               ` Bryan O'Donoghue [this message]
2024-04-25 16:43                                               ` Marc Gonzalez
2024-04-30 16:13                                                 ` venus decoder hangs at EOF Marc Gonzalez
2024-02-19 18:33 ` [RFC WIP PATCH] venus: add qcom,no-low-power property Rob Herring

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=b93ff9ea-367c-4382-bce2-4c8fa95cb849@linaro.org \
    --to=bryan.odonoghue@linaro.org \
    --cc=andersson@kernel.org \
    --cc=dmitry.baryshkov@linaro.org \
    --cc=konrad.dybcio@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=marijn.suijten@somainline.org \
    --cc=mchehab@kernel.org \
    --cc=mgonzalez@freebox.fr \
    --cc=phh@phh.me \
    --cc=quic_jhugo@quicinc.com \
    --cc=quic_vgarodia@quicinc.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox