From: Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>
To: petr.jakes-VOAeGBCOg48@public.gmane.org
Cc: i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org
Subject: Re: parport (i2c bus) maximum speed
Date: Fri, 13 Jun 2008 22:56:24 +0200 [thread overview]
Message-ID: <20080613225624.11ad3ece@hyperion.delvare> (raw)
In-Reply-To: <c193ec310806131104wcbba767g602db89266492f31-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On Fri, 13 Jun 2008 20:04:02 +0200, Petr Jakeš wrote:
> Maybe I was not specific enough. Actually there is an SCH3114 chip on our
> motherboard (http://www.smsc.com/main/catalog/sch311x.html ) and lm-sensors
> need dme1737 module for this chip.
> This chip acts as a SMBus master.
I seriously doubt it. I have the SCH311x datasheet under the eyes and
it doesn't even mention SMBus. Neither as a slave nor as a master.
Unless you are using GPIO pins to implement a bit-banged I2C bus using
a custom kernel driver...
The dme1737 driver supports the hardware monitoring block of the
SCH311x. This functionality is accessed over the LPC bus, not the SMBus.
> > I'm confused now. How is I2C/SMBus speed related to lm-sensors at all?
>
>
> I am confused as well :-)
> My feeling was lm-sensors are here to:
>
> 1. enable SMBus/I2C communication (mainly using HW masters presented on
> the motherboards) to communicate with SMBus slaves (mainly presented on the
> PC motherboards, ie clock, temperature, fans ....).
> 2. enable SMBus/I2C communication with some other chips which one can
> connect to the bus
Today, lm-sensors is a library and a set of tools to let users monitor
their hardware, i.e. watch the temperatures, voltages and fans. These
monitoring devices can either be on the SMBus, or on the LPC bus. In
the former case, an additional driver is needed, but that's an
implementation detail. The I2C (SMBus) bus drivers are provided by the
kernel, and so are the hwmon drivers. I would be tempted to say that
the hwmon drivers no longer belong to "lm-sensors", but if you want to
think of them as belonging to lm-sensors, why not.
In the past, the lm-sensors package has included i2c bus drivers,
because they were not yet merged in the kernel and we needed them. But
that was years ago. Thinking of the i2c bus drivers as being part of
lm-sensors today is no good, because then you forget that many hardware
monitoring chips don't need I2C/SMBus at all, and that many I2C/SMBus
devices are not hardware monitoring chips.
The i2c mailing list and the i2c-tools SVN repository are hosted on
lm-sensors.org for historical reasons only. They are completely
independent from the lm-sensors project.
> Because of above mentioned we have done some development and we are able,
> using lm-sensors, to communicate with PIC microcontrolers (they are acting
> as I2C slaves) on the VIA and Unicorn motherboards. From our test it looks
> like we are communicating close to the 100kbps.
You are not using lm-sensors for that. You are using the kernel's i2c
bus drivers. lm-sensors is for hardware monitoring only.
--
Jean Delvare
_______________________________________________
i2c mailing list
i2c@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/i2c
next prev parent reply other threads:[~2008-06-13 20:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-13 13:44 parport (i2c bus) maximum speed Petr Jakeš
[not found] ` <c193ec310806130644p22c1e466g9cd6e6711d4b691b-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-06-13 14:02 ` Jean Delvare
[not found] ` <20080613160205.60b719c3-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2008-06-13 15:55 ` Petr Jakeš
[not found] ` <c193ec310806130855s2227f429pd151466a88539c90-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-06-13 17:17 ` Jean Delvare
[not found] ` <20080613191707.13731136-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2008-06-13 18:04 ` Petr Jakeš
[not found] ` <c193ec310806131104wcbba767g602db89266492f31-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-06-13 20:56 ` Jean Delvare [this message]
[not found] ` <20080613225624.11ad3ece-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2008-06-13 22:32 ` Petr Jakeš
[not found] ` <c193ec310806131532o1e7a8bdasc4856aa09b90e9ae-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-06-14 20:37 ` Jean Delvare
2008-06-23 19:51 ` Cyrille Derory
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=20080613225624.11ad3ece@hyperion.delvare \
--to=khali-puyad+kwke1g9huczpvpmw@public.gmane.org \
--cc=i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org \
--cc=petr.jakes-VOAeGBCOg48@public.gmane.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