From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752679AbcBLNn0 (ORCPT ); Fri, 12 Feb 2016 08:43:26 -0500 Received: from hqemgate14.nvidia.com ([216.228.121.143]:9599 "EHLO hqemgate14.nvidia.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752424AbcBLNnY (ORCPT ); Fri, 12 Feb 2016 08:43:24 -0500 X-PGP-Universal: processed; by hqnvupgp08.nvidia.com on Fri, 12 Feb 2016 05:43:40 -0800 Message-ID: <56BDDEBB.8060105@nvidia.com> Date: Fri, 12 Feb 2016 19:01:39 +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: Rob Herring CC: Mark Brown , Pawel Moll , "Mark Rutland" , Ian Campbell , Kumar Gala , Liam Girdwood , "devicetree@vger.kernel.org" , "linux-kernel@vger.kernel.org" Subject: Re: [PATCH V2] regulator: max8973: add support for junction thermal warning References: <1452096440-6476-1-git-send-email-ldewangan@nvidia.com> In-Reply-To: X-Originating-IP: [10.19.65.30] X-ClientProxiedBy: BGMAIL101.nvidia.com (10.25.59.10) 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 Friday 12 February 2016 07:06 PM, Rob Herring wrote: > On Wed, Jan 6, 2016 at 10:07 AM, Laxman Dewangan wrote: > > Enhanced transient response (ETR) will affect the configuration of CKADV. > +-maxim,junction-temp-warning: Junction temp warning on which device generates > + warning interrupts. This is in millicelcius. > Please append units: maxim,junction-temp-warning-millicelsius or > perhaps maxim,junction-warn-millicelsius to shorten it a bit. This is very generic which is there on most of PMIC devices from Maxim, TI etc. So can we make it generic i.e. do not prefix with vendor name like "junction-warn-millicelsius"?