From: khali@linux-fr.org (Jean Delvare)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] [PATCH] I2C W83792D driver 1/3
Date: Wed, 27 Jul 2005 12:57:40 +0000 [thread overview]
Message-ID: <L0DMuJPu.1122461474.7585580.khali@localhost> (raw)
In-Reply-To: <20050727092431.10185.qmail@desitka.sh.cvut.cz>
Hi Rduolf,
On 2005-07-27, Rudolf Marek wrote:
> Uff my bad I did not check this. On the other hand the address can be
> changed to virtually any address via CR48, with condition that two lowest
> bits cant be changed.
I think the two lowest bits can be changed. Their initial value is set at
power-up time depending on two pin levels, just like is the case for
subclients, but I do believe this can be changed afterwards, just like
is the case for subclients too. Not that it really matters...
> Should we go for range 0x20 - 0x2f ?
No. That's what we did for it87, result is that since the driver was
written, only default address 0x2d was seen. I can't think of any
reason why someone would use a different address than the four possible
power-up default ones, especially since this chip has no other interface
IIRC, so the power-up address would have to be used at least once to
change the address at CR48. If the power-up address works to do that,
there is no reason not to use it afterwards as well.
So please stick to 0x2c - 0x2f. If anyone ever needs more, that's
exactly what the probe parameter is for (but I'm quite certain it will
never happen).
Thanks,
--
Jean Delvare
next prev parent reply other threads:[~2005-07-27 12:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-27 11:59 [lm-sensors] [PATCH] I2C W83792D driver 1/3 R.Marek
2005-07-27 12:19 ` Jean Delvare
2005-07-27 12:48 ` Rudolf Marek
2005-07-27 12:57 ` Jean Delvare [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-09-05 23:49 [lm-sensors] [PATCH] I2C: " Greg KH
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=L0DMuJPu.1122461474.7585580.khali@localhost \
--to=khali@linux-fr.org \
--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.