Received: by 2002:ac0:aa62:0:0:0:0:0 with SMTP id w31-v6csp2373994ima; Mon, 22 Oct 2018 08:44:19 -0700 (PDT) X-Google-Smtp-Source: ACcGV63MIbqSZqnZWC3dgHOQQtzyXAaM+Sq6dfLTvIbniICds9VDN5cQOGYzKtyiYbw6YMInDWdD X-Received: by 2002:a63:e07:: with SMTP id d7-v6mr18394611pgl.272.1540223059648; Mon, 22 Oct 2018 08:44:19 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1540223059; cv=none; d=google.com; s=arc-20160816; b=XGVRZoZK8g08ULEdxQnwxe1fb3YjHUdwURHN1KZQcBHFDnbGeRiCUYXmrMYo+pQcpV FWYSRyjGgICRib0jYAwl6rJuDwpsn7YQ3tnGANGZfzDPqLpkip29kR+2Fm2AX8waCoUu D3XH56j9LbvwX5mlSWwPWW9puDNZzz2PkHgksu29bwybVuYDSIrLFKMJbNROxXUogdyf cktYXt094AbJfcOqagja27SSSEiEv+tu+9XC4KaMzvBUlyojcZraPgtOmfA0bqqKTW81 pDKhZVJp2N4X3Zd7n0a86T9R5JhpOrTs3JzuVan/4/QxvoocMYK8BXXcsvaleNQ053xx 6yIg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject; bh=u88TSu4xJ/tUft5cKCgnTD0+EiZ+KsNnatM0wEOg1yw=; b=ysq60wQMWfTJ2vI79m8V+swWKsXFWr0Zp73ayuYI4oyS2buY6NoHndAI6cn5PAfmNv W47mSe4yWGVdNFp9BE1zmcqA2xml+isNJ26J+y+eC2pDtVfYkn4q9ggxuGuJcY9FuvnG 9WYiUcA5hn3MCl7VM35wUHy1sgEjs7OaXOFQcRyuexxa1pZR36EICpyrLRaqfEvliAGg 0qGeznYbOQV8Rc8OLjvnQsZxNUFJxkkknMJxKFdl4iY0d6E2Nmlyq6lc/eT7vOJeVd+0 LtwDQTOiSsBAPtWGB9ev99yUG6Jqy8j0t+P56u8cYTaKhKpe2sfINdJGuy7O6NmIzyCg g0pQ== ARC-Authentication-Results: i=1; mx.google.com; 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 e9-v6si38347549pln.265.2018.10.22.08.44.05; Mon, 22 Oct 2018 08:44:19 -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; 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 S1728573AbeJWACS (ORCPT + 99 others); Mon, 22 Oct 2018 20:02:18 -0400 Received: from avon.wwwdotorg.org ([104.237.132.123]:50602 "EHLO avon.wwwdotorg.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727590AbeJWACS (ORCPT ); Mon, 22 Oct 2018 20:02:18 -0400 X-Greylist: delayed 591 seconds by postgrey-1.27 at vger.kernel.org; Mon, 22 Oct 2018 20:02:18 EDT Received: from [10.20.204.51] (unknown [216.228.112.24]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by avon.wwwdotorg.org (Postfix) with ESMTPSA id 989871C01F5; Mon, 22 Oct 2018 09:33:25 -0600 (MDT) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.100.1 at avon.wwwdotorg.org Subject: Re: [RFC PATCH v2 09/17] ARM: dts: tegra20: harmony: Setup voltage regulators for DVFS To: Dmitry Osipenko Cc: "Rafael J. Wysocki" , Viresh Kumar , Rob Herring , Thierry Reding , Jonathan Hunter , Nishanth Menon , Stephen Boyd , Marcel Ziswiler , linux-tegra@vger.kernel.org, linux-pm@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org References: <20181021205501.23943-1-digetx@gmail.com> <20181021205501.23943-10-digetx@gmail.com> From: Stephen Warren Message-ID: Date: Mon, 22 Oct 2018 09:33:23 -0600 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.2.1 MIME-Version: 1.0 In-Reply-To: <20181021205501.23943-10-digetx@gmail.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 10/21/18 2:54 PM, Dmitry Osipenko wrote: > Set min/max regulators voltage and add CPU node that hooks up CPU with > voltage regulators. > diff --git a/arch/arm/boot/dts/tegra20-harmony.dts b/arch/arm/boot/dts/tegra20-harmony.dts > - sm0 { > + core_vdd_reg: sm0 { > regulator-name = "vdd_sm0,vdd_core"; > - regulator-min-microvolt = <1200000>; > - regulator-max-microvolt = <1200000>; > + regulator-min-microvolt = <1000000>; > + regulator-max-microvolt = <1300000>; > + regulator-coupled-with = <&rtc_vdd_reg>; > + regulator-coupled-max-spread = <150000>; > regulator-always-on; > }; How do you know for sure that these increased ranges are safe (high end) and stable (low end) for this particular board? IIRC the safe/legal range depends on the chip SKU, and to be honest I have no idea which SKU is present on Harmony... For public boards like Colibri I imagine there's enough information out there to tell what will work, but maybe not our internal boards like Harmony, unless you checked our ancient downstream kernels?