Received: by 2002:a05:6a10:2785:0:0:0:0 with SMTP id ia5csp195795pxb; Thu, 14 Jan 2021 03:38:45 -0800 (PST) X-Google-Smtp-Source: ABdhPJxAysRsKlAypaaRXVLSAzb/M84EwaXuoW14ULLV2RygqLy40t9CeKMex5T3KOvCtmdAwZ1K X-Received: by 2002:a05:6402:22ea:: with SMTP id dn10mr5288659edb.67.1610624325379; Thu, 14 Jan 2021 03:38:45 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1610624325; cv=none; d=google.com; s=arc-20160816; b=IIs4JbWLGqhjYSSBpik/lf6sxXX4r2tWpadKqxhwnXdHUe7iBSbaYRW+pxSs4AOdT7 D3AU6IG1QwyMpcHqsJtmCp5YbaLLTbwfpc5t0ydww0vWqef1MwKQXONFYiRfZOtj3CQn bJhGNuUdEupkfx57biCmppe/r+rL7dlGSKxovdtLuVCG+tVhlz3fxT6KYb+pRzLX8wT9 FwwbC+O4bTDT45ngPKWzqAb7w8368cp7maoY/iVtH7WhNNdbCyPnzxHXzyTJLI8Ze7Lt tYmg1htfido9Njs3W2AbMzqNf6wU/hUZEy8m/1ogbou49kW/vChZ0L22uoRfjUyzalRs qtIg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:dkim-signature:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject; bh=+9rocMNGS2IbcQd0Pjmdcp5Lyh6Q40HsTyIJIyT/ung=; b=pY/NLpLCAHFh7/t34JgnvrjmOoM9Cd8qLGR1qnJP7W3W2ASq7Dxz8WykhckfF/U60U iRyrvJGGATiBZEII2DEZmPg634KJGUP+ZnHZmkQ2jrKDQk7VqkAcu8GzSHEW+L3h098U NHMxFWmlwYoGmyf/srJgZewgez6eio0fwzDJlf2rkarGvL1c+ipdlXhDo0XPS55lYzIs Vhx5+/kEkVucRNX+Oi4FGdyQMmszhsytWpnsgWTQRAE16dxwDGkls8A0zlyonBJV89L4 cnaCU3Noe2whT45oJRP7SS9yNwb5JDyxM6XW7FdXnC2ElBdE1JMdEGhU1KXPJXyObcFT RpeQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@nvidia.com header.s=n1 header.b=VqU6jCvw; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=nvidia.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id k23si2468074ejk.337.2021.01.14.03.38.20; Thu, 14 Jan 2021 03:38:45 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@nvidia.com header.s=n1 header.b=VqU6jCvw; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=nvidia.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727652AbhANLfn (ORCPT + 99 others); Thu, 14 Jan 2021 06:35:43 -0500 Received: from hqnvemgate26.nvidia.com ([216.228.121.65]:18548 "EHLO hqnvemgate26.nvidia.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726427AbhANLfm (ORCPT ); Thu, 14 Jan 2021 06:35:42 -0500 Received: from hqmail.nvidia.com (Not Verified[216.228.121.13]) by hqnvemgate26.nvidia.com (using TLS: TLSv1.2, AES256-SHA) id ; Thu, 14 Jan 2021 03:35:02 -0800 Received: from [10.26.73.78] (172.20.145.6) by HQMAIL107.nvidia.com (172.20.187.13) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Thu, 14 Jan 2021 11:34:56 +0000 Subject: Re: [PATCH v1 0/5] Enable fw_devlink=on by default To: Saravana Kannan CC: Marc Zyngier , Greg Kroah-Hartman , "Rafael J. Wysocki" , Android Kernel Team , LKML , Jisheng Zhang , Kevin Hilman , John Stultz , Nicolas Saenz Julienne , linux-tegra References: <20201218031703.3053753-1-saravanak@google.com>

From: Jon Hunter Message-ID: <17703ac8-2238-0b64-3c98-ddadc7ae8a36@nvidia.com> Date: Thu, 14 Jan 2021 11:34:53 +0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset="utf-8" Content-Language: en-US Content-Transfer-Encoding: 7bit X-Originating-IP: [172.20.145.6] X-ClientProxiedBy: HQMAIL107.nvidia.com (172.20.187.13) To HQMAIL107.nvidia.com (172.20.187.13) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nvidia.com; s=n1; t=1610624102; bh=+9rocMNGS2IbcQd0Pjmdcp5Lyh6Q40HsTyIJIyT/ung=; h=Subject:To:CC:References:From:Message-ID:Date:User-Agent: MIME-Version:In-Reply-To:Content-Type:Content-Language: Content-Transfer-Encoding:X-Originating-IP:X-ClientProxiedBy; b=VqU6jCvwZSflxUQmUwklTL8K3RVd/N8CLw1I+sil+4CW8uQW8+HnYMZEFkn6zIY00 ntD/OFnB8K7z3UKaDO5VP/oTHUWG5+KcyHWMlTaJuViP/lv4GrP0+sWBWo5IIce2bF NtXbirmXOinZWj0dpsLmLlNQRoShoT0N2CYm9NROjcfCYZyHmFcvfr4rqxJHh5NTMH 6aRB8oyEI5DPAHHpSIu9TC4GedOpkAkNW/btZINTE1zmxik1snw9tLJDwyIzZlRCHX KRZ1yPUQpDvTQ6vuHOXBrZZTe3ngAJDbb1N666dxW8VIy/kEbXUp+M8AjHaHvrheVj +bx+agCnQpPOQ== Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 13/01/2021 21:29, Saravana Kannan wrote: ... >> I am seeing the same problem on Tegra30 Cardhu A04 where several regulators >> are continuously deferred and prevents the board from booting ... >> >> [ 2.518334] platform panel: probe deferral - supplier regulator@11 not ready >> >> [ 2.525503] platform regulator@1: probe deferral - supplier 4-002d not ready >> >> [ 2.533141] platform regulator@3: probe deferral - supplier regulator@101 not ready >> >> [ 2.540856] platform regulator@5: probe deferral - supplier regulator@101 not ready >> >> [ 2.548589] platform regulator@6: probe deferral - supplier regulator@101 not ready >> >> [ 2.556316] platform regulator@7: probe deferral - supplier regulator@101 not ready >> >> [ 2.564041] platform regulator@8: probe deferral - supplier regulator@101 not ready >> >> [ 2.571743] platform regulator@9: probe deferral - supplier regulator@101 not ready >> >> [ 2.579463] platform regulator@10: probe deferral - supplier regulator@101 not ready >> >> [ 2.587273] platform regulator@11: probe deferral - supplier regulator@101 not ready >> >> [ 2.595088] platform regulator@12: probe deferral - supplier regulator@104 not ready >> >> [ 2.603837] platform regulator@102: probe deferral - supplier regulator@104 not ready >> >> [ 2.611726] platform regulator@103: probe deferral - supplier regulator@104 not ready >> >> [ 2.620137] platform 3000.pcie: probe deferral - supplier regulator@5 not ready > > Looks like this is not the whole log? Do you see any "wait for > supplier" logs? That's what all these boot issues should boil down to. > And as usual, pointer to DT for this board please. Ah yes I see ... platform regulator@1: probe deferral - wait for supplier tps65911@2d Yes the device-tree for this board can be found here [0]. Looks like there is a circular dependency between the vddctrl_reg and vddcore_reg. This is part of coupled regulators which have a two-way linkage [1]. So this change appears to conflict with this. Jon [0] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/arch/arm/boot/dts/tegra30-cardhu-a04.dts [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/devicetree/bindings/regulator/regulator.yaml#n129 -- nvpublic