From: Laxmikant Rashinkar <lk.atwork@yahoo.com>
To: Scott Wood <scottwood@freescale.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: i2c driver's probe routine not getting called
Date: Wed, 5 Nov 2008 11:22:35 -0800 (PST) [thread overview]
Message-ID: <789886.15414.qm@web46310.mail.sp1.yahoo.com> (raw)
In-Reply-To: 4911C695.4070401@freescale.com
[-- Attachment #1: Type: text/plain, Size: 981 bytes --]
I actually tried using the in tree i2c-mpc driver before sending out my email. This driver would silently reset the system when i2c accesses took place.
So I guess I'll try to modify the old driver to support new OF interface.
thanks
LK
________________________________
From: Scott Wood <scottwood@freescale.com>
To: Laxmikant Rashinkar <lk.atwork@yahoo.com>
Cc: linuxppc-embedded@ozlabs.org
Sent: Wednesday, November 5, 2008 8:15:17 AM
Subject: Re: i2c driver's probe routine not getting called
Laxmikant Rashinkar wrote:
> I have linux-2.6.27.1 running on a MPC8347 based board.
>
> When my freescale I2C driver is insmoded, it calls platform_driver_register() successfully, but the probe routine doesn't get called.
Is "your" freescale I2C driver different from "the" freescale I2C driver in drivers/i2c/busses/i2c-mpc.c? If so, you'll need to update it to be an of_platform driver like the in-tree driver is (or, just switch to the in-tree driver).
-Scott
[-- Attachment #2: Type: text/html, Size: 1677 bytes --]
prev parent reply other threads:[~2008-11-05 19:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-05 3:30 i2c driver's probe routine not getting called Laxmikant Rashinkar
2008-11-05 16:15 ` Scott Wood
2008-11-05 19:22 ` Laxmikant Rashinkar [this message]
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=789886.15414.qm@web46310.mail.sp1.yahoo.com \
--to=lk.atwork@yahoo.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=scottwood@freescale.com \
/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;
as well as URLs for NNTP newsgroup(s).