From: Andre Draszik <kernel@andred.net>
To: linuxppc-embedded@ozlabs.org
Subject: Re: IIC troubles w/ ppc4xx (STB04)
Date: Sun, 16 Apr 2006 07:33:45 +0200 [thread overview]
Message-ID: <4441D739.6040107@andred.net> (raw)
In-Reply-To: <20060416030944.GA20416@gate.ebshome.net>
Hi,
Eugene Surovegin wrote:
> On Sun, Apr 16, 2006 at 03:41:28AM +0200, Andre Draszik wrote:
>> [...]
>> Basically, I get a Data Machine Check as soon as iic->directcntl is
>> accessed. Actually, this register is not described in the (old)
>> documentation I have.
>
> Does everything else work? I mean ordinary I2C access like read/write.
Well, i2c-dev is working fine, so i2c in general is working (w/
2.6.17-rc1). And also the initialization of the ibm i2c driver works
fine, i.e. all other registers can be accessed. It's only the directcntl
which throws the exception.
> If everything else is fine, just comment out that iic_smbus_quick()
> call or just don't use i2c_probe(). It's a hack anyway, because I2C
> spec has no provision for "probing". I wrote this bit-banging
> implementation just to get some people off my back :).
I see :) So if that doesn't work, what is the preferred way of testing
for existence of a device in a kernel module? Should I just
unconditionally i2c_client_register() a static struct and then
i2c_master_send() to see if it works?
> BTW, I never tested my driver on STB4, maybe ocp_defs are wrong (in
> this case i2c will not work at all).
Nope, this is correct, I already checked. :)
Thanks!
Andre'
next prev parent reply other threads:[~2006-04-16 5:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-16 1:41 IIC troubles w/ ppc4xx (STB04) Andre Draszik
2006-04-16 3:09 ` Eugene Surovegin
2006-04-16 5:33 ` Andre Draszik [this message]
2006-04-16 5:57 ` Eugene Surovegin
2006-04-16 6:55 ` Andre Draszik
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=4441D739.6040107@andred.net \
--to=kernel@andred.net \
--cc=linuxppc-embedded@ozlabs.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.