All of lore.kernel.org
 help / color / mirror / Atom feed
From: r.marek@sh.cvut.cz (Rudolf Marek)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] i2c -dev and i2c bus driver
Date: Tue, 08 Nov 2005 16:47:49 +0000	[thread overview]
Message-ID: <4370C89C.5090309@sh.cvut.cz> (raw)
In-Reply-To: <24EB6743805F45478251E18DEBF3F6BE8133DD@csserver.circadiant.com>


> yes, that's what I loaded after booing and using i2c-dev driver to talk to
> our i2c device, for the devices connnected to the ACB 2 of superIO from the
> microporcessor, every thing works. however, for the device, connected to
> ACB 1 of superIO, I won't be able to talk to them.

Hmm bad is that I dont know the hardware.
But from the driver i can see:


         for (i = 0; i < MAX_DEVICES; ++i) {
                if (base[i] > 0)
                        rc = scx200_acb_create(base[i], i);
        }

And there are two base defined.
So this could create two busses.

When you modprobe i2c-dev and the scx driver you should see
in

i2cdump -l

Listed two ACB busses
Do you see them?

If so I would suggest:

1) plug your device to ACB 2 where it works
   do: i2cdetect (put acb2 bus number here)
       i2cdump (put acb2 bus number here) 0xyourdeviceaddr

2) repeat with plugged to ACB1

Please post results here. Also, please point me to some documenattion of ACCESS bus... I'm really very short with my time...

Thanks
Regards
Rudolf

  parent reply	other threads:[~2005-11-08 16:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-03 20:57 [lm-sensors] i2c -dev and i2c bus driver Howard Wang
2005-11-04 20:40 ` Rudolf Marek
2005-11-04 23:55 ` Rudolf Marek
2005-11-07 17:49 ` Howard Wang
2005-11-07 18:00 ` Rudolf Marek
2005-11-08  0:55 ` Howard Wang
2005-11-08 16:47 ` Rudolf Marek [this message]
2005-11-09 15:34 ` Howard Wang
2005-11-11  0:43 ` Howard Wang
2005-11-11 13:02 ` Rudolf Marek

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=4370C89C.5090309@sh.cvut.cz \
    --to=r.marek@sh.cvut.cz \
    --cc=lm-sensors@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.