Received: by 2002:a05:6359:c8b:b0:c7:702f:21d4 with SMTP id go11csp463969rwb; Tue, 4 Oct 2022 06:31:53 -0700 (PDT) X-Google-Smtp-Source: AMsMyM6bZOGpFYC8YcOk5OB3qF8y5k7REh4i9jCgn7YfGZustEql2Zxm5UqDUr8JGfQLa22s+htg X-Received: by 2002:a17:902:d506:b0:178:3599:5e12 with SMTP id b6-20020a170902d50600b0017835995e12mr26871286plg.70.1664890313180; Tue, 04 Oct 2022 06:31:53 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1664890313; cv=none; d=google.com; s=arc-20160816; b=P6JWgLGWKuAkpjHAuosYGomEzjdThlwAV20LaUOR5lX3U0K+2WHOLk06fNJtF48x2H 62CqbZIy88WwlGd6bDNELeAsmNvg7r10NyPaZzYIT6rCHctalpW+PC5kmvyoQ1NZCQbE AHk8HpjBf96+ardzXC3d9Pl+LL7igKQNgEWnyoRpTY+lzuR3PaJZQ7DIZ5flAT1iRgmt 749ICwBn9L5Mon+TItBeG6SX+ADXr602rVmARUBUqu129NMjL8g7cOrwjtjCA5CJE+cL qi5cnln6x5UII6ThYQZFE2x3ECWG6cPv5NG5u4Ipjomaf72cOoQVyGal8wTk2SqnBK7c DjtQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=x7R0QoQX8EkKl/iwy07i+r2u0YMp5259F60knxVAX1I=; b=KsXh1tGFufT6HFDBSbpPlNwQPNY7M1kIoPIMQTGWg3F3L2nEXCylSVBIreU7I9hHvE FzNFlwc0LqghJ6sGc/FR/tMbwHSyTg31UnF44FM+6blTYmyBci3OySvH+p4mkOP5IaE0 jfTVItsENTQIK6YBneERH3ic29RcJsJk6c3d+GOmtmsIiwiM/0xzLhp1TsM1c+XUX18/ jXL/ewwoyfYwhqQarq6wUug/EwjM8AxPyNvIU7r2bkIOoPBk1jdpnif+oYNtx0QosolM hLS52/9y+XzaLro+V6tKqvgB8fhxioy9P8CcRZW8ffT9jeIjO2gSnoJRjmoOyNcTq85t C+uQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=JBdf8ZXl; 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=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id i1-20020a17090a058100b0020329ca07cbsi2753241pji.119.2022.10.04.06.31.34; Tue, 04 Oct 2022 06:31:53 -0700 (PDT) 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; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=JBdf8ZXl; 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=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230318AbiJDN2c (ORCPT + 99 others); Tue, 4 Oct 2022 09:28:32 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:37070 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230297AbiJDN2U (ORCPT ); Tue, 4 Oct 2022 09:28:20 -0400 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id E636C25C2 for ; Tue, 4 Oct 2022 06:28:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1664890099; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=x7R0QoQX8EkKl/iwy07i+r2u0YMp5259F60knxVAX1I=; b=JBdf8ZXloceptuCYpfFi2DsQKaFWQfkJHiBWUXaWjqFmZcuKw95xnAhfoNHwtxGeLROF65 YGFdKJ5RLoju46LYKqA64a2Ekcy0motiQtp4OgVujZwR2raWqjB5/Oe5uWNctkTM8TEVpH vteGOxvDTOEtrFCDWjnRcpmyceqh6rc= Received: from mail-qk1-f198.google.com (mail-qk1-f198.google.com [209.85.222.198]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_128_GCM_SHA256) id us-mta-269-jFksv2BzOw-zAO5lOJ8-hg-1; Tue, 04 Oct 2022 09:28:17 -0400 X-MC-Unique: jFksv2BzOw-zAO5lOJ8-hg-1 Received: by mail-qk1-f198.google.com with SMTP id bi3-20020a05620a318300b006cf2d389cdaso11519584qkb.8 for ; Tue, 04 Oct 2022 06:28:17 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date; bh=x7R0QoQX8EkKl/iwy07i+r2u0YMp5259F60knxVAX1I=; b=jw6DL56k74opgtHGb4gjFyFuQgCPBW2Y/yhmFWXrrUQWjFSm+L4vEXnlzjQweQsfvh U0n+kvIFrHajQQ1fiwO9CkN2SWZKkboqiSnIDU1TUWnd2Dg5zOxpjf7Ebwk2J4HvifHQ +xJGCkZIpH96u/wxMBxnaA8XPHOJTM1q5NLDhWLOqj9mO9a3kDAU7r/9/iK5cvwZmpzF W3fw5M/ZbmGFxme9bWaM/1HziYtjRSHaCo1vjUuGK2h2GcowtHnyY6CX+e2WAKwla6HS nnCrdmXnA9dT9a/cECNWmO8HMNQ/fFXd/3QEo5iv4Ng4VJL6T2uAh/OjCnGO4aFDXWPf hGiA== X-Gm-Message-State: ACrzQf3ftDoQwnyaCBDou8aTw/vNsW86h7Xuye8qi2Q1SZ3lfZf1OWBf lwG5C0vbuf8UVKStQbMU4G37C9WS1AtUzFkeHsKak33qoQqP470Byw3CkknUEswm9TP5JTUnLcw iG2jRm4j5gkgZvUj+1zdLNNLE X-Received: by 2002:a37:9745:0:b0:6cf:9ca3:b43d with SMTP id z66-20020a379745000000b006cf9ca3b43dmr16797896qkd.693.1664890097506; Tue, 04 Oct 2022 06:28:17 -0700 (PDT) X-Received: by 2002:a37:9745:0:b0:6cf:9ca3:b43d with SMTP id z66-20020a379745000000b006cf9ca3b43dmr16797878qkd.693.1664890097283; Tue, 04 Oct 2022 06:28:17 -0700 (PDT) Received: from localhost (pool-100-0-210-47.bstnma.fios.verizon.net. [100.0.210.47]) by smtp.gmail.com with ESMTPSA id q6-20020a05622a030600b0035badb499c7sm12347890qtw.21.2022.10.04.06.28.16 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 04 Oct 2022 06:28:16 -0700 (PDT) Date: Tue, 4 Oct 2022 09:28:16 -0400 From: Eric Chanudet To: Brian Masney Cc: Parikshit Pareek , Andy Gross , Bjorn Andersson , Konrad Dybcio , Rob Herring , Krzysztof Kozlowski , linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, Andrew Halaney , Shazad Hussain , Johan Hovold Subject: Re: [PATCH v5 0/3] arm64: dts: qcom: add dts for sa8540p-ride board Message-ID: <20221004132816.ryhyo5ihwruxspl6@echanude> References: <20221003125444.12975-1-quic_ppareek@quicinc.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Spam-Status: No, score=-2.8 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_LOW, SPF_HELO_NONE,SPF_NONE autolearn=unavailable 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 Mon, Oct 03, 2022 at 01:31:52PM -0400, Brian Masney wrote: > Just for documentation purposes, to get linux-next-20220930 booting on > the QDrive3 with the upstream arm64 defconfig I had to apply the > following patches: > > - arm64: dts: qcom: sc8280xp: fix UFS PHY serdes size > https://lore.kernel.org/linux-arm-msm/20220915141601.18435-1-johan+linaro@kernel.org/ > > Without this, the phy fails to probe due to the following error: > > qcom-qmp-ufs-phy 1d87000.phy: can't request region for resource [mem 0x01d87400-0x01d87507] > qcom-qmp-ufs-phy 1d87000.phy: failed to create lane0 phy, -16 > qcom-qmp-ufs-phy: probe of 1d87000.phy failed with error -16 > > - This hack patch is still needed: > disable has_address_auth_metacap and has_generic_auth > https://github.com/andersson/kernel/commit/d46a4d05d5a17ff4447af08471edd78e194d48e5 > > Without this, the boot hangs at: > > rcu: srcu_init: Setting srcu_struct sizes based on contention. > arch_timer: cp15 and mmio timer(s) running at 19.20MHz (virt/virt). > clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x46d987e47, max_idle_ns: 440795202767 ns > sched_clock: 56 bits at 19MHz, resolution 52ns, wraps every 4398046511078ns > > - My UFS clock patch is still needed: > arm64: dts: qcom: sc8280xp: correct ref_aux clock for ufs_mem_phy > https://lore.kernel.org/lkml/20220830180120.2082734-1-bmasney@redhat.com/T/#u > > - I didn't use an initrd for testing so I had to change the options > CONFIG_SCSI_UFS_QCOM and CONFIG_PHY_QCOM_QMP from =m to =y. I followed the instructions above and linux-next-20220930 booted on the QDrive3 to a prompt. It then hanged after a couple minutes and rebooted in Sahara mode: B - 1662280 - Sahara Init B - 1665422 - Sahara Open There seems to be no trace from the kernel, this happened consistently over 3 boots. I asked Brian, he mentioned he only booted to prompt so that may have happened unbeknownst to him as well. -- Eric Chanudet