mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Suzuki K Poulose <suzuki.poulose@arm.com>
To: James Clark <james.clark@linaro.org>, Leo Yan <leo.yan@arm.com>
Cc: Mike Leach <mike.leach@arm.com>,
	Yeoreum Yun <yeoreum.yun@arm.com>,
	coresight@lists.linaro.org, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] coresight: trbe: Hide enable_sink sysfs file
Date: Tue, 11 Aug 2026 10:17:50 +0100	[thread overview]
Message-ID: <e138019e-5c7b-4ae3-837a-97cc95edb836@arm.com> (raw)
In-Reply-To: <7d4a7f0c-2b0e-471e-9c29-867bae981523@linaro.org>

On 11/08/2026 10:10, James Clark wrote:
> 
> 
> On 11/08/2026 10:04, Leo Yan wrote:
>> On Fri, Aug 07, 2026 at 11:13:22AM +0100, James Clark wrote:
>>> TRBE doesn't support sysfs mode, but the enable_sink file can still be
>>> successfully written to enable the device, and only attempting to enable
>>> the source would later fail.
>>>
>>> Avoid misleading users by adding a flag that devices can use to hide
>>> either the enable_sink or enable_source files, and set it for TRBE.
>>>
>>> Don't set it for ETE as it's possible that ETE could appear on the
>>> legacy bus and work with sysfs, and writing to enable_source already
>>> reports EINVAL if the device doesn't support sysfs mode.
>>
>> It is a pity that we cannot determine from the ETE registers whether ETE
>> is connected to the legacy bus or TRBE.
>>
> 
> We could determine it from the device tree. A path has to be built or 
> you can't use it on the legacy bus either. Maybe we can do a more 
> general change in the future to hide the flag for any non-connected CPU 
> source.


There must be a sink enabled before the source can be enabled. So, 
enable_source will fail. I would leave things as is, given the
sinks can be loaded with modules and it is all dynamic

Cheers
Suzuki


> 
>>> Signed-off-by: James Clark <james.clark@linaro.org>
>>
>> Reviewed-by: Leo Yan <leo.yan@arm.com>
> 


  reply	other threads:[~2026-08-11  9:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-07 10:13 James Clark
2026-08-11  9:04 ` Leo Yan
2026-08-11  9:10   ` James Clark
2026-08-11  9:17     ` Suzuki K Poulose [this message]
2026-10-01 14:10 ` Suzuki K Poulose

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=e138019e-5c7b-4ae3-837a-97cc95edb836@arm.com \
    --to=suzuki.poulose@arm.com \
    --cc=coresight@lists.linaro.org \
    --cc=james.clark@linaro.org \
    --cc=leo.yan@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mike.leach@arm.com \
    --cc=yeoreum.yun@arm.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®