[PATCH 04/10] bus: introduce an Marvell EBU MBus driver

[thomas.petazzoni@free-electrons.com (Thomas Petazzoni)]

Dear Jason Gunthorpe,

On Fri, 8 Mar 2013 10:29:50 -0700, Jason Gunthorpe wrote:

> > Sorry, but we _do_ want the kernel to be able to set those timings
> > parameters, and therefore, a Device Bus driver will be needed,
> > regardless of whether it creates the address window or not.
> 
> See the very good idea from Maxime Bizon about autoprobing the ONFI
> timings directly from the NAND chip.

ONFI (Open NAND Firmware Interface) is about NAND, while the Device Bus
driver submitted by Ezequiel is about NOR. I don't think NORs have a
standard way of exposing their memory timings requirements. And the
Device Bus driver is not only for NORs, but also for example for FPGAs
connected on the memory bus.

Ezequiel followed the work done by Jon Hunter on the GPMC driver for
the memory bus of OMAP SoCs, which includes the definition of timings
in the Device Tree. To me, it seems like defining the timings in the
Device Tree do make sense, and "ONFI" is not a good enough answer to
get rid of the Device Bus driver submitted by Ezequiel.

Best regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com