From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752377AbcAFOa2 (ORCPT ); Wed, 6 Jan 2016 09:30:28 -0500 Received: from hqemgate15.nvidia.com ([216.228.121.64]:14774 "EHLO hqemgate15.nvidia.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751918AbcAFOa1 (ORCPT ); Wed, 6 Jan 2016 09:30:27 -0500 X-PGP-Universal: processed; by hqnvupgp08.nvidia.com on Wed, 06 Jan 2016 06:26:12 -0800 Message-ID: <568D22AA.8030902@nvidia.com> Date: Wed, 6 Jan 2016 19:50:26 +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 , Mark Brown CC: , , , , , , Subject: Re: [PATCH 1/1] regulator: max8973: add support for junction thermal warning References: <1452060922-24426-1-git-send-email-ldewangan@nvidia.com> <20160106121857.GW6588@sirena.org.uk> <568D064A.8080609@nvidia.com> <20160106123735.GX6588@sirena.org.uk> <20160106142521.GA11188@rob-hp-laptop> In-Reply-To: <20160106142521.GA11188@rob-hp-laptop> 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 Wednesday 06 January 2016 07:55 PM, Rob Herring wrote: > On Wed, Jan 06, 2016 at 12:37:35PM +0000, Mark Brown wrote: >> On Wed, Jan 06, 2016 at 05:49:22PM +0530, Laxman Dewangan wrote: >>> On Wednesday 06 January 2016 05:48 PM, Mark Brown wrote: >>>> * PGP Signed by an unknown key >>>> On Wed, Jan 06, 2016 at 11:45:22AM +0530, 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 needs to specify what the values are - it looks like it's raw >>>> register values but I'd have expected from this that it'd be an actual >>>> temperature. >>> I tried to roundoff to the next higher threshold when supported value (120 >>> or 140 degC) is not provided in driver. But it is fine to me to specify the >>> possible value setting here and DT binding doc. Will do on next patch. >> I don't really mind which you use so long as the documentation is clear. > I prefer that degrees are used rather than register values. > From DT/platform, any values can be passed. Driver will round off to next higher side. The document details will only provide what is supported by the PMIC device. E.g. It can pass to ,<=120C and driver will set nearest threshold which is 120C. If it is >120C then it will set to 140C. From mboxrd@z Thu Jan 1 00:00:00 1970 From: Laxman Dewangan Subject: Re: [PATCH 1/1] regulator: max8973: add support for junction thermal warning Date: Wed, 6 Jan 2016 19:50:26 +0530 Message-ID: <568D22AA.8030902@nvidia.com> References: <1452060922-24426-1-git-send-email-ldewangan@nvidia.com> <20160106121857.GW6588@sirena.org.uk> <568D064A.8080609@nvidia.com> <20160106123735.GX6588@sirena.org.uk> <20160106142521.GA11188@rob-hp-laptop> Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20160106142521.GA11188@rob-hp-laptop> Sender: linux-kernel-owner@vger.kernel.org To: Rob Herring , Mark Brown Cc: pawel.moll@arm.com, mark.rutland@arm.com, ijc+devicetree@hellion.org.uk, galak@codeaurora.org, lgirdwood@gmail.com, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org List-Id: devicetree@vger.kernel.org On Wednesday 06 January 2016 07:55 PM, Rob Herring wrote: > On Wed, Jan 06, 2016 at 12:37:35PM +0000, Mark Brown wrote: >> On Wed, Jan 06, 2016 at 05:49:22PM +0530, Laxman Dewangan wrote: >>> On Wednesday 06 January 2016 05:48 PM, Mark Brown wrote: >>>> * PGP Signed by an unknown key >>>> On Wed, Jan 06, 2016 at 11:45:22AM +0530, 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 needs to specify what the values are - it looks like it's raw >>>> register values but I'd have expected from this that it'd be an actual >>>> temperature. >>> I tried to roundoff to the next higher threshold when supported value (120 >>> or 140 degC) is not provided in driver. But it is fine to me to specify the >>> possible value setting here and DT binding doc. Will do on next patch. >> I don't really mind which you use so long as the documentation is clear. > I prefer that degrees are used rather than register values. > From DT/platform, any values can be passed. Driver will round off to next higher side. The document details will only provide what is supported by the PMIC device. E.g. It can pass to ,<=120C and driver will set nearest threshold which is 120C. If it is >120C then it will set to 140C.