From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from foss.arm.com (foss.arm.com [217.140.110.172]) by smtp.subspace.kernel.org (Postfix) with ESMTP id DB76D37F75B for ; Wed, 8 Apr 2026 09:07:08 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=217.140.110.172 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1775639232; cv=none; b=fzgntvvMnNSXdjjXoIkXhHgJiu1meXG1p54rf+rl7OZW+dwLs8mdUBVdFb2jwmTTCf4uJgtBulzIMCC57Lgai9lOSPNV9VXyJufHJm48zYKpyFM+WrY5KoP3jQiQ9ZU+aWLzTjg8Ww4igqKd34yURG1u2IhWMhg/Xaqn945RXSE= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1775639232; c=relaxed/simple; bh=W5LEguNCP4i5z7VzNmBYP1xbD/RZ4RT18i4OzYMTBT0=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=Tjc3DkpjILNF6vg58md5u9k31lCORHNjSyDzJIoKGriJe9oJrT90N7YCjNNzKcU5gxfp1O2RzA8MKM3spK3ANa3VOII+q55pf6eJ0r2B9lswxk7yVkVw05ugl1y90IfsHv9wcXObMNekidSLautjzwEv70C5Eg/9xW5pEWvbNGA= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=arm.com; spf=pass smtp.mailfrom=arm.com; dkim=pass (1024-bit key) header.d=arm.com header.i=@arm.com header.b=Gc5iu3VS; arc=none smtp.client-ip=217.140.110.172 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=arm.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=arm.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=arm.com header.i=@arm.com header.b="Gc5iu3VS" Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id C43AE293B; Wed, 8 Apr 2026 02:07:01 -0700 (PDT) Received: from e129823.arm.com (e129823.arm.com [10.1.197.6]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 05A443F641; Wed, 8 Apr 2026 02:07:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=arm.com; s=foss; t=1775639227; bh=W5LEguNCP4i5z7VzNmBYP1xbD/RZ4RT18i4OzYMTBT0=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=Gc5iu3VSYOasYG43MFYMUiI7Junj2YNPfM/1eL6e46J1NtvvOTE6nLBMmaWH84QXX EIKRs29ubUpoie2xV/JMp9WNRGBE6pFz7HJiCOj5G3TxNIzrKQ3ZX4/2GAUotZ7jpm AA+ONrRgQOH4qQRq7+0x3aCinXMqGqfpsHuXRuQU= Date: Wed, 8 Apr 2026 10:07:03 +0100 From: Yeoreum Yun To: Suzuki K Poulose Cc: coresight@lists.linaro.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, mike.leach@linaro.org, james.clark@linaro.org, alexander.shishkin@linux.intel.com, leo.yan@arm.com Subject: Re: [PATCH 1/2] coresight: etm4x: fix inconsistencies with sysfs configration Message-ID: References: <20260317181705.2456271-1-yeoreum.yun@arm.com> <20260317181705.2456271-2-yeoreum.yun@arm.com> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Hi Suzuki, [...] > > > > > To resolve these inconsistencies, the configuration should be separated into: > > > > - active_config, which represents the currently applied configuration > > To be more precise, it is the "Applied configuration for the current > session" Thanks for suggestion. I'll change it. > > > - config, which stores the settings configured via sysfs. > > While we are at it, should we stop using the drvdata->config for the > "capabilities" for the ETM (e.g., TRCSSCSRn in ss_status ?) Instead > we could save it in "drvdata->ss_status". This keeps everything > separated: > > 1. Boot time probed capabilities of ETM > 2. Sysfs configuration for the next Run > 3. Current active configuration for the ETM (sysfs or perf) Agree. with the Leo's suggestion, I'll change it. Thanks! [...]