Received: by 2002:a05:6a10:22f:0:0:0:0 with SMTP id 15csp2764313pxk; Tue, 15 Sep 2020 01:28:39 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwKj9UQkG9RDMxbJUJoBdwRnRDaBKMToi56bZ9CaRcDgAz27hiTldzp0G6CtEmUpWhS0qXa X-Received: by 2002:aa7:d750:: with SMTP id a16mr21800966eds.362.1600158519244; Tue, 15 Sep 2020 01:28:39 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1600158519; cv=none; d=google.com; s=arc-20160816; b=n8P+tqxqtP0u0hOv5UhHjuWPrwPUWu+1vcoZbYhq1l+iAi55QBQJoJsiirOxt3Isg7 RHHCemh1uYE0858AYiTGdwDuHrWfn9ZCzcwzN8ONAwQWcrhwJDoLBzGQigQlmKzTXaJh XjQV8qJH1ZhY1Mgnra6NNhqY6CT0f5LY2GQm2HRKI/6BoXUPfmEhvFV+HxuT24wlkPF+ PVfV3dAtJ7pxMlFWKNEAbEflhDr7uxnvGyk9DjOU5O2GjaeFfBL3PeSo2EhiMUxoOc1y C0FLA+QCEQyi5ZcRUEblTlfA2Jl6ZHIWX0sR1ND4KAd2RBtk2+3s4OWuUNgmTn1o/8hT rEwA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:message-id:references :in-reply-to:subject:cc:to:from:date:content-transfer-encoding :mime-version:dkim-signature; bh=pSgbry1PAaBdRWEhUEVxrVeaHzZFoZPrjHZu+EwHtIw=; b=Ycsn+8H+dLmnYiIDV+/AaNWEOwyBBTdKd+Iix28H47T8tSV2Q7EFfks49q8AawTHYs SHxXeE2AAMExNOJQxgPAmDj3kDxh6jrvwESo9Ls86CTrKwH0bwLrIAYmlS6v5d2NRM6m 0xyWyk5FmlD5nwY1kBe0NF7n1ZrRGVqUzB+j3Vb5No18pndmGgFIPXt728ajkip14HaW mkbjKjp37YAYXI1pLL5ZdfS6hdN3XhKDkIg+6sOe9uc9PaAXmlNoVRe0hOY9qh/4vs5V AmwqHw2ur2yYtb4dMGHMWZfMk1gGRMculGziC3Oesz7gFIT9BnfYP2tuuFGU60yVdPe+ We9A== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@mg.codeaurora.org header.s=smtp header.b=szVodTbr; 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id bu18si8794700ejb.324.2020.09.15.01.28.16; Tue, 15 Sep 2020 01:28:39 -0700 (PDT) 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=fail header.i=@mg.codeaurora.org header.s=smtp header.b=szVodTbr; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726414AbgIOIZC (ORCPT + 99 others); Tue, 15 Sep 2020 04:25:02 -0400 Received: from mail29.static.mailgun.info ([104.130.122.29]:18448 "EHLO mail29.static.mailgun.info" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726318AbgIOIP5 (ORCPT ); Tue, 15 Sep 2020 04:15:57 -0400 DKIM-Signature: a=rsa-sha256; v=1; c=relaxed/relaxed; d=mg.codeaurora.org; q=dns/txt; s=smtp; t=1600157723; h=Message-ID: References: In-Reply-To: Subject: Cc: To: From: Date: Content-Transfer-Encoding: Content-Type: MIME-Version: Sender; bh=pSgbry1PAaBdRWEhUEVxrVeaHzZFoZPrjHZu+EwHtIw=; b=szVodTbrLlD2rnYl2lSuQVub3MhHBdWC0/E3ZDDRsFMqbruq2uyU1QXGnOUESKYzKLzJBGeV HwlWH/UdCXO6pO5IKuAxhfrdrdsixbuiLlDxz2ncUaYysL33aF0w96ibnZvivzqN7qsR1gPo OrnK8Wo1EeDaRrXaKHcb5h4TZdM= X-Mailgun-Sending-Ip: 104.130.122.29 X-Mailgun-Sid: WyI0MWYwYSIsICJsaW51eC1rZXJuZWxAdmdlci5rZXJuZWwub3JnIiwgImJlOWU0YSJd Received: from smtp.codeaurora.org (ec2-35-166-182-171.us-west-2.compute.amazonaws.com [35.166.182.171]) by smtp-out-n07.prod.us-east-1.postgun.com with SMTP id 5f6077f8885efaea0a56a88d (version=TLS1.2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256); Tue, 15 Sep 2020 08:14:48 GMT Received: by smtp.codeaurora.org (Postfix, from userid 1001) id 101CDC433CA; Tue, 15 Sep 2020 08:14:48 +0000 (UTC) X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-caf-mail-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.9 required=2.0 tests=ALL_TRUSTED,BAYES_00, URIBL_BLOCKED autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.codeaurora.org (localhost.localdomain [127.0.0.1]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: nguyenb) by smtp.codeaurora.org (Postfix) with ESMTPSA id 4097EC433C8; Tue, 15 Sep 2020 08:14:47 +0000 (UTC) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Tue, 15 Sep 2020 01:14:47 -0700 From: nguyenb@codeaurora.org To: Bjorn Andersson Cc: cang@codeaurora.org, asutoshd@codeaurora.org, martin.petersen@oracle.com, linux-scsi@vger.kernel.org, linux-arm-msm@vger.kernel.org, Rob Herring , Avri Altman , Vinod Koul , "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" , open list Subject: Re: [PATCH v1 1/2] scsi: dt-bindings: ufs: Add vcc-voltage-level for UFS In-Reply-To: <20200915044154.GB670377@yoga> References: <0a9d395dc38433501f9652a9236856d0ac840b77.1598939393.git.nguyenb@codeaurora.org> <20200915044154.GB670377@yoga> Message-ID: <748d238a3d9e53834a498c6f37f9f3c9@codeaurora.org> X-Sender: nguyenb@codeaurora.org User-Agent: Roundcube Webmail/1.3.9 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2020-09-14 21:41, Bjorn Andersson wrote: > On Tue 01 Sep 01:00 CDT 2020, Bao D. Nguyen wrote: > >> UFS's specifications supports a range of Vcc operating >> voltage levels. Add documentation for the UFS's Vcc voltage >> levels setting. >> >> Signed-off-by: Can Guo >> Signed-off-by: Asutosh Das >> Signed-off-by: Bao D. Nguyen >> --- >> Documentation/devicetree/bindings/ufs/ufshcd-pltfrm.txt | 2 ++ >> 1 file changed, 2 insertions(+) >> >> diff --git a/Documentation/devicetree/bindings/ufs/ufshcd-pltfrm.txt >> b/Documentation/devicetree/bindings/ufs/ufshcd-pltfrm.txt >> index 415ccdd..7257b32 100644 >> --- a/Documentation/devicetree/bindings/ufs/ufshcd-pltfrm.txt >> +++ b/Documentation/devicetree/bindings/ufs/ufshcd-pltfrm.txt >> @@ -23,6 +23,8 @@ Optional properties: >> with "phys" attribute, provides phandle to >> UFS PHY node >> - vdd-hba-supply : phandle to UFS host controller supply >> regulator node >> - vcc-supply : phandle to VCC supply regulator node >> +- vcc-voltage-level : specifies voltage levels for VCC supply. >> + Should be specified in pairs (min, max), >> units uV. > > What exactly are these pairs representing? The pair is the min and max Vcc voltage request to the PMIC chip. As a result, the regulator output voltage would only be in this range. > > Is this supposed to be 3 pairs of (min,max) for vcc, vcc and vccq2 to > be > passed into a regulator_set_voltage() for each regulator? Yes, that's right. I should include the other power supplies in this change as well. > > Or are these some sort of "operating points" for the vcc-supply? > > Regards, > Bjorn > >> - vccq-supply : phandle to VCCQ supply regulator node >> - vccq2-supply : phandle to VCCQ2 supply regulator node >> - vcc-supply-1p8 : For embedded UFS devices, valid VCC range >> is 1.7-1.95V >> -- >> The Qualcomm Innovation Center, Inc. is a member of the Code Aurora >> Forum, >> a Linux Foundation Collaborative Project >>