From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id D47A7F89248 for ; Tue, 21 Apr 2026 10:03:35 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender:List-Subscribe:List-Help :List-Post:List-Archive:List-Unsubscribe:List-Id:In-Reply-To:Content-Type: MIME-Version:References:Message-ID:Subject:Cc:To:From:Date:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=1ymte7yWU6imnPYbHZd0E3auT708F3JtTDpYQVqDeeQ=; b=Rs2ubwlZYcsfUR0BX54EG6vP8I mr8mTftTkHhw5A7FnVhNygWKkEACIKBmXi1AO3A8d6g9tvXZNHVazHe3+Y8RGeDv1/VsOahVG+5Z8 Pjme8og3lfh5h3ffxgSGuQWf1eZRZIBpzrS4n+JGLgweW0uIS40Bg7qWMybzqSa5wc9ue3/CB0AVu Jskuaeqs2w4QpGPP2k0DvpU72sVj77Z8D82Ib+cL4b8jWADurmH6vH0igtCJQu9x4Wm4W/jTG+ckF Ar+VbZMsr2MszD5N5EhMl/VelF5zgTM17oWaWtH7X+0+eMRH7HO4JHxDbzFHJbCshMFY9cFN7JPJe thF4+I8Q==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.98.2 #2 (Red Hat Linux)) id 1wF7x6-00000008OqI-0Kx5; Tue, 21 Apr 2026 10:03:32 +0000 Received: from foss.arm.com ([217.140.110.172]) by bombadil.infradead.org with esmtp (Exim 4.98.2 #2 (Red Hat Linux)) id 1wF7wz-00000008Opi-2piY for linux-arm-kernel@lists.infradead.org; Tue, 21 Apr 2026 10:03:30 +0000 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 0A9B925DC; Tue, 21 Apr 2026 03:03:19 -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 2636C3F915; Tue, 21 Apr 2026 03:03:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=arm.com; s=foss; t=1776765804; bh=1ymte7yWU6imnPYbHZd0E3auT708F3JtTDpYQVqDeeQ=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=R60mC3LzWg2rAYU9AvmzP4L2y+w3o+qfzqVcSZIOG3rd/GT/Le4+lOVBgtM//7JD8 FpO6YEDQyMhp8fParKUfNlgRDqzyA6qh1rd1eo1i2fbSQvPGjW46YYp3/3DXB+oQjr N5e2FaD7Xz+5Wfx1FNQyCS+KQooK3EDs4crJZxj8= Date: Tue, 21 Apr 2026 11:03:20 +0100 From: Yeoreum Yun To: Mike Leach Cc: Suzuki K Poulose , Leo Yan , coresight@lists.linaro.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, james.clark@linaro.org, alexander.shishkin@linux.intel.com, jie.gan@oss.qualcomm.com Subject: Re: [PATCH v5 04/12] coresight: etm4x: exclude ss_status from drvdata->config Message-ID: References: <20260415165528.3369607-1-yeoreum.yun@arm.com> <20260415165528.3369607-5-yeoreum.yun@arm.com> <20260416155118.GM356832@e132581.arm.com> <57dbea1b-670b-4b8f-a590-1d4239bc2c76@arm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20260421_030325_848795_861BBB4B X-CRM114-Status: GOOD ( 12.32 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org Hi Mike, > Hi, > > This register [bit 31] indicates if a single shot comparator has matched. So > read-back provides information to the user post run to determine which if > any of the comparators set in this way has actually matched. Okay. so after disable sysfs session, to check former session check whether comprator has matched. > > Moreover, the specification states "Software must reset this bit to 0 to > re-enable single-shot control" and "Reset state is unknown. STATUS must be > written to set an initial state...." > > Therefore this register must be written as part of any configuration so > should be available in the drvdata->config for both read and write, But I don't think this is the reason for locate ss_status into "config" since its write purpose is not to configure but the "clear" former bit. That's why I think it's enough to clear when the new sysfs session starts. Am I missing something? Thanks! -- Sincerely, Yeoreum Yun