From mboxrd@z Thu Jan 1 00:00:00 1970 From: Laxman Dewangan Subject: Re: [PATCH V7 1/8] mfd: add device-tree binding doc for PMIC max77620/max20024 Date: Tue, 9 Feb 2016 23:26:41 +0530 Message-ID: <56BA2859.2040605@nvidia.com> References: <1454171931-27752-1-git-send-email-ldewangan@nvidia.com> <1454171931-27752-2-git-send-email-ldewangan@nvidia.com> <20160209154215.GF24522@x1> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from hqemgate15.nvidia.com ([216.228.121.64]:17113 "EHLO hqemgate15.nvidia.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754343AbcBISIS (ORCPT ); Tue, 9 Feb 2016 13:08:18 -0500 In-Reply-To: <20160209154215.GF24522@x1> Sender: linux-gpio-owner@vger.kernel.org List-Id: linux-gpio@vger.kernel.org To: Lee Jones Cc: robh+dt@kernel.org, pawel.moll@arm.com, mark.rutland@arm.com, ijc+devicetree@hellion.org.uk, galak@codeaurora.org, linus.walleij@linaro.org, gnurou@gmail.com, broonie@kernel.org, a.zummo@towertech.it, alexandre.belloni@free-electrons.com, lgirdwood@gmail.com, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org, rtc-linux@googlegroups.com, swarren@nvidia.com, treding@nvidia.com, k.kozlowski@samsung.com, vreddytalla@nvidia.com On Tuesday 09 February 2016 09:12 PM, Lee Jones wrote: > On Sat, 30 Jan 2016, Laxman Dewangan wrote: > > + Normal mode also called as active mode on which all step-down > + regulators, all linear regulators, GPIOs, and the 32kHz > + oscillator are in normal active mode. > + sleep mode: Regulators/GPIOs/clock can go on OFF state based on > "can go on OFF state"? Regulator/GPIO has two states, enable and disable. If sleep mode is configured for these resource and external signal triggers to sleep then this get disabled. >> + Different modes of regulators/clock/GPIOs are controlled by the their >> +FPS configurations. There is different configuration registers for each of >> +these resources. Typical configurations per resource are: >> + FPS source: Attach the resource to required FPS source. When >> + resources are attached to one of FPS source then >> + resournce can be enable/disable when related FPS > Have you used spell check? I suggest you do. My bad, I did but mixed with technical ignorance. Will try best. > >> + source gets the control signal for ON and OFF. >> + Power on slot: Slot number on which resource is ON once FPS source >> + get ON signal. > Can you find another way of explaining this please? Hmm.. Does it look fine: There is 8 slots for each FPS on which resource can get enabled. This property provides the slot number on which resource gets enabled after FPS sequence started. > > > + > +-maxim,enable-sleep: Boolean, enable sleep state of PMIC > We already have bindings for sleeping. Please use a generic one. Which property? Saw sleep property with vendor prefix. From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from hqemgate15.nvidia.com (hqemgate15.nvidia.com. [216.228.121.64]) by gmr-mx.google.com with ESMTPS id tn7si5241069pac.1.2016.02.09.10.08.18 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 09 Feb 2016 10:08:18 -0800 (PST) Message-ID: <56BA2859.2040605@nvidia.com> Date: Tue, 9 Feb 2016 23:26:41 +0530 From: Laxman Dewangan MIME-Version: 1.0 To: Lee Jones CC: , , , , , , , , , , , , , , , , , , Subject: [rtc-linux] Re: [PATCH V7 1/8] mfd: add device-tree binding doc for PMIC max77620/max20024 References: <1454171931-27752-1-git-send-email-ldewangan@nvidia.com> <1454171931-27752-2-git-send-email-ldewangan@nvidia.com> <20160209154215.GF24522@x1> In-Reply-To: <20160209154215.GF24522@x1> Content-Type: text/plain; charset=UTF-8; format=flowed Reply-To: rtc-linux@googlegroups.com List-ID: List-Post: , List-Help: , List-Archive: , List-Unsubscribe: , On Tuesday 09 February 2016 09:12 PM, Lee Jones wrote: > On Sat, 30 Jan 2016, Laxman Dewangan wrote: > > + Normal mode also called as active mode on which all step-down > + regulators, all linear regulators, GPIOs, and the 32kHz > + oscillator are in normal active mode. > + sleep mode: Regulators/GPIOs/clock can go on OFF state based on > "can go on OFF state"? Regulator/GPIO has two states, enable and disable. If sleep mode is configured for these resource and external signal triggers to sleep then this get disabled. >> + Different modes of regulators/clock/GPIOs are controlled by the their >> +FPS configurations. There is different configuration registers for each of >> +these resources. Typical configurations per resource are: >> + FPS source: Attach the resource to required FPS source. When >> + resources are attached to one of FPS source then >> + resournce can be enable/disable when related FPS > Have you used spell check? I suggest you do. My bad, I did but mixed with technical ignorance. Will try best. > >> + source gets the control signal for ON and OFF. >> + Power on slot: Slot number on which resource is ON once FPS source >> + get ON signal. > Can you find another way of explaining this please? Hmm.. Does it look fine: There is 8 slots for each FPS on which resource can get enabled. This property provides the slot number on which resource gets enabled after FPS sequence started. > > > + > +-maxim,enable-sleep: Boolean, enable sleep state of PMIC > We already have bindings for sleeping. Please use a generic one. Which property? Saw sleep property with vendor prefix. -- -- You received this message because you are subscribed to "rtc-linux". Membership options at http://groups.google.com/group/rtc-linux . Please read http://groups.google.com/group/rtc-linux/web/checklist before submitting a driver. --- You received this message because you are subscribed to the Google Groups "rtc-linux" group. To unsubscribe from this group and stop receiving emails from it, send an email to rtc-linux+unsubscribe@googlegroups.com. For more options, visit https://groups.google.com/d/optout. From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756633AbcBISIU (ORCPT ); Tue, 9 Feb 2016 13:08:20 -0500 Received: from hqemgate15.nvidia.com ([216.228.121.64]:17113 "EHLO hqemgate15.nvidia.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754343AbcBISIS (ORCPT ); Tue, 9 Feb 2016 13:08:18 -0500 X-PGP-Universal: processed; by hqnvupgp07.nvidia.com on Tue, 09 Feb 2016 10:07:41 -0800 Message-ID: <56BA2859.2040605@nvidia.com> Date: Tue, 9 Feb 2016 23:26:41 +0530 From: Laxman Dewangan User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: Lee Jones CC: , , , , , , , , , , , , , , , , , , Subject: Re: [PATCH V7 1/8] mfd: add device-tree binding doc for PMIC max77620/max20024 References: <1454171931-27752-1-git-send-email-ldewangan@nvidia.com> <1454171931-27752-2-git-send-email-ldewangan@nvidia.com> <20160209154215.GF24522@x1> In-Reply-To: <20160209154215.GF24522@x1> X-Originating-IP: [10.19.65.30] X-ClientProxiedBy: DRUKMAIL102.nvidia.com (10.25.59.20) To bgmail102.nvidia.com (10.25.59.11) Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tuesday 09 February 2016 09:12 PM, Lee Jones wrote: > On Sat, 30 Jan 2016, Laxman Dewangan wrote: > > + Normal mode also called as active mode on which all step-down > + regulators, all linear regulators, GPIOs, and the 32kHz > + oscillator are in normal active mode. > + sleep mode: Regulators/GPIOs/clock can go on OFF state based on > "can go on OFF state"? Regulator/GPIO has two states, enable and disable. If sleep mode is configured for these resource and external signal triggers to sleep then this get disabled. >> + Different modes of regulators/clock/GPIOs are controlled by the their >> +FPS configurations. There is different configuration registers for each of >> +these resources. Typical configurations per resource are: >> + FPS source: Attach the resource to required FPS source. When >> + resources are attached to one of FPS source then >> + resournce can be enable/disable when related FPS > Have you used spell check? I suggest you do. My bad, I did but mixed with technical ignorance. Will try best. > >> + source gets the control signal for ON and OFF. >> + Power on slot: Slot number on which resource is ON once FPS source >> + get ON signal. > Can you find another way of explaining this please? Hmm.. Does it look fine: There is 8 slots for each FPS on which resource can get enabled. This property provides the slot number on which resource gets enabled after FPS sequence started. > > > + > +-maxim,enable-sleep: Boolean, enable sleep state of PMIC > We already have bindings for sleeping. Please use a generic one. Which property? Saw sleep property with vendor prefix.