All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Bozeman <daniel@orb.net>
To: shawn.lin@rock-chips.com, finley.xiao@rock-chips.com,
	jonas@kwiboo.se, ulf.hansson@linaro.org, heiko@sntech.de,
	linux-pm@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] pmdomain/rockchip: skip QoS operations for idle-only domains
Date: Tue, 28 Apr 2026 01:32:17 +0000	[thread overview]
Message-ID: <afAOIfNcy73GC7lU@claude-dev> (raw)
In-Reply-To: <adRH235mv00OdOsb@claude-dev>

Hi Jonas,

Just following up — I have the NanoPi Zero2 on my bench and am
happy to run any tests if that would be helpful.

I can confirm the EPROBE_DEFER teardown crash is still
reproducible on your next-20260403-rk3528 branch (7.0-rc6)
with your conditional NO_STAY_ON fix applied. If you'd like
me to test a different approach or gather additional debug
output, just let me know.

Thanks,
Daniel


WARNING: multiple messages have this Message-ID (diff)
From: Daniel Bozeman <daniel@orb.net>
To: shawn.lin@rock-chips.com, finley.xiao@rock-chips.com,
	jonas@kwiboo.se, ulf.hansson@linaro.org, heiko@sntech.de,
	linux-pm@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] pmdomain/rockchip: skip QoS operations for idle-only domains
Date: Tue, 28 Apr 2026 01:32:17 +0000	[thread overview]
Message-ID: <afAOIfNcy73GC7lU@claude-dev> (raw)
In-Reply-To: <adRH235mv00OdOsb@claude-dev>

Hi Jonas,

Just following up — I have the NanoPi Zero2 on my bench and am
happy to run any tests if that would be helpful.

I can confirm the EPROBE_DEFER teardown crash is still
reproducible on your next-20260403-rk3528 branch (7.0-rc6)
with your conditional NO_STAY_ON fix applied. If you'd like
me to test a different approach or gather additional debug
output, just let me know.

Thanks,
Daniel

_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip

  reply	other threads:[~2026-04-28  1:32 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-31 18:02 [PATCH 1/2] pmdomain/rockchip: skip QoS operations for idle-only domains Daniel Bozeman
2026-03-31 18:02 ` Daniel Bozeman
2026-03-31 18:02 ` [PATCH 2/2] pmdomain/rockchip: skip domains returning -EPROBE_DEFER Daniel Bozeman
2026-03-31 18:02   ` Daniel Bozeman
2026-04-01  1:17 ` [PATCH 1/2] pmdomain/rockchip: skip QoS operations for idle-only domains Shawn Lin
2026-04-01  1:17   ` Shawn Lin
     [not found]   ` <CAG+Ngm+xJCCQMPddZx8AbPEeH3rUrn3GKF575zXpGPJrnELvMw@mail.gmail.com>
2026-04-01  2:54     ` Shawn Lin
2026-04-01  2:54       ` Shawn Lin
2026-04-01  6:13       ` Daniel Bozeman
2026-04-01  6:13         ` Daniel Bozeman
2026-04-01  7:11         ` Shawn Lin
2026-04-01  7:11           ` Shawn Lin
2026-04-03 21:27           ` Daniel Bozeman
2026-04-03 21:27             ` Daniel Bozeman
2026-04-04 11:40             ` Shawn Lin
2026-04-04 11:40               ` Shawn Lin
2026-04-04 22:42               ` Daniel Bozeman
2026-04-04 22:42                 ` Daniel Bozeman
2026-04-05 23:29               ` Jonas Karlman
2026-04-05 23:29                 ` Jonas Karlman
2026-04-06 23:55                 ` Daniel Bozeman
2026-04-06 23:55                   ` Daniel Bozeman
2026-04-28  1:32                   ` Daniel Bozeman [this message]
2026-04-28  1:32                     ` Daniel Bozeman
  -- strict thread matches above, loose matches on Subject: below --
2026-04-01  2:52 Daniel Bozeman

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=afAOIfNcy73GC7lU@claude-dev \
    --to=daniel@orb.net \
    --cc=finley.xiao@rock-chips.com \
    --cc=heiko@sntech.de \
    --cc=jonas@kwiboo.se \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=shawn.lin@rock-chips.com \
    --cc=ulf.hansson@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.