All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] I2C addresses of TMP435
Date: Wed, 27 May 2015 13:15:15 +0000	[thread overview]
Message-ID: <5565C363.4050809@roeck-us.net> (raw)
In-Reply-To: <20150527112549.1e5e0e2f@endymion.delvare>

On 05/27/2015 02:25 AM, Jean Delvare wrote:
> Hi Guenter,
>
> In this commit:
> http://www.lm-sensors.org/changeset/6260
>
> You listed 0x37 as a possible address for the TMP435. While this is
> correct, I don't think we want to probe this address. Currently we do
> not probe it for any other chip, and we even removed it explicitly in
> the past:
> http://www.lm-sensors.org/changeset/3233
>
> In the light of recent reports of display breakage caused by
> sensors-detect I would like to play it safe and not probe address 0x37
> (which is used by some EEPROMs as well as the DDC/CI interface.)
>
> While less critical, it might also make sense to remove 0x37 from
> normal_i2c[] in the tmp401 driver. Users with a TMP435 as this address
> can always instantiate it explicitly.
>
> What do you think?
>

Ok with me. 0x37 is also scanned by the atxp1 driver, so I assume
we would have to remove it from both for it to make a difference.

Thanks,
Guenter


_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

  reply	other threads:[~2015-05-27 13:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-27  9:25 [lm-sensors] I2C addresses of TMP435 Jean Delvare
2015-05-27 13:15 ` Guenter Roeck [this message]
2015-05-27 14:58 ` Jean Delvare

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=5565C363.4050809@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=lm-sensors@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.