Received: by 2002:ac0:98c7:0:0:0:0:0 with SMTP id g7-v6csp294335imd; Fri, 26 Oct 2018 08:38:34 -0700 (PDT) X-Google-Smtp-Source: AJdET5dvlUpNEIiVMDpNfLDc1bxyhb4bkFMiOZhjG7JeVgZaE/045Mvody9+wXUveYdHmHOFYqTp X-Received: by 2002:a17:902:9b89:: with SMTP id y9-v6mr3939001plp.239.1540568314813; Fri, 26 Oct 2018 08:38:34 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1540568314; cv=none; d=google.com; s=arc-20160816; b=KhB4XlBooH/i8iNHgBlBE10nqwR/hziH/48pEdqaMXC82l4VgfrFNiQPHBKk7tOnnv I0zrHh/YmAGrLqYqkoPOnm/0t2ZrSQkWaeVwVG6DSPZcjv5iXevm3C15OxI88b9/rWJM +6rA1N40LukoUIWA5vGmUF4yQXLZH/HFOd4S/SLSeWNDNdTgi3dJCbRdB+nx/0hCH6i/ UGOcbWN5xJeqDFuHuRxrfQ90xhnJAavNTDpSvhpLlk5/DQeVvHtJEAOHP6t8w3aOOnuZ WSFCh5TUC84Mfml6KRwMddX7V9OBL3gBl1W4Zm/HDrVIHL/3Qz6nFkERmIDF9Qk2kSIt JbmQ== 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:mime-version :references:in-reply-to:date:cc:to:from:subject:message-id; bh=t2lzG6tJLazUT3wuEs1dNLMcj6LYPufxJufXKiBoLow=; b=NbLkFKhjyWY3FEo8uqv75YRS0H6OJymBJJg0QwYIKj3Fq0Xj+yHdZSWGdTKHQOUK3L DMwVMKv1LztASuCSzeTV0+QdCyE5gi9QxH1ig2QVB2ULwg7IFGjXyma/jCYHuddJwdWl PnP1Ncsb96MlpEyUb/wt8bPba6QUYoTLSRyCaiTNgXK08xgiyVuht76ins4D7WiNfiYg t6slVOeRki65zeWDOoVzw+s5RFj2XfYTo/WKBIZ/M4NpTDoz4vAIquVNEJe1Ffsb0ZLA FdQPcPUV/M9qmgwvSxxrWAS4Iwlb0HL0HR+a+xkA+R2eOZdhrRprFCzpmOcosB7WaeAx 828g== 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 34-v6si11262021pgy.249.2018.10.26.08.38.17; Fri, 26 Oct 2018 08:38:34 -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 S1727636AbeJ0APX (ORCPT + 99 others); Fri, 26 Oct 2018 20:15:23 -0400 Received: from metis.ext.pengutronix.de ([85.220.165.71]:45815 "EHLO metis.ext.pengutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726159AbeJ0APX (ORCPT ); Fri, 26 Oct 2018 20:15:23 -0400 Received: from kresse.hi.pengutronix.de ([2001:67c:670:100:1d::2a]) by metis.ext.pengutronix.de with esmtp (Exim 4.89) (envelope-from ) id 1gG4B8-0006VN-8S; Fri, 26 Oct 2018 17:37:38 +0200 Message-ID: <1540568255.2245.11.camel@pengutronix.de> Subject: Re: [RFC PATCH v2 01/17] OPP: Allow to request stub voltage regulators From: Lucas Stach To: Dmitry Osipenko , Viresh Kumar Cc: "Rafael J. Wysocki" , 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 Date: Fri, 26 Oct 2018 17:37:35 +0200 In-Reply-To: References: <20181021205501.23943-1-digetx@gmail.com> <20181021205501.23943-2-digetx@gmail.com> <20181022053636.ag62j3rj3vovbz53@vireshk-i7> <20181022113224.b5fiebgy2aap66nd@vireshk-i7> <29f893be-feed-c4c5-8468-51f7228dd468@gmail.com> <20181024064123.lbpbeervghp35fe7@vireshk-i7> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.22.6-1+deb9u1 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-SA-Exim-Connect-IP: 2001:67c:670:100:1d::2a X-SA-Exim-Mail-From: l.stach@pengutronix.de X-SA-Exim-Scanned: No (on metis.ext.pengutronix.de); SAEximRunCond expanded to false X-PTX-Original-Recipient: linux-kernel@vger.kernel.org Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Am Freitag, den 26.10.2018, 15:03 +0300 schrieb Dmitry Osipenko: [...] > > On the other hand, the tegra20 cpufreq driver is common across a lot of boards. > > What will happen if the DT for some of the boards isn't correct and missed the > > necessary regulator node ? > > AFAIK, there is assumption that bootloader should setup regulators in > a way that kernel could work properly at max clock rates. Otherwise > things won't work. This isn't true. The assumption is that the bootloader sets up the regulators such that stable operation at the CPU speed used by the bootloader is guaranteed. Often the bootloader doesn't know about specific SKUs, so drives things at a rate/voltage that is safe across all SKUs [1], in which case the bootloader is totally unaware of the voltage needed to run the CPU at highest possible clock frequency. Regards, Lucas [1] http://git.denx.de/?p=u-boot.git;a=commit;h=2364e151e432b4ccf32dc9e6147121253d4ff86d