mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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 14:44:30 +0200	[thread overview]
Message-ID: <38b2ab8a0809050544l1914530clec53494e12c77ff5@mail.gmail.com> (raw)
In-Reply-To: <20080905112056.44b7b910@hyperion.delvare>

On Fri, Sep 5, 2008 at 11:20 AM, Jean Delvare <khali@linux-fr.org> wrote:
> On Fri, 5 Sep 2008 10:57:56 +0200, Francis Moreau wrote:
ags probably are useful, but they're are hard coded in adapters...
>
> Nothing prevents you from setting the class flags based on
> platform-specific information if you have a need for that.
>

Just to be sure, do you mean by hacking the adapter source code ?

> That being said, in cases where you have that level of information
> about which devices are present on the I2C bus,

Isn't the case for most of all embedded platforms ?

> you probably want to
> declare the I2C devices at the platform level, and not rely on probing
> at all (so .class is 0).

do you mean by using I2C_BOARD_INFO ?

Thanks
-- 
Francis

  reply	other threads:[~2008-09-05 12:44 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-04  7:43 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
2008-09-05  9:20           ` Jean Delvare
2008-09-05 12:44             ` Francis Moreau [this message]
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=38b2ab8a0809050544l1914530clec53494e12c77ff5@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

all inboxes | Powered by JetHome®