Received: by 10.223.176.5 with SMTP id f5csp723798wra;
        Wed, 7 Feb 2018 06:33:18 -0800 (PST)
X-Google-Smtp-Source: AH8x225V9ZihHLoZPoyHsc1Hz2yvRMlP308xxXrP1OD+LTCma0wh7EFtUYWhcmIZKMX1gavMdyqd
X-Received: by 2002:a17:902:bc85:: with SMTP id bb5-v6mr6321928plb.425.1518013998215;
        Wed, 07 Feb 2018 06:33:18 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; t=1518013998; cv=none;
        d=google.com; s=arc-20160816;
        b=YF2qWZ7bvADiB42JIuwmufd+9D+4fwVFvHxG6aI1hFmJP36e6gHAxoSmmbfSLIlABO
         /nNCGNNkizBJccWD01TF2RJf8d2SYkkrGj1hMUoMwF/Tvg0cazUNS1FK+vxad+1pr+no
         QxJDdJ1ytI5tUN7wr0pHLtpvtBNHkkxUxvk6txi957dFwn5YVMn8yY55CUZtugni5K4X
         3VAZBBBilYhh5ZT17mXNo3rxkLnvf98Bf+RrUVuPvTGlgEGE1Q7z6st5OQ3xmuv8//os
         BGTONWOAZpmNS8J93M2s2tCf8pdkPEy7ggYfaWsgJqOgxVXYQq2hS+VfTh9XTFJTFSE2
         7q4Q==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816;
        h=list-id:precedence:sender:user-agent:in-reply-to
         :content-disposition:mime-version:references:message-id:subject:cc
         :to:from:date:arc-authentication-results;
        bh=MyMZ438GMIbdjYWX9Mky4bsi9KeDXzunWlYHC7uI06o=;
        b=mxJpHWAyisLJPdwE/2Y3YGqp3mrW2sLUQ2zVnlfbswKoGfYC5hjKWSz6nAxYhfpMk2
         Z1Kg5mEG27fjbsvdJK5pQ1QPAy/rw03X7t4yjAO5WjgyKI0pDfN8xrlL1EOKLaMqdz3b
         UA4jONMkskqJ1n+bkMCYhq31IvaHiXsTrQXxaCz6rp0fzgnczH/bwI8wEurhtmnKeFFj
         LYabhSPhIil67Q+0wesD/UXjCZfTbzJ0EXQ3TLh5Tuvj/0dJdVSaSYFHT7gxT+IzvRfr
         CmKtXIogiYewQ+GxkyQOm4I6W67Mlto4qQUQQ7/aKjhhydpok9PVaHvSjnxGNk4K9tZ8
         HMBg==
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;
       dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=nvidia.com
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67])
        by mx.google.com with ESMTP id m6si1195417pff.273.2018.02.07.06.33.03;
        Wed, 07 Feb 2018 06:33:18 -0800 (PST)
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;
       dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=nvidia.com
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1754206AbeBGOcV (ORCPT <rfc822;shmalave.kernel@gmail.com>
        + 99 others); Wed, 7 Feb 2018 09:32:21 -0500
Received: from hqemgate16.nvidia.com ([216.228.121.65]:16191 "EHLO
        hqemgate16.nvidia.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1753923AbeBGOcT (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Wed, 7 Feb 2018 09:32:19 -0500
Received: from hqpgpgate102.nvidia.com (Not Verified[216.228.121.13]) by hqemgate16.nvidia.com
        id <B5a7b0dfd0000>; Wed, 07 Feb 2018 06:32:30 -0800
Received: from HQMAIL105.nvidia.com ([172.20.161.6])
  by hqpgpgate102.nvidia.com (PGP Universal service);
  Wed, 07 Feb 2018 06:33:01 -0800
X-PGP-Universal: processed;
        by hqpgpgate102.nvidia.com on Wed, 07 Feb 2018 06:33:01 -0800
Received: from UKMAIL101.nvidia.com (10.26.138.13) by HQMAIL105.nvidia.com
 (172.20.187.12) with Microsoft SMTP Server (TLS) id 15.0.1347.2; Wed, 7 Feb
 2018 14:32:17 +0000
Received: from tbergstrom-lnx.Nvidia.com (10.21.24.170) by
 UKMAIL101.nvidia.com (10.26.138.13) with Microsoft SMTP Server (TLS) id
 15.0.1347.2; Wed, 7 Feb 2018 14:32:14 +0000
Received: by tbergstrom-lnx.Nvidia.com (Postfix, from userid 1002)
        id 9B240F8037C; Wed,  7 Feb 2018 16:32:13 +0200 (EET)
Date:   Wed, 7 Feb 2018 16:32:13 +0200
From:   Peter De Schrijver <pdeschrijver@nvidia.com>
To:     Mark Brown <broonie@kernel.org>
CC:     <linux-tegra@vger.kernel.org>, <linux-clk@vger.kernel.org>,
        <mturquette@baylibre.com>, <sboyd@codeaurora.org>,
        <robh+dt@kernel.org>, <mark.rutland@arm.com>,
        <devicetree@vger.kernel.org>, <lgirdwood@gmail.com>,
        <linux-kernel@vger.kernel.org>,
        Laxman Dewangan <ldewangan@nvidia.com>
Subject: Re: [PATCH v3 01/11] regulator: core: add API to get voltage
 constraints
Message-ID: <20180207143213.GB5850@tbergstrom-lnx.Nvidia.com>
References: <1517934852-23255-1-git-send-email-pdeschrijver@nvidia.com>
 <1517934852-23255-2-git-send-email-pdeschrijver@nvidia.com>
 <20180206163544.GI5681@sirena.org.uk>
 <20180207084744.GG7031@tbergstrom-lnx.Nvidia.com>
 <20180207104351.GA6003@sirena.org.uk>
 <20180207123750.GA5850@tbergstrom-lnx.Nvidia.com>
 <20180207141846.GC6003@sirena.org.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <20180207141846.GC6003@sirena.org.uk>
X-NVConfidentiality: public
User-Agent: Mutt/1.5.21 (2010-09-15)
X-Originating-IP: [10.21.24.170]
X-ClientProxiedBy: UKMAIL101.nvidia.com (10.26.138.13) To UKMAIL101.nvidia.com
 (10.26.138.13)
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On Wed, Feb 07, 2018 at 02:18:46PM +0000, Mark Brown wrote:
> On Wed, Feb 07, 2018 at 02:37:51PM +0200, Peter De Schrijver wrote:
> > On Wed, Feb 07, 2018 at 10:43:51AM +0000, Mark Brown wrote:
> > > On Wed, Feb 07, 2018 at 10:47:44AM +0200, Peter De Schrijver wrote:
> > > > On Tue, Feb 06, 2018 at 04:35:44PM +0000, Mark Brown wrote:
> > > > > On Tue, Feb 06, 2018 at 06:34:02PM +0200, Peter De Schrijver wrote:
> 
> > > > > > Add API to get min/max rail voltage configured from platform for
> > > > > > given rails.
> 
> > > > > because...
> 
> > > > of the next patch where this is used to retrieve the minimum rail voltage.
> 
> > > And that in turn is needed for...?
> 
> > To calculate the required voltage for each frequency.
> 
> You're going to have to provide a much better explanation of what this
> is doing - right now it seems like an abuse of constraints.  Client
> drivers can already determine if a particular voltage they want to set
> is available via regulator_list_voltage() and so on, that's what
> constraints are there to set.  It sounds like you're trying to use them
> for something else but you're really not explaining your use case
> clearly.

There is no way to query what voltage I will actually get for a given input
voltage. If you read drivers/clk/tegra/cvb. (you did do that right?), you
will see that there is a minimum and maximum voltage defined by
charaterization which needs to be capped to the regulator generated voltages
for those points.

Peter.