linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stanimir Varbanov <stanimir.varbanov@linaro.org>
To: linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-msm@vger.kernel.org
Cc: Stanimir Varbanov <stanimir.varbanov@linaro.org>
Subject: [PATCH 0/3] Few corrections in non-tz firmware boot
Date: Wed,  5 Oct 2022 11:37:27 +0300	[thread overview]
Message-ID: <20221005083730.963322-1-stanimir.varbanov@linaro.org> (raw)

Here are 3 patches which corrects reset bits, non-pix memory region and
use writel/readl with memory barriers included.

Those patches in fact fixes iommu context faults seen on Chromebook
(sc7180) during testing suspend/resume.

Stanimir Varbanov (3):
  venus: firmware: Correct reset bit
  venus: firmware: Correct non-pix start and end addresses
  venus: firmware: Correct assertion of reset bit on remote processor

 drivers/media/platform/qcom/venus/firmware.c | 20 ++++++++++----------
 1 file changed, 10 insertions(+), 10 deletions(-)

-- 
2.25.1


             reply	other threads:[~2022-10-05  8:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-05  8:37 Stanimir Varbanov [this message]
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)
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=20221005083730.963322-1-stanimir.varbanov@linaro.org \
    --to=stanimir.varbanov@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.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).