These patches introduce Async External Memory Interface (EMIF16/AEMIF) controller driver for Davinci/Keystone archs. For more informations see documentation: Davinci DM646x - http://www.ti.com/lit/ug/sprueq7c/sprueq7c.pdf OMAP-L138 - http://www.ti.com/lit/ug/spruh77a/spruh77a.pdf Kestone - http://www.ti.com/lit/ug/sprugz3a/sprugz3a.pdf Based on v3.14-rc3. v4..v5: - memory: ti-aemif: introduce AEMIF driver deleted DRV_NAME in favour of KBUILD_MODNAME deleted redundant err message in case of memory allocation some cosmetic changes v3..v4: rebased on latest of linux-keystone.git keystone/master v2..v3 (https://lkml.org/lkml/2013/12/11/148): - memory: ti-aemif: introduce AEMIF driver changed to work with multiple AEMIF controllers corrected "copyright" to "authors" in header changed compatible "ti,omap-L138-aemif" to "ti,da850-aeimf" used NULL in clk_get() instead of "aemif" name driver can be build as loadable module treat all child nodes as cs nodes, it makes code simpler - memory: ti-aemif: add bindings for AEMIF driver deleted direct link driver/memory/ti-aemif.c clarified description of controller ranges property changed compatible "ti,omap-L138-aemif" to "ti,da850-aeimf" added cs number information in commit log removed compatible property from cs node, it makes code simpler v1..v2 (https://lkml.org/lkml/2013/11/21/170): - memory: ti-aemif: introduce AEMIF driver - memory: ti-aemif: add bindings for AEMIF driver added ti.cs-chipselect property instead of representing chipselect number in cs node name. Ivan Khoronzhuk (2): memory: ti-aemif: introduce AEMIF driver memory: ti-aemif: add bindings for AEMIF driver .../bindings/memory-controllers/ti-aemif.txt | 210 ++++++++++ drivers/memory/Kconfig | 11 + drivers/memory/Makefile | 1 + drivers/memory/ti-aemif.c | 427 +++++++++++++++++++++ 4 files changed, 649 insertions(+) create mode 100644 Documentation/devicetree/bindings/memory-controllers/ti-aemif.txt create mode 100644 drivers/memory/ti-aemif.c -- 1.8.3.2 -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
