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 vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 298B8C64ED8 for ; Mon, 27 Feb 2023 10:44:51 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230111AbjB0Kot (ORCPT ); Mon, 27 Feb 2023 05:44:49 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:50448 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229894AbjB0Kon (ORCPT ); Mon, 27 Feb 2023 05:44:43 -0500 Received: from foss.arm.com (foss.arm.com [217.140.110.172]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id 82465B455; Mon, 27 Feb 2023 02:44:41 -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 511B5C14; Mon, 27 Feb 2023 02:45:24 -0800 (PST) Received: from [10.57.91.127] (unknown [10.57.91.127]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 2B4E83F881; Mon, 27 Feb 2023 02:44:38 -0800 (PST) Message-ID: <3c3c55a8-8979-76f9-3b61-31c50ceefd33@arm.com> Date: Mon, 27 Feb 2023 10:44:28 +0000 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:102.0) Gecko/20100101 Thunderbird/102.7.2 Subject: Re: [PATCH v2 1/9] dt-bindings: arm: Add support for DSB element To: Tao Zhang , Mathieu Poirier , Alexander Shishkin , Konrad Dybcio , Mike Leach , Rob Herring , Krzysztof Kozlowski Cc: Jinlong Mao , Leo Yan , Greg Kroah-Hartman , coresight@lists.linaro.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, devicetree@vger.kernel.org, Tingwei Zhang , Yuanfang Zhang , Trilok Soni , Hao Zhang , linux-arm-msm@vger.kernel.org, bjorn.andersson@linaro.org, Tao Zhang References: <1674114105-16651-1-git-send-email-quic_taozha@quicinc.com> <1674114105-16651-2-git-send-email-quic_taozha@quicinc.com> <7195d3dd-8c39-00c5-5037-5d6d01698cf5@quicinc.com> From: Suzuki K Poulose In-Reply-To: <7195d3dd-8c39-00c5-5037-5d6d01698cf5@quicinc.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 27/02/2023 03:07, Tao Zhang wrote: > Hi Suzuki, > > 在 2/22/2023 2:11 AM, Suzuki K Poulose 写道: >> On 19/01/2023 07:41, Tao Zhang wrote: >>> Add property "qcom,dsb-elem-size" to support DSB(Discrete Single >>> Bit) element for TPDA. Specifies the DSB element size supported >>> by each monitor connected to the aggregator on each port. Should >>> be specified in pairs (port, dsb element size). >>> >>> Signed-off-by: Tao Zhang >>> Signed-off-by: Tao Zhang >>> --- >>>   .../bindings/arm/qcom,coresight-tpda.yaml          | 22 >>> ++++++++++++++++++++++ >>>   1 file changed, 22 insertions(+) >>> >>> diff --git >>> a/Documentation/devicetree/bindings/arm/qcom,coresight-tpda.yaml >>> b/Documentation/devicetree/bindings/arm/qcom,coresight-tpda.yaml >>> index 2ec9b5b..298db7f 100644 >>> --- a/Documentation/devicetree/bindings/arm/qcom,coresight-tpda.yaml >>> +++ b/Documentation/devicetree/bindings/arm/qcom,coresight-tpda.yaml >>> @@ -58,6 +58,26 @@ properties: >>>       minItems: 1 >>>       maxItems: 2 >>>   +  qcom,dsb-element-size: >>> +    description: | >>> +      Specifies the DSB(Discrete Single Bit) element size supported by >>> +      each monitor connected to the aggregator on each port. Should be >>> +      specified in pairs . >> >> Isn't this a property of the TPDM connected to the port ? i.e. the DSB >> size ? Thus shouldn't this be part of the TPDM device (and the TPDA >> will be able to find it from the TPDM device) ? >> > Since  the port number is about the input port of TPDA, this property > needs to be configured in the TPDA-related settings. That is because, you chose to describe the property of TPDM in TPDA ? Instead if you do it as follows : tpdm { qcom,tpdm-dsb-elemenet-size = <32> out_ports { port { remote-endpoint=<&tpda_port_number>; } } tpda { in_ports { port { remote-endpoint=<&tpdm0_port0>; } } } The TPDA driver can figure out the "port" that a given TPDM is connected to and thus find out the DSB size. For the tpda driver, pdata->conns could hold the reference to the TPDM device and thus fetch the DSB size. (Note: James is working on a patch to add input port connections to the platform data). Suzuki