All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: "Wilson, David T. (GSFC-5870)" <david.wilson@nasa.gov>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-hwmon@vger.kernel.org" <linux-hwmon@vger.kernel.org>
Subject: Re: Potential issue with smb word operations for tmp461 device in tmp401 driver
Date: Fri, 15 Oct 2021 15:27:19 -0700	[thread overview]
Message-ID: <20211015222719.GG1480361@roeck-us.net> (raw)
In-Reply-To: <SA1PR09MB7440BF952778F0DB8138747DE7B99@SA1PR09MB7440.namprd09.prod.outlook.com>

Hi,

On Fri, Oct 15, 2021 at 05:43:54PM +0000, Wilson, David T. (GSFC-5870) wrote:
> Hi,
> 
> I am reporting what I believe is a potential issue in the tmp401 driver for the tmp461 device specifically. I am new to reporting issues, so I apologize in advance if I've provided insufficient information for an issue report.
> 
> The problem I'm encountering is that when I use the tmp401 linux driver to read temperature values from the tmp461, all of the read temperature values end with 996 (e.g. 33996, 38996, etc...).
> 
> Looking further into the tmp401 commit messages, I see that the driver was changed to use smb word operations instead of separate byte operations. Although the other supported devices (i.e. tmp432, etc...) are noted to support 16-bit read operations in their respective datasheets, I see no indications of 16-bit read support in the tmp461 datasheet, which is supported by my inquiry in the TI forums (https://e2e.ti.com/support/sensors-group/sensors/f/sensors-forum/1044935/tmp461-linux-driver-support-and-16-bit-temperature-register-reads).
> 
> Reverting the driver to the commit before the smb word change, I am then able to read temperature values that do not end only with 996. As a result, I believe that the tmp461 support may be partially broken by the switch to smb word operations.
> 

Thanks a lot for the report. Can you send me a register dump for the tmp461 ?

Thanks,
Guenter

  reply	other threads:[~2021-10-15 22:27 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-15 17:43 Potential issue with smb word operations for tmp461 device in tmp401 driver Wilson, David T. (GSFC-5870)
2021-10-15 22:27 ` Guenter Roeck [this message]
2021-10-16  2:33   ` [EXTERNAL] " Wilson, David T. (GSFC-5870)
2021-10-16  3:31     ` Guenter Roeck
2021-10-19  4:56 ` Guenter Roeck
2021-10-19  5:42   ` [EXTERNAL] " Wilson, David T. (GSFC-5870)
2021-10-19 14:18     ` Guenter Roeck
2021-10-21  5:37       ` Wilson, David T. (GSFC-5870)
2021-10-21  7:07         ` Guenter Roeck
2021-10-28  1:54           ` Wilson, David T. (GSFC-5870)
2021-10-28  4:03             ` Guenter Roeck
2021-10-28 16:20             ` Guenter Roeck

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20211015222719.GG1480361@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=david.wilson@nasa.gov \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.