From: Joakim Tjernlund <Joakim.Tjernlund@transmode.se>
To: linuxppc-dev@ozlabs.org
Subject: mpc83xx SPI driver never calls its probe function
Date: Thu, 02 Nov 2006 14:23:13 +0100 [thread overview]
Message-ID: <4549F141.5050905@transmode.se> (raw)
I am trying to get the driver/spi/spi_mpc83xx.c driver going and I am stuck.
I have tried to add spi_board_info and a platform_device:
static struct fsl_spi_platform_data bcm_platform_data = {
.initial_spmode = 0,
.bus_num = 1,
.max_chipselect = 1,
/* board specific information */
.activate_cs = bcm_cs_activate,
.deactivate_cs = bcm_cs_deactivate,
.sysclk = 266,
};
static struct spi_board_info spi_board_info[] __initdata = { {
.modalias = "bcm5322",
.platform_data = &bcm_platform_data,
.max_speed_hz = 120000,
.bus_num = 1,
.chip_select = 0,
},
};
struct platform_device bcm_5322 = {
.name = "bcm5322",
.id = 1,
.dev = {
.platform_data = &bcm_platform_data,
},
};
and register that with
platform_device_register(&bcm_5322);
spi_register_board_info(spi_board_info, ARRAY_SIZE(spi_board_info))
I also got a protocol driver that does:
static struct spi_driver bcm_driver = {
.driver = {
.name = "bcm5322",
.owner = THIS_MODULE,
},
.probe = bcm_probe,
.remove = __devexit_p(bcm_remove),
};
and then calls spi_register_driver(&bcm_driver);
and I can't get the into the *probe functions. No matter what
combination I try,
the *probe functions for both the protocol driver and the spi_mpc83xx
driver are
never called.
I need some advice on how to enable my
protocol driver and the spi_mpc83xx driver.
Jocke
next reply other threads:[~2006-11-02 13:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-02 13:23 Joakim Tjernlund [this message]
2009-03-06 20:41 ` MC Technology GMBH - Re: mpc83xx SPI driver never calls its probe function Steffen
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=4549F141.5050905@transmode.se \
--to=joakim.tjernlund@transmode.se \
--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 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.