[PATCH] powerpc: Create "rom" (MTD) device prpmc2800

Mark A. Greer mgreer at mvista.com
Tue Jun 5 05:40:16 EST 2007


On Fri, Jun 01, 2007 at 11:30:32PM -0500, Milton Miller wrote:
> On Sat Jun 2 09:20:22 EST 2007,  Mark A. Greer wrote:
> 
> >Find the "rom" device for the prpmc2800 and create a device for it.
> >The device will be picked up by the code in 
> >drivers/mtd/maps/physmap_of.c
> >and will setup MTD on that FLASH device.
> ...
> > /*
> >+ * Register a platform device for MTD.
> >+ */
> >+static int __init prpmc2800_register_mtd(void)
> >+{
> >+       struct device_node *np;
> >+
> >+       np = of_find_compatible_node(NULL, "rom", "direct-mapped");
> >+       of_platform_device_create(np, np->name, NULL);
> >+}
> >+arch_initcall(prpmc2800_register_mtd);
> >
> 
> I think "direct-mapped" as compatible is a bit too broad or vague.

It is.  Basically, all I was trying to do was fit with the code that was
already in drivers/mtd/maps/physmap_of.c.  I wasn't expecting to (re)trigger
the debate that it did.  Its a good thing, though.  FLASH/MTD
representation in the DT needs to get sorted out.

> The compatible is supposed to be useable to find and match a driver
> without regard to the name of the node.  Perhaps direct-mapped-rom?
> (as opossed to a direct-mapped-ram, sram, or some width flash bank).
> 
> Actually, looking back at your device tree {1], your list several
> properties for flash, including bank-width and partition names.
> Perhaps first compatible should be direct-mapped-partitioned-flash,
> direct-mapped-partitioned-rom, direct-mapped-rom  (to me a
> direct-mapped-rom driver would expose one section of address space
> read-only). I'm assuming that your driver for this "direct-mapped"
> device will look at these properties from the of device node and
> call the mtd layer somewhat directly with their contents.

The "driver" is already there, drivers/mtd/maps/physmap_of.c.  I
conjured up the DT node so it would work with that existing driver.

> PS: I know you've posted this a few times.  I'm just behind in
> my reading and  replying :-).

No problem.  I just missed an entire thread the was directed at me :-P

Mark



More information about the Linuxppc-dev mailing list