* [PATCH v3] sysdev,mv64x60: MV64x60 device bus
@ 2008-04-29 20:26 Remi Machet
2008-04-29 20:46 ` Dale Farnsworth
2008-04-30 4:35 ` Paul Mackerras
0 siblings, 2 replies; 3+ messages in thread
From: Remi Machet @ 2008-04-29 20:26 UTC (permalink / raw)
To: Paul Mackerras, Dale Farnsworth, Stephen Rothwell; +Cc: linuxppc-dev
Follow up of my email of 4/16/2008 titled "MV64x60 device bus".
For each mv64360 entry in the OpenFirmware database, add the
registration of an of_bus to take care of devices connected to
the MV64x60 asynchronous devices controller.
Signed-off-by: Remi Machet (rmachet@slac.stanford.edu)
---
Use the compatible field to detect devices to register (on Dale Farnsworth
suggestion).
Added __initdata to variable of_mv64x60_devices (thanks to Stephen Rothwell
for pointing that out).
arch/powerpc/sysdev/mv64x60_dev.c | 10 ++++++++++
1 files changed, 10 insertions(+)
diff --git a/arch/powerpc/sysdev/mv64x60_dev.c b/arch/powerpc/sysdev/mv64x60_dev.c
index 41af122..c38695e 100644
--- a/arch/powerpc/sysdev/mv64x60_dev.c
+++ b/arch/powerpc/sysdev/mv64x60_dev.c
@@ -15,6 +15,7 @@
#include <linux/console.h>
#include <linux/mv643xx.h>
#include <linux/platform_device.h>
+#include <linux/of_platform.h>
#include <asm/prom.h>
@@ -25,6 +26,11 @@
* PowerPC of_platform_bus_type. They support platform_bus_type instead.
*/
+static struct of_device_id __initdata of_mv64x60_devices[] = {
+ { .compatible = "marvell,mv64306-devctrl", },
+ {}
+};
+
/*
* Create MPSC platform devices
*/
@@ -482,6 +488,10 @@ static int __init mv64x60_device_setup(void)
of_node_put(np);
}
+ /* Now add every node that is on the device bus (type is devicectrl */
+ for_each_compatible_node(np, NULL, "marvell,mv64360")
+ of_platform_bus_probe(np, of_mv64x60_devices, NULL);
+
return 0;
}
arch_initcall(mv64x60_device_setup);
^ permalink raw reply related [flat|nested] 3+ messages in thread
* Re: [PATCH v3] sysdev,mv64x60: MV64x60 device bus
2008-04-29 20:26 [PATCH v3] sysdev,mv64x60: MV64x60 device bus Remi Machet
@ 2008-04-29 20:46 ` Dale Farnsworth
2008-04-30 4:35 ` Paul Mackerras
1 sibling, 0 replies; 3+ messages in thread
From: Dale Farnsworth @ 2008-04-29 20:46 UTC (permalink / raw)
To: Remi Machet; +Cc: Stephen Rothwell, Paul Mackerras, linuxppc-dev
On Tue, Apr 29, 2008 at 01:26:38PM -0700, Remi Machet wrote:
> Follow up of my email of 4/16/2008 titled "MV64x60 device bus".
> For each mv64360 entry in the OpenFirmware database, add the
> registration of an of_bus to take care of devices connected to
> the MV64x60 asynchronous devices controller.
>
> Signed-off-by: Remi Machet (rmachet@slac.stanford.edu)
Acked-by: Dale Farnsworth <dale@farnsworth.org>
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [PATCH v3] sysdev,mv64x60: MV64x60 device bus
2008-04-29 20:26 [PATCH v3] sysdev,mv64x60: MV64x60 device bus Remi Machet
2008-04-29 20:46 ` Dale Farnsworth
@ 2008-04-30 4:35 ` Paul Mackerras
1 sibling, 0 replies; 3+ messages in thread
From: Paul Mackerras @ 2008-04-30 4:35 UTC (permalink / raw)
To: Remi Machet; +Cc: linuxppc-dev, Stephen Rothwell
Remi Machet writes:
> Follow up of my email of 4/16/2008 titled "MV64x60 device bus".
> For each mv64360 entry in the OpenFirmware database, add the
> registration of an of_bus to take care of devices connected to
> the MV64x60 asynchronous devices controller.
Your patch description should also explain what good things will come
of doing this, or what bad things will be avoided. Also please put
the "Follow up..." sentence below the 3 dashes so I don't have to edit
it out.
If there are no further review comments, and if you resend with a
better patch description, I'll queue this up for the next merge window
(for 2.6.27).
Paul.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2008-04-30 4:35 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-04-29 20:26 [PATCH v3] sysdev,mv64x60: MV64x60 device bus Remi Machet
2008-04-29 20:46 ` Dale Farnsworth
2008-04-30 4:35 ` Paul Mackerras
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).