From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757920AbcCaSt6 (ORCPT ); Thu, 31 Mar 2016 14:49:58 -0400 Received: from hqemgate14.nvidia.com ([216.228.121.143]:13757 "EHLO hqemgate14.nvidia.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752462AbcCaSt4 (ORCPT ); Thu, 31 Mar 2016 14:49:56 -0400 X-PGP-Universal: processed; by hqnvupgp07.nvidia.com on Thu, 31 Mar 2016 11:48:08 -0700 Message-ID: <56FD6ED6.3020507@nvidia.com> Date: Fri, 1 Apr 2016 00:09:18 +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 , "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: <56ED0F58.7060005@nvidia.com> <56FBD4A3.7080208@nvidia.com> <20160330181623.GQ2350@sirena.org.uk> <56FCCC60.3080303@nvidia.com> <20160331165145.GF2350@sirena.org.uk> <56FD5A9F.5050001@nvidia.com> <20160331174741.GO2350@sirena.org.uk> <56FD62BA.3040406@nvidia.com> <20160331183130.GR2350@sirena.org.uk> <56FD6CF7.5080909@nvidia.com> <20160331184553.GS2350@sirena.org.uk> In-Reply-To: <20160331184553.GS2350@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 On Friday 01 April 2016 12:15 AM, Mark Brown wrote: > * PGP Signed by an unknown key > > On Fri, Apr 01, 2016 at 12:01:19AM +0530, Laxman Dewangan wrote: >> On Friday 01 April 2016 12:01 AM, Mark Brown wrote: >>> So the PMIC actually has a setting for the rate you're seeing but for >>> some resaon you can't use it? >> PMIC has the different rate setting what I am seeing on platform (measured). >> HW team measured the ramp dealy with specific configuration of rate setting >> on PMIC which is not default (OTP-One time programmed from Vendor). > That doesn't tell me what happens if you just configure the device to > deliver the rate you're observing... The setting for observed value is not there for device configuration. Device support 5mV/us and 100mV/us. We observed 50mV/us when setting device to 100mV/us.