[PATCH v7 1/5] drivers: memory: Introduce Marvell EBU Device Bus driver

Jason Cooper jason at lakedaemon.net
Thu Apr 11 13:27:46 EDT 2013


On Wed, Apr 10, 2013 at 04:04:00PM -0300, Ezequiel Garcia wrote:
> Marvell EBU SoCs such as Armada 370/XP, Orion5x (88f5xxx) and
> Discovery (mv78xx0) supports a Device Bus controller to access several
> kinds of memories and I/O devices (NOR, NAND, SRAM, FPGA).
> 
> This commit adds a driver to handle this controller. So far only
> Armada 370, Armada XP and Discovery SoCs are supported.
> 
> The driver must be registered through a device tree node;
> as explained in the binding document.
> 
> For each child node in the device tree, this driver will:
>   * set timing parameters
>   * register a child device
>   * setup an address decoding window, using the mbus driver
> 
> Keep in mind the address decoding window setup is only a temporary hack.
> This code will be removed from this devbus driver as soon as a proper device
> tree binding for the mbus driver is added.
> 
> Signed-off-by: Ezequiel Garcia <ezequiel.garcia at free-electrons.com>
> Acked-by: Arnd Bergmann <arnd at arndb.de>
> ---
>  .../bindings/memory-controllers/mvebu-devbus.txt   | 156 ++++++++++
>  drivers/memory/Kconfig                             |  10 +
>  drivers/memory/Makefile                            |   1 +
>  drivers/memory/mvebu-devbus.c                      | 340 +++++++++++++++++++++
>  4 files changed, 507 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/memory-controllers/mvebu-devbus.txt
>  create mode 100644 drivers/memory/mvebu-devbus.c

Applied to mvebu/drivers with gregkh's ack.

thx,

Jason.



More information about the linux-arm-kernel mailing list