From: "Reeve Yang" <yang.reeve@gmail.com>
To: linuxppc-dev@ozlabs.org
Subject: spi_mpc83xx driver question
Date: Fri, 29 Dec 2006 00:46:00 +0000 [thread overview]
Message-ID: <198592450612281646y7de55a9ep3d0361f90abb0f94@mail.gmail.com> (raw)
Hi there,
I'm developing mmc driver based on spi_mpc83xx driver. Our mmc card is
connect through SPI to mpc8343E. Now the SPI controller is up, but
protocol driver has problem. I have following piece of code:
static struct spi_driver spimmc_driver = {
.driver = {
.name = "spimmc",
.bus = &spi_bus_type,
.owner = THIS_MODULE,
},
.probe = spimmc_probe,
.remove = __devexit_p(spimmc_remove),
.suspend = spimmc_suspend,
.resume = spimmc_resume,
};
static int __init spimmc_init (void)
{
return spi_register_driver(&spimmc_driver);
}
module_init(spimmc_init);
Looking at sysfs, the spimmc driver is there, but ".probe" has never
been called. My question is, how this "probe" callback get called
during init? What could be the reason for that guy not being called?
If I call spimmc_probe driectly from spi_mpc83xx.c (for experiment),
kernel failure happened during boot:
[ 26.484876] Badness in kref_get at lib/kref.c:32
[ 26.489627] Call trace: [c0004fb0] [c0005200] [c00048d0]
[c00e3ad0] [c010a780] [c010af94] [c013beec] [c013b064] [c013df68]
[c0256474] [c010bea
[ 26.508407] Oops: kernel access of bad area, sig: 11 [#1]
I really need help from someone to explain it....
Thanks.
- Reeve
next reply other threads:[~2006-12-29 0:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-29 0:46 Reeve Yang [this message]
2006-12-29 18:27 ` spi_mpc83xx driver question Kumar Gala
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=198592450612281646y7de55a9ep3d0361f90abb0f94@mail.gmail.com \
--to=yang.reeve@gmail.com \
--cc=linuxppc-dev@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 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).