Received: by 2002:a25:824b:0:0:0:0:0 with SMTP id d11csp8634428ybn; Tue, 1 Oct 2019 10:55:00 -0700 (PDT) X-Google-Smtp-Source: APXvYqw/ZfbHYN4VaWQtR5G0lMXAYr46kB6ubzhx29mSMTzawQVavO4OAU6yhBF3+Kz10oGVtS+s X-Received: by 2002:aa7:c555:: with SMTP id s21mr27074801edr.151.1569952500896; Tue, 01 Oct 2019 10:55:00 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1569952500; cv=none; d=google.com; s=arc-20160816; b=hKTjKxd8Vjf2vndPABfK59VCHZ7qXQjI4uqvDV1yi88CQMUwUEV8iu5vm3SotQ9nK6 bgWiAXkjSLKaC8lZ28aM9OAwKRJ865zT0/Uj9K5SngSEAak44UsgD1LU0492+TshAlGj NFbB4/gJyRRld2qx5DnTHweQa0D6yGjA/8MGzf+aqlqkuFOEbaMm6PE/YNlz1eQKx7HJ ASXWRYrIuAo9DXQfRPFJM+P1eG8/ZoIwBsKYaAzUjBLbZMfXqtS+y6FeYwAmZUQhhhdv erHYETLdUUnc7zV6Ao5NBJEWDcoFxRBuEuIUE5sL4avHM19RHYJ0oQOe7QtY9RLSjpvZ DmzQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:message-id:references :in-reply-to:subject:cc:to:from:date:content-transfer-encoding :mime-version:dkim-signature:dkim-signature; bh=xJlMeIQRDFi4hL63uEjSA8LuJrews9acmghDK8DjApg=; b=n//ZLZJVjDupYlfzX493Lmj6zFwQdGFf7uTW0QrGYgcEW8hRGNULZ/7Ff75hde98GB j8k4bPqyp7APdHVa95D+3NoUF0Ep3uAqYqlMY2Qdm/RBSmObq87drYjkDgA65erPV9fM twCaei00D+JbgxTPJfqnKDNCK5XjMdCWufCrutJRBLJ7uhUlfpsi0XgAVnXJh2o2/t4d /jCGV0k7YDO1WS336a9agxZJh3VgngbEy0AKUXX7yPJtuovipZcSp96ovlQSGwC/qOCw OyGqZgDeobYmofgLivp4yGjuu6mTzfvN+gCp2atk/ag1XOjE5H2rpN724Xbkqyk118j0 8JQw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@codeaurora.org header.s=default header.b="oj2/PZIW"; dkim=pass header.i=@codeaurora.org header.s=default header.b=lTkHXHKu; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id f12si9645602ejj.108.2019.10.01.10.54.35; Tue, 01 Oct 2019 10:55:00 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@codeaurora.org header.s=default header.b="oj2/PZIW"; dkim=pass header.i=@codeaurora.org header.s=default header.b=lTkHXHKu; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730703AbfJARwS (ORCPT + 99 others); Tue, 1 Oct 2019 13:52:18 -0400 Received: from smtp.codeaurora.org ([198.145.29.96]:37462 "EHLO smtp.codeaurora.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725844AbfJARwR (ORCPT ); Tue, 1 Oct 2019 13:52:17 -0400 Received: by smtp.codeaurora.org (Postfix, from userid 1000) id 233ED61156; Tue, 1 Oct 2019 17:52:15 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=codeaurora.org; s=default; t=1569952336; bh=EqX6F8UDW8JnIw6Hk7q7L1dvCzSEMNOpUg0sXKY32yA=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=oj2/PZIWdgJsjvx+7sB/HBZhXwlRP+/bp7ky6LvLjqD4g9BiNDvcglCZ62SjD1tBq QAgX6+g9hprx8wVBP7v9QVjcT7vKvuZQPgA01lEQC46BDaHrF+QmyochFDLUPJwYM0 4m7xO8XStOzyEZlV7qC04Ce1g/yklG9gIRkBlQgg= X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on pdx-caf-mail.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.7 required=2.0 tests=ALL_TRUSTED,BAYES_00, DKIM_INVALID,DKIM_SIGNED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.codeaurora.org (localhost.localdomain [127.0.0.1]) by smtp.codeaurora.org (Postfix) with ESMTP id 104336083C; Tue, 1 Oct 2019 17:52:15 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=codeaurora.org; s=default; t=1569952335; bh=EqX6F8UDW8JnIw6Hk7q7L1dvCzSEMNOpUg0sXKY32yA=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=lTkHXHKunAsS8EWDCTk+X0f1W5i2eyWsNoTkfA4JrXjUWLAdpwvRUvZwQy/sqsCha kE/4opxhjU4rATlKtRc59y0kRLw3/N3qA8EqPvRggNEEkhrNsP+u2hClns35iEAvhg rCNeqT75U1nPhoOrRrPqkFZOS/g7yYIjD6ij5xpI= MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Tue, 01 Oct 2019 10:52:15 -0700 From: Sai Prakash Ranjan To: Jeffrey Hugo Cc: Mark Rutland , Rajendra Nayak , Mathieu Poirier , Suzuki K Poulose , Alexander Shishkin , MSM , Marc Gonzalez , lkml , Bjorn Andersson , David Brown , Andy Gross , Sibi Sankar , Leo Yan , linux-arm-kernel@lists.infradead.org Subject: Re: [PATCHv9 2/3] arm64: dts: qcom: msm8998: Add Coresight support In-Reply-To: References: <90114e06825e537c3aafd3de5c78743a9de6fadc.1564550873.git.saiprakash.ranjan@codeaurora.org> <16212a577339204e901cf4eefa5e82f1@codeaurora.org> Message-ID: X-Sender: saiprakash.ranjan@codeaurora.org User-Agent: Roundcube Webmail/1.2.5 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2019-10-01 10:14, Jeffrey Hugo wrote: > On Tue, Oct 1, 2019 at 11:04 AM Sai Prakash Ranjan > wrote: >> >> On 2019-10-01 09:13, Jeffrey Hugo wrote: >> > Sai, >> > >> > This patch breaks boot on the 835 laptops. However, I haven't seen >> > the same issue on the MTP. I wonder, is coresight expected to work >> > with production fused devices? I wonder if thats the difference >> > between the laptop and MTP that is causing the issue. >> > >> > Let me know what I can do to help debug. >> > >> >> I did test on MSM8998 MTP and didn't face any issue. I am guessing >> this >> is the same issue which you reported regarding cpuidle? Coresight ETM > > Yes, its the same issue. Right now, I need both patches reverted to > boot. > >> and cpuidle do not work well together since ETMs share the same power >> domain as CPU and they might get turned off when CPU enters idle >> states. >> Can you try with cpuidle.off=1 cmdline or just remove idle states from >> DT to confirm? If this is the issue, then we can try the below patch >> from Andrew Murray for ETM save and restore: >> >> https://patchwork.kernel.org/patch/11097893/ > > Is there still value in testing this if the idle states are removed, > yet the coresight nodes still cause issues? > > Funny enough, I'm using the arm64 defconfig which doesn't seem to > select CONFIG_CORESIGHT, so I'm not even sure what would be binding to > the DT devices... > Haan then likely it's the firmware issue. We should probably disable coresight in soc dtsi and enable only for MTP. For now you can add a status=disabled for all coresight nodes in msm8998.dtsi and I will send the patch doing the same in a day or two(sorry I am travelling currently). Thanks, Sai