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=-2.2 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,URIBL_BLOCKED,USER_AGENT_MUTT autolearn=unavailable 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 4E01AC31E5D for ; Wed, 19 Jun 2019 18:39:14 +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 2B660214AF for ; Wed, 19 Jun 2019 18:39:14 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=lists.infradead.org header.i=@lists.infradead.org header.b="GBTDDgGo"; dkim=fail reason="signature verification failed" (2048-bit key) header.d=gerhold.net header.i=@gerhold.net header.b="ZkHVKPK7" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 2B660214AF Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=gerhold.net 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-Transfer-Encoding:Content-Type:Cc:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References: Message-ID:Subject:To:From:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=asvrEJZKot5x5AAHJ0LJkJzErY4IeVMN22EWsTmqMx4=; b=GBTDDgGoAbp0qW maI8Z22FLbaLXN8R5j9NVw33WyYuyV8h7YLWzW7JYgzvqVLimOnf+ekKd8GhFqYREv0ZpURASZsmo UtiIDiLbV3EV3FwC/aglrvDB6w0wnq4ytv0pySKgOaAHd0gxlKvxQLwSmRN+2F6ETATRCrRGQ/FeU vLP5yaW9MOIX01AKy+/Y7uDS8DfyhH9P2YlKUcYXq9Wnrt7EtoEEg44XV6zChjQal11e9NcyNySVd c1yBL+KCQ6Ux/ulYt3wJHPybKdsMJtE2VEGNI9M5cyE3BXiIf9IcNRXxfK5uoQmuOOq1YE2JJtSsj w2APl7BbpXk8kQFTCs6w==; Received: from localhost ([127.0.0.1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.92 #3 (Red Hat Linux)) id 1hdfUE-0006Kg-Ie; Wed, 19 Jun 2019 18:39:10 +0000 Received: from mo6-p00-ob.smtp.rzone.de ([2a01:238:20a:202:5300::9]) by bombadil.infradead.org with esmtps (Exim 4.92 #3 (Red Hat Linux)) id 1hdfUB-0006KG-LM for linux-arm-kernel@lists.infradead.org; Wed, 19 Jun 2019 18:39:09 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1560969545; s=strato-dkim-0002; d=gerhold.net; h=In-Reply-To:References:Message-ID:Subject:Cc:To:From:Date: X-RZG-CLASS-ID:X-RZG-AUTH:From:Subject:Sender; bh=yE9t/HpOhUCCw92yGlKlu+arbDgwr4eDSSJxIXUUaY0=; b=ZkHVKPK7jcxsewNjULrLMPbxeABqnHziLoCrr2T3ojot+NCPEPnSlEnuqahgZ3uetD wBpktQl8875oRGY9PNHSIibkeJfbMzw83AE0/F8H/zYk8rbB8mXJS5TAtOgvp8GCCTAu WRHVVWEOlADAsG0XcQpntdACurPCcqr6D26vhW4hSdnmi0S2BAf1vL/GBOg5tRzyVPK2 kvGzzJoO1wIlAZHXccNw+1gpZwX/394UFXQ6rxhhWOfg3zahlJ2dp6aN+bUfQXSO4QX5 3dgXPLW3nshxK89XDH5nW8T8W+ru71eBlPDMjcFGofA7PxAP7y/na/Lud6b2rhuH3iF+ mz1A== X-RZG-AUTH: ":P3gBZUipdd93FF5ZZvYFPugejmSTVR2nRPhVOQ/OcYgojyw4j34+u267EpF+OQRc4oDXF5yRxHE=" X-RZG-CLASS-ID: mo00 Received: from gerhold.net by smtp.strato.de (RZmta 44.24 AUTH) with ESMTPSA id m0a13fv5JId57Jh (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (curve secp521r1 with 521 ECDH bits, eq. 15360 bits RSA)) (Client did not present a certificate); Wed, 19 Jun 2019 20:39:05 +0200 (CEST) Date: Wed, 19 Jun 2019 20:39:04 +0200 From: Stephan Gerhold To: Suzuki K Poulose Subject: Re: Coresight causes synchronous external abort on msm8916 Message-ID: <20190619183904.GB937@gerhold.net> References: <20190618202623.GA53651@gerhold.net> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.12.0 (2019-05-25) X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20190619_113908_303278_53F90A48 X-CRM114-Status: GOOD ( 22.26 ) 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: david.brown@linaro.org, agross@kernel.org, linux-arm-kernel@lists.infradead.org, mathieu.poirier@linaro.org, linux-arm-msm@vger.kernel.org Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+infradead-linux-arm-kernel=archiver.kernel.org@lists.infradead.org Hi, On Wed, Jun 19, 2019 at 09:49:03AM +0100, Suzuki K Poulose wrote: > Hi Stephan, > > On 18/06/2019 21:26, Stephan Gerhold wrote: > > Hi, > > > > I'm trying to run mainline Linux on a smartphone with MSM8916 SoC. > > It works surprisingly well, but the coresight devices seem to cause the > > following crash shortly after userspace starts: > > > > Internal error: synchronous external abort: 96000010 [#1] PREEMPT SMP > > ... > > > > > > In this case I'm using a simple device tree similar to apq8016-sbc, > > but it also happens using something as simple as msm8916-mtp.dts > > on this particular device. > > (Attached: dmesg log with msm8916-mtp.dts and arm64 defconfig) > > > > I can avoid the crash and boot without any further problems by disabling > > every coresight device defined in msm8916.dtsi, e.g.: > > > > tpiu@820000 { status = "disabled"; }; > > ... > > > > > I don't have any use for coresight at the moment, > > but it seems somewhat odd to put this in the device specific dts. > > > > Any idea what could be causing this crash? > > This is mostly due to the missing power domain support. The CoreSight > components are usually in a debug power domain. So unless that is turned on, > (either by specifying proper power domain ids for power management protocol > supported by the firmware OR via other hacks - e.g, connecting a DS-5 to > keep the debug power domain turned on , this works on Juno -). Interesting, thanks a lot! In this case I'm wondering how it works on the Dragonboard 410c. Does it enable these power domains in the firmware? (Assuming it boots without this error...) If coresight is not working properly on all/most msm8916 devices, shouldn't coresight be disabled by default in msm8916.dtsi? At least until those power domains can be set up by the kernel. If this is a device-specific issue, what would be an acceptable solution for mainline? Can I turn on these power domains from the kernel? Or is it fine to disable coresight for this device with the snippet above? I'm not actually trying to use coresight, I just want the device to boot :) And since I am considering submitting my device tree for inclusion in mainline, I want to ask in advance how I should tackle this problem. Thanks! Stephan _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel