From: Keita Morisaki <keyz@google.com>
To: suzuki.poulose@arm.com
Cc: alexander.shishkin@linux.intel.com, coresight@lists.linaro.org,
ericchancf@google.com, james.clark@linaro.org, keyz@google.com,
leo.yan@arm.com, linux-kernel@vger.kernel.org,
mike.leach@linaro.org, yimingtseng@google.com
Subject: Re: [BUG] CoreSight: WARN_ON in coresight_disclaim_device_unlocked due to register reset on CPU power-cycle
Date: Fri, 20 Jun 2025 18:19:06 +0800 [thread overview]
Message-ID: <20250620101906.3762866-1-keyz@google.com> (raw)
In-Reply-To: <9c5bf40a-b0d8-414c-a0c9-f5da5d9b612d@arm.com>
Hi,
(Resending the same message in plain text (no HTML). The previous message was rejected by the mailing list because it contained HTML.)
thank you so much for the quick response. Really appreciate it.
> Thanks for the report ! In the future, please use
> scripts/get_maintainer.pl for the clear list of people/list
> for reporting issues.
I will do that!
> We have the ETM driver performing the save/restore of ETM context during
> a CPUidle. This is only done when the ETM/ETE is described to be loosing
> context over PM operation. If this is not done (via DT), the driver
> doesn't do anything. This could be problematic. Could you try adding:
>
> "arm,coresight-loses-context-with-cpu"
>
>
> property to the ETE nodes and see if it makes a difference ?
Noted. We will try this and get back to you.
Best,
Keita
next prev parent reply other threads:[~2025-06-20 10:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAGo=-X1K1qZ_p9X0yeKy8Wm4QMDs2+4VE08LUNKOCrA15KFLTA@mail.gmail.com>
2025-06-20 8:44 ` [BUG] CoreSight: WARN_ON in coresight_disclaim_device_unlocked due to register reset on CPU power-cycle Suzuki K Poulose
2025-06-20 10:19 ` Keita Morisaki [this message]
2025-06-23 8:59 ` Keita Morisaki
2025-06-23 12:05 ` James Clark
2025-06-24 13:02 ` Leo Yan
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=20250620101906.3762866-1-keyz@google.com \
--to=keyz@google.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=coresight@lists.linaro.org \
--cc=ericchancf@google.com \
--cc=james.clark@linaro.org \
--cc=leo.yan@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mike.leach@linaro.org \
--cc=suzuki.poulose@arm.com \
--cc=yimingtseng@google.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