From: "Petr Jakeš" <petr.jakes-VOAeGBCOg48@public.gmane.org>
To: Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>
Cc: i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org
Subject: Re: parport (i2c bus) maximum speed
Date: Fri, 13 Jun 2008 20:04:02 +0200 [thread overview]
Message-ID: <c193ec310806131104wcbba767g602db89266492f31@mail.gmail.com> (raw)
In-Reply-To: <20080613191707.13731136-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 2632 bytes --]
>
> > Now we do SMBus communication through dme1737 (we have compatilbe chip on
> > the motherboard). I guess it is not possible to change the bus speed
> because
> > the master (DME1737) is generating the clock frequency of the SMBus.
>
> I don't think the DME1737 can act as an SMBus master, or can it? As far
> as I know the DME1737 is an SMBus slave and multiplexer, but not a
> master. If I am correct then what matters is the actual SMBus master on
> the motherboard.
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.
>
> > Just for your information we have PIC 16F887 connected to the bus as a
> slave
> > (which was really pain and a lot of SW hacking on the PIC side - it looks
> > like Microchip I2C HW/SW implementation does not work properly
> "sometimes").
> >
> > The good thing is we have slaves connected directly to the system SMBus
> and
> > we are doing MISSIVE communication on the bus (motors control, keyboard,
> LCD
> > display, I/O) and we have not observed any single problem (we are using
> > py-smbus binding for the communication).
> >
> > Are there some other ways (HW interfaces etc.) to get lm-sensors work on
> the
> > higher speed?
>
> 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
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.
I was just wondering if it is possible to set the lm-sensors to communicate
faser, so I posted my question to this discussion group.
> Most SMBus controllers on PC motherboards run at low speeds (from 10 to
> 64 kbps), mainly because there's no need for speed when you only have a
> hardware monitoring chip and a couple SPD EEPROMs on the bus. So If you
> want high-speed you'll have to use an additional controller, but I
> don't know of any (except for parallel port or USB do-it-yourself
> adapters, but that's not much faster.)
OK, thanks for this info
Petr Jakes
[-- Attachment #1.2: Type: text/html, Size: 3435 bytes --]
[-- Attachment #2: Type: text/plain, Size: 157 bytes --]
_______________________________________________
i2c mailing list
i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org
http://lists.lm-sensors.org/mailman/listinfo/i2c
next prev parent reply other threads:[~2008-06-13 18:04 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š [this message]
[not found] ` <c193ec310806131104wcbba767g602db89266492f31-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-06-13 20:56 ` Jean Delvare
[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=c193ec310806131104wcbba767g602db89266492f31@mail.gmail.com \
--to=petr.jakes-voaegbcog48@public.gmane.org \
--cc=i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org \
--cc=khali-PUYAD+kWke1g9hUCZPvPmw@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