On Thu, Mar 31, 2016 at 10:43:03PM +0530, Laxman Dewangan wrote: > We need two properties, one what we measured in platform and second one for > what we want to program PMIC. This is for the case where vendor advertised > ramp delay is not same as measured due to platform design. What makes you say that we need two properties? > Based on discussion, regulator-ramp-delay is for measured ramp delay in > platform. So we will need another property for configuring PMIC. So as well as delaying in the kernel to cover the ramp time you want to configure something in the PMIC? What are you trying to configure in the PMIC? How will the PMIC driver meaningfully interpret a generic property given that the whole point here is that the PMIC is unable to deliver in spec behaviour?