From: "Linux regression tracking (Thorsten Leemhuis)" <regressions@leemhuis.info>
To: Mauro Carvalho Chehab <mchehab@kernel.org>
Cc: Vikash Garodia <vgarodia@qti.qualcomm.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"mka@chromium.org" <mka@chromium.org>,
Albert Esteve <aesteve@redhat.com>,
"stanimir.varbanov@linaro.org" <stanimir.varbanov@linaro.org>,
Enric Balletbo i Serra <eballetb@redhat.com>,
Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Stanimir Varbanov <stanimir.k.varbanov@gmail.com>,
"Vikash Garodia (QUIC)" <quic_vgarodia@quicinc.com>,
"linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>,
"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
Fritz Koenig <frkoenig@google.com>,
"Dikshita Agarwal (QUIC)" <quic_dikshita@quicinc.com>,
"Rajeshwar Kurapaty (QUIC)" <quic_rkurapat@quicinc.com>,
Javier Martinez Canillas <javierm@redhat.com>,
Linux regressions mailing list <regressions@lists.linux.dev>
Subject: Re: [PATCH] Revert "venus: firmware: Correct non-pix start and end addresses"
Date: Wed, 15 Feb 2023 14:18:29 +0100 [thread overview]
Message-ID: <b548da46-bf91-6f1c-4b63-4002109056bc@leemhuis.info> (raw)
In-Reply-To: <CAFOAJEdBbzqkGVqw+vgNYNxyaTHwvjFyskTwjycP820L2tOctA@mail.gmail.com>
On 15.02.23 11:57, Javier Martinez Canillas wrote:
> On Wed, Feb 15, 2023 at 11:53 AM Linux regression tracking (Thorsten
> Leemhuis) <regressions@leemhuis.info> wrote:
>> On 11.02.23 15:27, Linux regression tracking (Thorsten Leemhuis) wrote:
>>> On 10.02.23 11:07, Javier Martinez Canillas wrote:
>>>> On 2/10/23 10:22, Vikash Garodia wrote:
>>>>
>>>>>> So what should we do about this folks? Since not allowing the driver to probe on
>>>>>> at least SC7180 is a quite serious regression, can we revert for now until a proper
>>>>>> fix is figured out?
>>>>> I am able to repro this issue on sc7180 and discussing with firmware team on the cause
>>>>> of reset failure. The original patch was raised for fixing rare SMMU faults during warm
>>>>> boot of video hardware. Hence looking to understand the regressing part before we
>>>>> proceed to revert.
>>>> Great, if you are working on a proper fix then that would be much better indeed.
>>> Yeah, that's great, but OTOH: there is almost certainly just one week
>>> before 6.2 will be released. Ideally this should be fixed by then.
>>> Vikash, do you think that's in the cards? If not: why not revert this
>>> now to make sure 6.2 works fine?
>> Hmm, no reply. And we meanwhile have Wednesday and 6.2 is almost
>> certainly going to be out on Sunday. And the problem was called "a quite
>> serious regression" above. So why not quickly fix this with the revert,
>> as proposed earlier?
>> Vikash? Javier?
>
> I agree with you, that we should land this revert and then properly
> fix the page fault issue in v6.3.
>
> But it's not my call, the v4l2/media folks have to decide that.
In that case: Mauro, what's your opinion here?
Thread starts here:
https://lore.kernel.org/lkml/20230207102254.1446461-1-javierm@redhat.com/
Regression report:
https://lore.kernel.org/lkml/Y9LSMap%2BjRxbtpC8@google.com/
Ciao, Thorsten
next prev parent reply other threads:[~2023-02-15 13:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230207102254.1446461-1-javierm@redhat.com>
[not found] ` <DM8PR02MB8169809493BF2822E6C29EECF3DB9@DM8PR02MB8169.namprd02.prod.outlook.com>
[not found] ` <ef09bc9f-d570-be11-238b-bd34063917fc@redhat.com>
[not found] ` <70c01751-1dd7-c4bd-a96e-94dea437aa40@redhat.com>
[not found] ` <DM8PR02MB81696369DBFE619E43F81EEFF3DE9@DM8PR02MB8169.namprd02.prod.outlook.com>
[not found] ` <e87344c6-acef-7f3f-5cac-24961dbd9401@redhat.com>
[not found] ` <6f97a117-0d9c-e21b-9adf-50f2233ba9e3@leemhuis.info>
[not found] ` <ea283f0a-ca72-447e-ce87-68c1bbee793e@leemhuis.info>
2023-02-15 10:57 ` [PATCH] Revert "venus: firmware: Correct non-pix start and end addresses" Javier Martinez Canillas
2023-02-15 13:18 ` Linux regression tracking (Thorsten Leemhuis) [this message]
2023-02-21 15:03 ` Thorsten Leemhuis
2023-02-23 5:45 ` Vikash Garodia
2023-02-23 8:05 ` Javier Martinez Canillas
2023-02-28 16:03 ` Javier Martinez Canillas
[not found] ` <d18fac76-6b77-a446-5fe0-7236556e9187@quicinc.com>
[not found] ` <0c84724d-08d4-ddcb-5f71-4eb8261240c6@quicinc.com>
2023-03-06 10:43 ` Javier Martinez Canillas
2023-04-01 20:53 ` Leonard Lausen
2023-04-02 5:02 ` Linux regression tracking (Thorsten Leemhuis)
2023-04-03 6:32 ` Thorsten Leemhuis
2023-04-03 0:27 ` Leonard Lausen
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=b548da46-bf91-6f1c-4b63-4002109056bc@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=aesteve@redhat.com \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=eballetb@redhat.com \
--cc=frkoenig@google.com \
--cc=javierm@redhat.com \
--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=mka@chromium.org \
--cc=quic_dikshita@quicinc.com \
--cc=quic_rkurapat@quicinc.com \
--cc=quic_vgarodia@quicinc.com \
--cc=regressions@lists.linux.dev \
--cc=stanimir.k.varbanov@gmail.com \
--cc=stanimir.varbanov@linaro.org \
--cc=vgarodia@qti.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;
as well as URLs for NNTP newsgroup(s).