All of lore.kernel.org
 help / color / mirror / Atom feed
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: Mon, 23 Jun 2025 16:59:37 +0800	[thread overview]
Message-ID: <20250623085937.894003-1-keyz@google.com> (raw)
In-Reply-To: <20250620101906.3762866-1-keyz@google.com>

> 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 ?

I tried this in our environment, and this worked well. The "arm,coresight-loses-context-with-cpu" property was what we needed.
Thank you so much again for the swift response with the useful information!

Best,
Keita

  reply	other threads:[~2025-06-23  8:59 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
2025-06-23  8:59     ` Keita Morisaki [this message]
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=20250623085937.894003-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 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.