Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752585AbcCaHQs (ORCPT ); Thu, 31 Mar 2016 03:16:48 -0400 Received: from hqemgate16.nvidia.com ([216.228.121.65]:2413 "EHLO hqemgate16.nvidia.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750972AbcCaHQr (ORCPT ); Thu, 31 Mar 2016 03:16:47 -0400 X-PGP-Universal: processed; by hqnvupgp08.nvidia.com on Thu, 31 Mar 2016 00:15:28 -0700 Message-ID: <56FCCC60.3080303@nvidia.com> Date: Thu, 31 Mar 2016 12:36:08 +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: Mark Brown CC: Bjorn Andersson , Bjorn Andersson , Rob Herring , Pawel Moll , Mark Rutland , Ian Campbell , Liam Girdwood , Bjorn Andersson , Stephen Warren , "devicetree@vger.kernel.org" , "linux-kernel@vger.kernel.org" , Gandhar Dighe , Stuart Yates Subject: Re: [PATCH 1/2] regulator: DT: Add support to scale ramp delay based on platform behavior References: <20160229174751.GQ21240@tuxbot> <20160301022326.GC18327@sirena.org.uk> <56D5111E.6090606@nvidia.com> <20160302033833.GV18327@sirena.org.uk> <56D65F7E.3090907@nvidia.com> <20160302043506.GC18327@sirena.org.uk> <56E81103.8010903@nvidia.com> <56ED0F58.7060005@nvidia.com> <56FBD4A3.7080208@nvidia.com> <20160330181623.GQ2350@sirena.org.uk> In-Reply-To: <20160330181623.GQ2350@sirena.org.uk> 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="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 685 Lines: 17 On Wednesday 30 March 2016 11:46 PM, Mark Brown wrote: > * PGP Signed by an unknown key > > On Wed, Mar 30, 2016 at 06:59:07PM +0530, Laxman Dewangan wrote: > >> Like to add property as "regulator-device-ramp-delay" which will be used for >> PMIC configuration and regulator-ramp-delay will be used for delay >> calculation. This is case when advertised ramp delay does not match with the >> platform measured ramp delay. > Why -device? > This is device specific and just to differentiate with regulator-ramp-delay which is the platform specific. May be there is some other good name. I can think of other name as regulator-typical-ramp-delay, regulator-advertised-ramp-delay etc.