From: Sascha Hauer <s.hauer@pengutronix.de>
To: linuxppc-dev@ozlabs.org
Subject: SPI devices and OF
Date: Wed, 4 Apr 2007 13:09:16 +0200 [thread overview]
Message-ID: <20070404110916.GA9910@localhost.localdomain> (raw)
Hi,
I'm currently writing a driver for the mpc5200 spi controller (the
dedicated one, not the PSC ones).
The driver has the form of a of_platform_driver. My problem is that I
don't know how to define the spi devices on the spi bus. My current
approach is having something like this in the OF tree:
spi@f00 {
device_type = "spi";
compatible = "mpc5200b-spi\0mpc5200-spi";
reg = <f00 20>;
interrupts = <2 d 0 2 e 0>;
interrupt-parent = <500>;
mmc@0 {
device_type = "mmc_spi";
compatible = "mmc_spi";
};
};
I can then parse the children in my spi driver with
while( (child = of_get_next_child(odev->node, child))) {
struct spi_board_info info;
info.max_speed_hz =
info.bus_num =
info.chip_select =
...
spi_register_board_info(&info, 1);
}
I think it will work this way but I found no way getting the
platform_data for the spi devices.
I could also define the spi devices in a board specific c file but there
I would not know which spi bus is which if there is more than one.
Any thoughts on this or am I completely on the wrong track?
Sascha
next reply other threads:[~2007-04-04 11:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-04 11:09 Sascha Hauer [this message]
2007-04-04 11:51 ` SPI devices and OF Vitaly Wool
2007-04-04 16:34 ` Kumar Gala
2007-04-04 17:03 ` Arnd Bergmann
2007-04-04 17:12 ` Kumar Gala
2007-04-05 7:32 ` Benjamin Herrenschmidt
2007-04-05 15:00 ` Milton Miller
2007-04-05 8:33 ` Sascha Hauer
2007-04-04 15:57 ` Milton Miller
2007-04-05 8:50 ` Sascha Hauer
2007-04-05 14:44 ` Milton Miller
2007-04-05 19:11 ` Sascha Hauer
2007-04-05 19:52 ` Arnd Bergmann
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=20070404110916.GA9910@localhost.localdomain \
--to=s.hauer@pengutronix.de \
--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.