Received: by 2002:a05:6358:16cc:b0:ea:6187:17c9 with SMTP id r12csp902361rwl; Thu, 5 Jan 2023 06:13:58 -0800 (PST) X-Google-Smtp-Source: AMrXdXtcxwkY6VKoSa+BxJHQ8AG9E9LDcTWWSIRQWwUUpja+n4naWFIzswAwr/FlSs3IbotZsX7/ X-Received: by 2002:a62:1d0f:0:b0:581:b3b3:7717 with SMTP id d15-20020a621d0f000000b00581b3b37717mr26090641pfd.26.1672928038201; Thu, 05 Jan 2023 06:13:58 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1672928038; cv=none; d=google.com; s=arc-20160816; b=vaplbXKE9A2M3+ZekGBLdMZl7XQJuElkFeBi9gG3AD4QiHKYzZlKBObzKiRiFkzmpt ADdDImZdp8+fKhe9cBN8WCIUDBT/FjI4DsO4e9dkMi6shA/C1e2MNOiayjOkKgqYVzVX WZ1ke2xCrSptJ8B95b7K+U2PvRa4GLNKr6o0iKjyrLzGV3q3KYpqOIAv38ZUhyQx3Eu/ sizRbN9Um0Ffl6i4452V6xWnaN8j8P/O3yt3RLu+MIL37+4zlKHuZDZrVp+6vGicZiGk NeoWkYxgEjYsXbuHobfQGfuH7WRc4bBuWbLv43ZZSTtlWIKiJhNg/GrY4GC5CCFTqJhi NZZg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:in-reply-to:references :cc:to:from:content-language:subject:user-agent:mime-version:date :message-id; bh=LceOlShWOtsOicvFWlVGZL3Lt5fsJ7397h2xNqSJBiw=; b=RNyuv/oOlGIMJhucbuWHALrWDma3VxIYa2HYwZ47TyeIpVf0PBVr66kOmhdxM+of7T QAVpnWs/55ij105RvDtI2yX6uTeIGVV/GrHcjdhuwdqJAUJGXBt9GaRyOf3p5H7ppdrJ +ohBdSRKhL8/35lamNBF0pPNwXWo0/B4X9mO2dll9qHn9ynAhyPDCgprnHvLFuEmVozM Py+Te87384moXDqM7UVxlHYHf4Iufy5RgWfajEA4Nw3v4WxAYhh7RXmlJwBtX3CPUM/i ZtVT4C9+J+Fp51PY2/j1OwtmqBZogIfhcClbHE5MbnNMuN9/fBuYwtpI/Ku8+iGi5Odh BIiA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=arm.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id j125-20020a625583000000b005750855ff7dsi34541904pfb.107.2023.01.05.06.13.48; Thu, 05 Jan 2023 06:13:58 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=arm.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234244AbjAEN5m (ORCPT + 58 others); Thu, 5 Jan 2023 08:57:42 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:41774 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234048AbjAEN4w (ORCPT ); Thu, 5 Jan 2023 08:56:52 -0500 Received: from foss.arm.com (foss.arm.com [217.140.110.172]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id 457434A960; Thu, 5 Jan 2023 05:55:44 -0800 (PST) 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 A3E3215BF; Thu, 5 Jan 2023 05:56:25 -0800 (PST) Received: from [10.57.44.158] (unknown [10.57.44.158]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 2D2CC3F71A; Thu, 5 Jan 2023 05:55:42 -0800 (PST) Message-ID: <990b948f-11b3-2463-2d0c-be9d30d10328@arm.com> Date: Thu, 5 Jan 2023 13:55:40 +0000 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.4.2 Subject: Re: [PATCH] coresight: cti: Add PM runtime call in enable_store Content-Language: en-US From: James Clark To: Mao Jinlong Cc: coresight@lists.linaro.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, Tingwei , Yuanfang Zhang , Tao Zhang , Hao Zhang , linux-arm-msm@vger.kernel.org, Mathieu Poirier , Mike Leach , Alexander Shishkin References: <20221224141700.20891-1-quic_jinlmao@quicinc.com> <9a86f7cd-2dce-f27a-af21-d64318ca3ef7@arm.com> In-Reply-To: <9a86f7cd-2dce-f27a-af21-d64318ca3ef7@arm.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-7.1 required=5.0 tests=BAYES_00,NICE_REPLY_A, RCVD_IN_DNSWL_MED,SPF_HELO_NONE,SPF_NONE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 04/01/2023 13:11, James Clark wrote: > > > On 24/12/2022 14:17, Mao Jinlong wrote: >> In commit 6746eae4bbad ("coresight: cti: Fix hang in cti_disable_hw()") >> PM runtime calls are removed from cti_enable_hw/cti_disable_hw. When >> enabling CTI by writing enable sysfs node, clock for accessing CTI >> register won't be enabled. Device will crash due to register access >> issue. Add PM runtime call in enable_store to fix this issue. >> >> Signed-off-by: Mao Jinlong >> --- >> drivers/hwtracing/coresight/coresight-cti-sysfs.c | 11 +++++++++-- >> 1 file changed, 9 insertions(+), 2 deletions(-) >> >> diff --git a/drivers/hwtracing/coresight/coresight-cti-sysfs.c b/drivers/hwtracing/coresight/coresight-cti-sysfs.c >> index 6d59c815ecf5..b1ed424ae043 100644 >> --- a/drivers/hwtracing/coresight/coresight-cti-sysfs.c >> +++ b/drivers/hwtracing/coresight/coresight-cti-sysfs.c >> @@ -108,10 +108,17 @@ static ssize_t enable_store(struct device *dev, >> if (ret) >> return ret; >> >> - if (val) >> + if (val) { >> + ret = pm_runtime_resume_and_get(dev->parent); >> + if (ret) >> + return ret; >> ret = cti_enable(drvdata->csdev); >> - else >> + if (ret) >> + pm_runtime_put(dev->parent); >> + } else { >> ret = cti_disable(drvdata->csdev); >> + pm_runtime_put(dev->parent); > > Hi Jinlong, > > This new pm_runtime_put() causes this when writing 0 to enable: > > [ 483.253814] coresight-cti 23020000.cti: Runtime PM usage count > underflow! > > Maybe we can modify cti_disable_hw() to return a value to indicate that > the disable actually happened, and only then call pm_runtime_put(). > > I suppose you could also check in the store function if it was already > enabled first, but then I don't know what kind of locking that would > need? cti_disable_hw() already seems to have a couple of locks, so maybe > the return value solution is easiest. > We've also just seen another issue where multiple calls to cti_disable_hw() can cause enable_req_count to go negative. I'm going to work on a few fixes (including yours) to make sure that it's complete and post it shortly. James