From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756227AbbLQL4N (ORCPT ); Thu, 17 Dec 2015 06:56:13 -0500 Received: from mail1.bemta14.messagelabs.com ([193.109.254.114]:58852 "EHLO mail1.bemta14.messagelabs.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751464AbbLQL4L (ORCPT ); Thu, 17 Dec 2015 06:56:11 -0500 X-Env-Sender: Andreas.Werner@men.de X-Msg-Ref: server-5.tower-193.messagelabs.com!1450353368!10897909!1 X-Originating-IP: [80.255.6.145] X-StarScan-Received: X-StarScan-Version: 7.35.1; banners=-,-,- X-VirusChecked: Checked X-PGP-Universal: processed; by keys.men.de on Thu, 17 Dec 2015 12:56:08 +0100 Date: Thu, 17 Dec 2015 12:54:20 +0100 From: Andreas Werner To: Jean Delvare CC: Andreas Werner , Guenter Roeck , , , Subject: Re: [lm-sensors] LM90 driver and ti tmp461 detection Message-ID: <20151217115420.GB2349@awelinux> References: <20151210120856.GA27765@awelinux> <5669AB55.5030309@roeck-us.net> <20151210171231.GA28022@awelinux> <20151212110842.10e7693e@endymion.delvare> <20151215151123.GA2349@awelinux> <20151217124808.63f8f54f@endymion.delvare> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: <20151217124808.63f8f54f@endymion.delvare> User-Agent: Mutt/1.5.24 (2015-08-30) X-Originating-IP: [192.1.1.170] X-ClientProxiedBy: MEN-EX01.intra.men.de (192.168.1.1) To MEN-EX01.intra.men.de (192.168.1.1) X-EXCLAIMER-MD-CONFIG: e4841e51-7998-49c0-ba41-8b8a0e2d8962 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Dec 17, 2015 at 12:48:08PM +0100, Jean Delvare wrote: > Hi Andreas, > > On Tue, 15 Dec 2015 16:11:24 +0100, Andreas Werner wrote: > > here is the register dump of the tmp461. > > Thanks. > > > It seemse that we really cannot detect if it is a tmp461 or a tmp451. > > Also the magic "ID Register" offset 0xff is 0x00 for both devices. > > I would use register 0x16, which doesn't exist but reads 0x00 on the > TMP451. It could in theory also read 0x00 on the TMP461 but only if > both channels are disabled, which makes little sense. More likely at > least one channel will be enabled so you'll have value 0x01-0x03 if > this is a TMP461. > Yes you are right. Both channels are enabled during POR, so the chance to have a 0x00 as in the TMP451 will be very low. > -- > Jean Delvare > SUSE L3 Support