From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755141AbcFHRn5 (ORCPT ); Wed, 8 Jun 2016 13:43:57 -0400 Received: from bh-25.webhostbox.net ([208.91.199.152]:36499 "EHLO bh-25.webhostbox.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751580AbcFHRnz (ORCPT ); Wed, 8 Jun 2016 13:43:55 -0400 Date: Wed, 8 Jun 2016 10:43:38 -0700 From: Guenter Roeck To: "Andrew F. Davis" Cc: Jean Delvare , Jonathan Corbet , linux-hwmon@vger.kernel.org, linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH] hwmon: (tmp401) Add support for TI TMP461 Message-ID: <20160608174338.GC16615@roeck-us.net> References: <20160531162720.460-1-afd@ti.com> <57525C13.3040601@roeck-us.net> <57584E3D.8070501@ti.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <57584E3D.8070501@ti.com> User-Agent: Mutt/1.5.23 (2014-03-12) X-Authenticated_sender: guenter@roeck-us.net X-OutGoing-Spam-Status: No, score=-1.0 X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - bh-25.webhostbox.net X-AntiAbuse: Original Domain - vger.kernel.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - roeck-us.net X-Get-Message-Sender-Via: bh-25.webhostbox.net: authenticated_id: guenter@roeck-us.net X-Authenticated-Sender: bh-25.webhostbox.net: guenter@roeck-us.net X-Source: X-Source-Args: X-Source-Dir: Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Jun 08, 2016 at 11:56:29AM -0500, Andrew F. Davis wrote: [ ... ] > >> static const u8 TMP432_TEMP_MSB_READ[4][3] = { > >> @@ -149,6 +156,7 @@ static const struct i2c_device_id tmp401_id[] = { > >> { "tmp431", tmp431 }, > >> { "tmp432", tmp432 }, > >> { "tmp435", tmp435 }, > >> + { "tmp461", tmp461 }, > > > > Please also provide code in the detect function to auto-detect the chip. > > > > It looks like the ID reg has been removed (at least from the datasheet) > so I'm not sure there is any good way to ID this part. > Outch :-( Well, nothing we can do about that. Even if the register was there and provides a value, it would be undocumented and thus unreliable and unusable. Too bad. Thanks, Guenter