From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-4.1 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SIGNED_OFF_BY, SPF_PASS autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 0E005C43381 for ; Wed, 13 Feb 2019 23:38:43 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id B7C83222C9 for ; Wed, 13 Feb 2019 23:38:42 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=akkea.ca header.i=@akkea.ca header.b="t3iXeMnv" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2390974AbfBMXil (ORCPT ); Wed, 13 Feb 2019 18:38:41 -0500 Received: from node.akkea.ca ([192.155.83.177]:57794 "EHLO node.akkea.ca" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728875AbfBMXik (ORCPT ); Wed, 13 Feb 2019 18:38:40 -0500 Received: by node.akkea.ca (Postfix, from userid 33) id 4FAE14E204B; Wed, 13 Feb 2019 23:38:40 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akkea.ca; s=mail; t=1550101120; bh=FnQNYygIwD1JkOGeUp/htcq1DTGYJpG2VKo6H9w9vAU=; h=To:Subject:Date:From:Cc:In-Reply-To:References; b=t3iXeMnvD1kyT3iapmFDEqnU3/Lx/drQVkeMB9fsIw6WzftkeD4dOjRKce63M71R+ HDQHNHVxme5qM64xv/yiBNUyObo4MfSI4a3QxwI2EfAmLVgFacntSoDBc803A836aV cMI4JvgVh2t1++eVrn0xPcXXSJPWN4Bw/DnJz5LA= To: Matti Vaittinen Subject: Re: [PATCH v2 1/3] devicetree: bindings: bd718x7: document HW state related ROHM specific properties X-PHP-Originating-Script: 1000:rcube.php MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Wed, 13 Feb 2019 15:38:40 -0800 From: Angus Ainslie Cc: mazziesaccount@gmail.com, Lee Jones , Rob Herring , Mark Rutland , Liam Girdwood , Mark Brown , devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, heikki.haikola@fi.rohmeurope.com, mikko.mutanen@fi.rohmeurope.com, =?UTF-8?Q?Robin_Gong_=E2=80=8E?= , =?UTF-8?Q?Elven?= =?UTF-8?Q?_Wang_=E2=80=8E?= , =?UTF-8?Q?Anson_Huan?= =?UTF-8?Q?g_=E2=80=8E?= , linux-kernel-owner@vger.kernel.org In-Reply-To: <501fe1a68a9ad0987ddc0d3f559b2bdd1f65a5b7.1550050645.git.matti.vaittinen@fi.rohmeurope.com> References: <501fe1a68a9ad0987ddc0d3f559b2bdd1f65a5b7.1550050645.git.matti.vaittinen@fi.rohmeurope.com> Message-ID: <044d28c6ea1f9dd58f4c1942411aaf58@www.akkea.ca> X-Sender: angus@akkea.ca User-Agent: Roundcube Webmail/1.1.3 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Matti, On 2019-02-13 01:50, Matti Vaittinen wrote: > Add ROHM BD71837 / BD71847 specific device tree bindings for > controlling the PMIC shutdown/reset states and voltages for > different HW states. The PMIC was designed to be used with NXP > i.MX8 SoC and it supports SNVS low power state which seems to > be typical for NXP i.MX SoCs. However, when SNVS is used we must > not allow SW to control enabling/disabling those regulators which > are crucial for system to boot as there is a HW limitation which > causes SW controlled regulators to be kept shut down after SNVS > reset. > > Allow setting the SNVS to be used as reset target state and allow > marking those regulators which are critical for boot. > > Signed-off-by: Matti Vaittinen > --- > .../devicetree/bindings/mfd/rohm,bd71837-pmic.txt | 15 +++++++++++ > .../bindings/regulator/rohm,bd71837-regulator.txt | 30 > ++++++++++++++++++++++ > 2 files changed, 45 insertions(+) > > diff --git > a/Documentation/devicetree/bindings/mfd/rohm,bd71837-pmic.txt > b/Documentation/devicetree/bindings/mfd/rohm,bd71837-pmic.txt > index a4b056761eaa..f07c32975315 100644 > --- a/Documentation/devicetree/bindings/mfd/rohm,bd71837-pmic.txt > +++ b/Documentation/devicetree/bindings/mfd/rohm,bd71837-pmic.txt > @@ -23,6 +23,21 @@ Required properties: > > Optional properties: > - clock-output-names : Should contain name for output clock. > +- rohm,reset-snvs-powered : Transfer BD718x7 to SNVS state at reset. > + > +The BD718x7 supports two different HW states as reset target states. > States > +are called as SNVS and READY. At READY state all the PMIC power > outputs go > +down and OTP is reload. At the SNVS state all other logic and external > +devices apart from the SNVS power domain are shut off. Please refer to > NXP > +i.MX8 documentation for further information regarding SNVS state. When > a > +reset is done via SNVS state the PMIC OTP data is not reload. This > cause > + It looks like there is some text missing here. > +There is a HW quirk in BD718x7 which causes power outputs that have > been > +under SW control to stay down when reset has switched power state to > SNVS. > +If reset is done via READY state the power outputs will be set to HW > control > +by OTP loading. Thus the reset target state is set to READY by > default. If > +SNVS state is used the boot crucial regulators must have the > +regulator-always-on and regulator-boot-on properties set in regulator > node. > > Example: > > diff --git > a/Documentation/devicetree/bindings/regulator/rohm,bd71837-regulator.txt > b/Documentation/devicetree/bindings/regulator/rohm,bd71837-regulator.txt > index 4b98ca26e61a..4a05cbf915ee 100644 > --- > a/Documentation/devicetree/bindings/regulator/rohm,bd71837-regulator.txt > +++ > b/Documentation/devicetree/bindings/regulator/rohm,bd71837-regulator.txt > @@ -27,8 +27,38 @@ BUCK1, BUCK2, BUCK3, BUCK4, BUCK5, BUCK6 > LDO1, LDO2, LDO3, LDO4, LDO5, LDO6 > > Optional properties: > +- rohm,dvs-run-voltage : PMIC default "RUN" state voltage in uV. > + See below table for bucks which support this. > +- rohm,dvs-idle-voltage : PMIC default "IDLE" state voltage in uV. > + See below table for bucks which support this. > +- rohm,dvs-suspend-voltage : PMIC default "SUSPEND" state voltage in > uV. > + See below table for bucks which support this. > - Any optional property defined in bindings/regulator/regulator.txt > > +Supported default DVS states: > + > +BD71837: > +buck | dvs-run-voltage | dvs-idle-voltage | dvs-suspend-voltage > +----------------------------------------------------------------------------- > +1 | supported | supported | supported > +---------------------------------------------------------------------------- > +2 | supported | supported | not supported > +---------------------------------------------------------------------------- > +3 | supported | not supported | not supported > +---------------------------------------------------------------------------- > +4 | supported | not supported | not supported > +---------------------------------------------------------------------------- > +rest | not supported | not supported | not supported > + > +BD71847: > +buck | dvs-run-voltage | dvs-idle-voltage | dvs-suspend-voltage > +----------------------------------------------------------------------------- > +1 | supported | supported | supported > +---------------------------------------------------------------------------- > +2 | supported | supported | not supported > +---------------------------------------------------------------------------- > +rest | not supported | not supported | not supported > + > Example: Could you add an example of the optional properties ? Thanks Angus > regulators { > buck1: BUCK1 { > -- > 2.14.3