mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Ulf Hansson <ulf.hansson@linaro.org>,
	Heiko Stuebner <heiko@sntech.de>,  Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	 Conor Dooley <conor+dt@kernel.org>,
	 Sebastian Reichel <sebastian.reichel@collabora.com>
Cc: "Liam Girdwood" <lgirdwood@gmail.com>,
	"Elaine Zhang" <zhangqing@rock-chips.com>,
	"Adrián Martínez Larumbe" <adrian.larumbe@collabora.com>,
	"Boris Brezillon" <boris.brezillon@collabora.com>,
	"Peter Geis" <pgwipeout@gmail.com>,
	"Tomeu Vizoso" <tomeu@tomeuvizoso.net>,
	"Vignesh Raman" <vignesh.raman@collabora.com>,
	linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
	linux-rockchip@lists.infradead.org, devicetree@vger.kernel.org
Subject: Re: (subset) [PATCH v6 0/8] Fix RK3588 power domain problems
Date: Tue, 25 Feb 2025 14:46:21 +0000	[thread overview]
Message-ID: <174049478169.62098.16182863254035343977.b4-ty@kernel.org> (raw)
In-Reply-To: <20250220-rk3588-gpu-pwr-domain-regulator-v6-0-a4f9c24e5b81@kernel.org>

On Thu, 20 Feb 2025 19:58:03 +0100, Sebastian Reichel wrote:
> I got a report, that the Linux kernel crashes on Rock 5B when the panthor
> driver is loaded late after booting. The crash starts with the following
> shortened error print:
> 
> rockchip-pm-domain fd8d8000.power-management:power-controller: failed to set domain 'gpu', val=0
> rockchip-pm-domain fd8d8000.power-management:power-controller: failed to get ack on domain 'gpu', val=0xa9fff
> SError Interrupt on CPU4, code 0x00000000be000411 -- SError
> 
> [...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next

Thanks!

[1/8] regulator: Add (devm_)of_regulator_get()
      commit: 0dffacbbf8d044456d50c893adb9499775c489f4

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.

Thanks,
Mark


  parent reply	other threads:[~2025-02-25 14:46 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-20 18:58 Sebastian Reichel
2025-02-20 18:58 ` [PATCH v6 1/8] regulator: Add (devm_)of_regulator_get() Sebastian Reichel
2025-02-25 17:59   ` Mark Brown
2025-02-28 12:11     ` Ulf Hansson
2025-02-20 18:58 ` [PATCH v6 2/8] pmdomain: rockchip: cleanup mutex handling in rockchip_pd_power Sebastian Reichel
2025-02-20 18:58 ` [PATCH v6 3/8] pmdomain: rockchip: forward rockchip_do_pmu_set_power_domain errors Sebastian Reichel
2025-02-20 18:58 ` [PATCH v6 4/8] pmdomain: rockchip: reduce indentation in rockchip_pd_power Sebastian Reichel
2025-02-20 18:58 ` [PATCH v6 5/8] pmdomain: rockchip: fix rockchip_pd_power error handling Sebastian Reichel
2025-02-20 18:58 ` [PATCH v6 6/8] dt-bindings: power: rockchip: add regulator support Sebastian Reichel
2025-02-20 18:58 ` [PATCH v6 7/8] pmdomain: " Sebastian Reichel
2025-02-20 18:58 ` [PATCH v6 8/8] arm64: dts: rockchip: Add GPU power domain regulator dependency for RK3588 Sebastian Reichel
2025-02-25 14:46 ` Mark Brown [this message]
2025-02-28 12:14 ` [PATCH v6 0/8] Fix RK3588 power domain problems Ulf Hansson
2025-02-28 13:46 ` (subset) " Heiko Stuebner

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=174049478169.62098.16182863254035343977.b4-ty@kernel.org \
    --to=broonie@kernel.org \
    --cc=adrian.larumbe@collabora.com \
    --cc=boris.brezillon@collabora.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=heiko@sntech.de \
    --cc=krzk+dt@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=pgwipeout@gmail.com \
    --cc=robh@kernel.org \
    --cc=sebastian.reichel@collabora.com \
    --cc=tomeu@tomeuvizoso.net \
    --cc=ulf.hansson@linaro.org \
    --cc=vignesh.raman@collabora.com \
    --cc=zhangqing@rock-chips.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

all inboxes | Powered by JetHome®