From: "Francis Moreau" <francis.moro@gmail.com>
To: "Jean Delvare" <khali@linux-fr.org>
Cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
i2c@lm-sensors.org
Subject: Re: qestion about I2C_CLASS_HWMON flag
Date: Fri, 5 Sep 2008 10:57:56 +0200 [thread overview]
Message-ID: <38b2ab8a0809050157yfb21b08v23ae368d3337c1ca@mail.gmail.com> (raw)
In-Reply-To: <20080904120855.7e7b9720@hyperion.delvare>
Good morning Jean,
On Thu, Sep 4, 2008 at 12:08 PM, Jean Delvare <khali@linux-fr.org> wrote:
> In general they can, yes (where they can't, it's due to restrictions in
> protocol implementations, not device types.) But this isn't a matter of
> what devices can be on the bus. This is a matter of what devices can be
> probed for on a given bus. For example, hardware monitoring drivers
> which handle I2C devices, make sure that I2C_CLASS_HWMON is set before
> probing I2C addresses on a given bus in search of a device to
> auto-detect. On the other hand, if they are merely attaching to an I2C
> device which has already been instantiated (and thus no probing is
> needed) they do not care about the class. The reason for this mechanism
> is that probing can be risky, so we want to limit it to what is
> strictly needed. For example, there is no point in probing the I2C bus
> of a TV adapter for hardware monitoring chips - there simply can't be
> any there. If there ever was any, that would be such a special case
> that we would instantiate the I2C device in question explicitly from
> the adapter code, so we have no need for probing.
OK but which devices that can be connected to an I2C bus is platform specific,
isn't it ? For example, an I2C adapter can be used in a TV and in that
case there
may be no point to probe for a HW mon chips but this same I2C adapter can be
used by other platforms in a different context where there's a HW mon chip.
So the flags probably are useful, but they're are hard coded in adapters...
Sorry if I'm still missing something.
--
Francis
next prev parent reply other threads:[~2008-09-05 8:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-04 7:43 qestion about I2C_CLASS_HWMON flag Francis Moreau
2008-09-04 7:58 ` Jean Delvare
2008-09-04 8:04 ` Francis Moreau
2008-09-04 8:05 ` Francis Moreau
2008-09-04 8:37 ` Jean Delvare
2008-09-04 8:49 ` Francis Moreau
2008-09-04 10:08 ` Jean Delvare
2008-09-05 8:57 ` Francis Moreau [this message]
2008-09-05 9:20 ` Jean Delvare
2008-09-05 12:44 ` Francis Moreau
2008-09-05 13:11 ` Jean Delvare
2008-09-05 13:38 ` Francis Moreau
2008-09-05 13:49 ` Jean Delvare
2008-09-05 14:44 ` Francis Moreau
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=38b2ab8a0809050157yfb21b08v23ae368d3337c1ca@mail.gmail.com \
--to=francis.moro@gmail.com \
--cc=i2c@lm-sensors.org \
--cc=khali@linux-fr.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox