From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753508AbbDBOtJ (ORCPT ); Thu, 2 Apr 2015 10:49:09 -0400 Received: from atrey.karlin.mff.cuni.cz ([195.113.26.193]:39622 "EHLO atrey.karlin.mff.cuni.cz" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752419AbbDBOtE (ORCPT ); Thu, 2 Apr 2015 10:49:04 -0400 Date: Thu, 2 Apr 2015 16:49:01 +0200 From: Pavel Machek To: Grazvydas Ignotas Cc: Pali Rohar , sre@debian.org, sre@ring0.de, kernel list , linux-arm-kernel , "linux-omap@vger.kernel.org" , Tony Lindgren , khilman@kernel.org, Aaro Koskinen , ivo.g.dimitrov.75@gmail.com, edubezval@gmail.com, rui.zhang@intel.com, linux-pm@vger.kernel.org, devicetree@vger.kernel.org Subject: Re: [PATCH] ti-soc-thermal: implement omap3 support Message-ID: <20150402144901.GC18125@amd> References: <20150103114632.GA21883@amd> <20150118202447.GA29014@amd> <20150331084234.GA11712@amd> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > > +/* Thresholds and limits for OMAP34XX MPU temperature sensor */ > > +static struct temp_sensor_data omap34xx_mpu_temp_sensor_data = { > > + .min_freq = 32768, > > + .max_freq = 32768, > > + .max_temp = -99000, > > + .min_temp = 99000, > > This looks mixed up. Also, perhaps use -40000 to 125000 to match the > table below? Yes, that looks reasonable, thanks for review. v2 in minute or so. Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html