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 X-Spam-Level: X-Spam-Status: No, score=-0.8 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id CBC5FC433DF for ; Tue, 19 May 2020 09:04:09 +0000 (UTC) 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 mail.kernel.org (Postfix) with ESMTPS id 723E7208A7 for ; Tue, 19 May 2020 09:04:09 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lists.infradead.org header.i=@lists.infradead.org header.b="uXX0eVua"; dkim=fail reason="signature verification failed" (1024-bit key) header.d=mg.codeaurora.org header.i=@mg.codeaurora.org header.b="xD8kfojI" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 723E7208A7 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=codeaurora.org Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-arm-kernel-bounces+infradead-linux-arm-kernel=archiver.kernel.org@lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20170209; h=Sender:Content-Type: Content-Transfer-Encoding:Cc:List-Subscribe:List-Help:List-Post:List-Archive: List-Unsubscribe:List-Id:Message-ID:References:In-Reply-To:Subject:To:From: Date:MIME-Version:Reply-To:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=/QYtr+TVQUf+Zyv3Yu7ZIVYS+Xe0XcUaXavzZhTJM8o=; b=uXX0eVuaRBlAw59WhFuPn0Qaf Fsi1uB2dirLXtqPKLfRDpOkhHdOQ3tOQthGjjPleVkYyl9DdqqKkEzcKPhizaYLkTx87OlLhTo+er rHWQY9tbR/RlZwN1NAbKYqU5qkhQ/Zf7U/uNCfTC9qy//YCfLcWJWQsxLj2Vk3ApqmWYlC1qq+qX/ LEI55gCjfX1ggUK/i8brhVjNChwNd/RklRODLqFk/JBYyeewKCP4jIXJ8BpkwJ4g0cfZsR584yhYF PschZ1692wEGhEofQsnpPiB160KQQXmu8i1YQq1bovl970pQWlasexfXetw9dWmAaEVyk40Y3Wdss NPOTtjK4w==; Received: from localhost ([127.0.0.1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.92.3 #3 (Red Hat Linux)) id 1jayAS-000344-PN; Tue, 19 May 2020 09:04:08 +0000 Received: from mail26.static.mailgun.info ([104.130.122.26]) by bombadil.infradead.org with esmtps (Exim 4.92.3 #3 (Red Hat Linux)) id 1jayAP-00033Y-2W for linux-arm-kernel@lists.infradead.org; Tue, 19 May 2020 09:04:06 +0000 DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=mg.codeaurora.org; q=dns/txt; s=smtp; t=1589879044; h=Message-ID: References: In-Reply-To: Subject: Cc: To: From: Date: Content-Transfer-Encoding: Content-Type: MIME-Version: Sender; bh=krynLA3PVnStDQ90BA4lcITyrT/iSvbyv+EPo/hP2Ao=; b=xD8kfojI23VeZoWICAeTA9/BYpbIO1f+Mi6Ec9LImEC6hTRl8r9h2LV2TczcE8+6RlEySxTu adPU4z8EZqHERVfWeUAyI1B3otDKVr+rZWS8YfnQz1OTiXE+uIUlJiQ7pLcj9bBK5zLTSeoQ KvPYau0sVUpEOG1ATWW7xekSUU4= X-Mailgun-Sending-Ip: 104.130.122.26 X-Mailgun-Sid: WyJiYzAxZiIsICJsaW51eC1hcm0ta2VybmVsQGxpc3RzLmluZnJhZGVhZC5vcmciLCAiYmU5ZTRhIl0= Received: from smtp.codeaurora.org (ec2-35-166-182-171.us-west-2.compute.amazonaws.com [35.166.182.171]) by mxa.mailgun.org with ESMTP id 5ec3a103.7fdb70c8b960-smtp-out-n02; Tue, 19 May 2020 09:04:03 -0000 (UTC) Received: by smtp.codeaurora.org (Postfix, from userid 1001) id 83755C43636; Tue, 19 May 2020 09:04:03 +0000 (UTC) Received: from mail.codeaurora.org (localhost.localdomain [127.0.0.1]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: saiprakash.ranjan) by smtp.codeaurora.org (Postfix) with ESMTPSA id 14B85C433D2; Tue, 19 May 2020 09:04:03 +0000 (UTC) MIME-Version: 1.0 Date: Tue, 19 May 2020 14:34:03 +0530 From: Sai Prakash Ranjan To: Mike Leach , Suzuki K Poulose , Mathieu Poirier Subject: Re: [PATCH] coresight: dynamic-replicator: Fix handling of multiple connections In-Reply-To: <4bd741e342f8e2743197ed6105dacffa@codeaurora.org> References: <20200426143725.18116-1-saiprakash.ranjan@codeaurora.org> <84918e7d-c933-3fa1-a61e-0615d4b3cf2c@arm.com> <668ea1283a6dd6b34e701972f6f71034@codeaurora.org> <5b0f5d77c4eec22d8048bb0ffa078345@codeaurora.org> <759d47de-2101-39cf-2f1c-cfefebebd548@arm.com> <7d343e96cf0701d91152fd14c2fdec42@codeaurora.org> <47f6d51bfad0a0bf1553e101e6a2c8c9@codeaurora.org> <37b3749e-2363-0877-c318-9c334a5d1881@arm.com> <364049a30dc9d242ec611bf27a16a6c9@codeaurora.org> <5a76926a6532d3f91cca169d474ba98e@codeaurora.org> <4bd741e342f8e2743197ed6105dacffa@codeaurora.org> Message-ID: <825b922dab9821fa46f321d600648e10@codeaurora.org> X-Sender: saiprakash.ranjan@codeaurora.org User-Agent: Roundcube Webmail/1.3.9 X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20200519_020405_205107_166A0BE0 X-CRM114-Status: GOOD ( 14.20 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Russell King , linux-arm-msm@vger.kernel.org, Linux Kernel Mailing List , linux-arm-kernel , Stephen Boyd Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+infradead-linux-arm-kernel=archiver.kernel.org@lists.infradead.org Hi Mike, Suzuki, On 2020-05-16 15:34, Sai Prakash Ranjan wrote: > Hi Mike, Suzuki > > [...] > >>> >>> Please look at the CoreSight components specification 3.0 (ARM IHI >>> 0029E) Section B2.1.2 which describes the Unique Component Identifier >>> (UCI). >>> As mentioned above this consists of a combination of bits from >>> multiple registers, including PIDR4. >>> >> >> Ok got it now, thanks for clearing the doubt. I will go ahead with >> this method to identify QCOM impl and post a patch. >> > > Looking some more into this, since we have this limitation only on > specific replicator on very few QCOM SoCs, rather than having a blanket > workaround for all QCOM, we were thinking it would be better to have > this workaround based on a firmware property something like > "qcom,replicator-loses-context" for those replicators with this > limitation and then set the drvdata->check_idfilter_val based on > this property. > Sorry for going back and forth on this one, but I think having a firmware property will clearly help us identify the issue on specific SoCs rather than wholesale workaround for all QCOM SoCs. For now, I will post a patch based on the property "qcom,replicator-loses-context", please feel free to yell at me if this is completely wrong and we can discuss it further in that patch. Thanks, Sai -- QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel