Hi Arnd, On Thu, Dec 08, 2011 at 21:18:08, Arnd Bergmann wrote: > On Thursday 08 December 2011, Nori, Sekhar wrote: > > DaVinci AEMIF is an async memory interface peripheral implemented > > in arch/arm/mach-davinci/aemif.c. It helps interface to NAND, NOR > > and other asynchronous memories. Currently it just provides an API > > for timing value configuration. The API is invoked by the MTD NAND > > driver. > > > > Specification here: http://www.ti.com/lit/ug/sprue20c/sprue20c.pdf > > > > We are looking at a place for this outside of architecture code. > > I think the best place depends on how you plan to use the sram > interface. If all memory behind the aemif is handled by mtd, I would > put the entire driver somewhere in the mtd infrastructure.
All the boards and use cases I have come across for AEMIF so far (5-6 years) have either used NAND or NOR memory. > If you want it to provide endpoint devices that are handled by > distinct subsystems in Linux, I would make it an mfd multifunction > device and make the common code a driver that scans the connected > memories in order to register its child devices for each of the > subsystems. Okay. Thanks for the explanation. Since the users of AEMIF at this point are mtd devices, I propose moving it to drivers/mtd/davinci-aemif.c (of course, mtd folks need to approve). Thanks, Sekhar _______________________________________________ devicetree-discuss mailing list devicetree-discuss@lists.ozlabs.org https://lists.ozlabs.org/listinfo/devicetree-discuss