From: "Linux regression tracking #update (Thorsten Leemhuis)" <regressions@leemhuis.info>
To: Matthias Kaehlcke <mka@chromium.org>,
Stanimir Varbanov <stanimir.varbanov@linaro.org>
Cc: linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-msm@vger.kernel.org,
Fritz Koenig <frkoenig@chromium.org>,
Nathan Hebert <nhebert@chromium.org>
Subject: Re: [PATCH 2/3] venus: firmware: Correct non-pix start and end addresses
Date: Mon, 20 Mar 2023 11:52:01 +0100 [thread overview]
Message-ID: <071cf060-9845-dbb4-0a5b-ac4e2183d6f6@leemhuis.info> (raw)
In-Reply-To: <b2007bc9-b05f-eb17-a373-9587b01d3788@leemhuis.info>
[TLDR: This mail in primarily relevant for Linux kernel regression
tracking. See link in footer if these mails annoy you.]
On 05.02.23 12:00, Linux kernel regression tracking (#adding) wrote:
> On 26.01.23 20:19, Matthias Kaehlcke wrote:
>> On Wed, Oct 05, 2022 at 11:37:29AM +0300, Stanimir Varbanov wrote:
>>
>> I found that this commit prevents the AOSS from entering sleep mode during
>> system suspend at least on sc7180 and sc7280. AOSS not entering sleep mode
>> leads to a (apparently significant) increase in S3 power consumption, on
>> trogdor and herobrine it prevents the system from staying suspended, because
>> the embedded controller detect the condition and wakes the sytem up again.
>
> Thanks for the report. To be sure the issue doesn't fall through the
> cracks unnoticed, I'm adding it to regzbot, the Linux kernel regression
> tracking bot:
>
> #regzbot ^introduced a837e5161cfffbb32
> #regzbot title meida: venus: firmware: AOSS doesn't seel anymore on at
> least sc7180 and sc7280
> #regzbot ignore-activity
#regzbot fix: media: Revert "venus: firmware: Correct non-pix start and
end addresses"
#regzbot ignore-activity
Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
--
Everything you wanna know about Linux kernel regression tracking:
https://linux-regtracking.leemhuis.info/about/#tldr
That page also explains what to do if mails like this annoy you.
next prev parent reply other threads:[~2023-03-20 10:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-05 8:37 [PATCH 0/3] Few corrections in non-tz firmware boot Stanimir Varbanov
2022-10-05 8:37 ` [PATCH 1/3] venus: firmware: Correct reset bit Stanimir Varbanov
2022-10-05 8:37 ` [PATCH 2/3] venus: firmware: Correct non-pix start and end addresses Stanimir Varbanov
2023-01-26 19:19 ` Matthias Kaehlcke
2023-02-02 16:39 ` [REGRESSION][PATCH " Matthias Kaehlcke
2023-02-05 11:00 ` [PATCH " Linux kernel regression tracking (#adding)
2023-02-11 14:23 ` Linux regression tracking #update (Thorsten Leemhuis)
2023-03-20 10:52 ` Linux regression tracking #update (Thorsten Leemhuis) [this message]
2023-04-05 12:45 ` Linux regression tracking #update (Thorsten Leemhuis)
2022-10-05 8:37 ` [PATCH 3/3] venus: firmware: Correct assertion of reset bit on remote processor Stanimir Varbanov
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=071cf060-9845-dbb4-0a5b-ac4e2183d6f6@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=frkoenig@chromium.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mka@chromium.org \
--cc=nhebert@chromium.org \
--cc=regressions@lists.linux.dev \
--cc=stanimir.varbanov@linaro.org \
/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).