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: Thu, 4 Sep 2008 10:49:55 +0200 [thread overview]
Message-ID: <38b2ab8a0809040149u2bc0342h5c32b87f9277322f@mail.gmail.com> (raw)
In-Reply-To: <20080904103707.557ac764@hyperion.delvare>
On Thu, Sep 4, 2008 at 10:37 AM, Jean Delvare <khali@linux-fr.org> wrote:
> Hi Francis,
>
> On Thu, Sep 4, 2008 at 9:43 AM, Francis Moreau <francis.moro@gmail.com> wrote:
>> I'm wondering why does this flag exist ?
>>
>> Why is a hw monitor device so special so that an I2C bus needs
>> a flag to tell the rest of the world that it support it ?
>
> I don't understand your point. We have I2C_CLASS flags for many I2C
> device types (analog TV, digital TV, etc.) I2C_CLASS_HWMON isn't the
> exception you describe. Look at <linux/i2c.h> for a list of these flags.
>
My question (sorry if that silly) is why do we need these flags at all ?
Can't I2C bus address any kinds of I2C devices ?
What make hwmon devices special so that some I2C adapter can't
talk to them ?
Thanks
--
Francis
next prev parent reply other threads:[~2008-09-04 8:50 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 [this message]
2008-09-04 10:08 ` Jean Delvare
2008-09-05 8:57 ` Francis Moreau
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=38b2ab8a0809040149u2bc0342h5c32b87f9277322f@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