From: santosh.shilimkar@ti•com (Santosh Shilimkar)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH v4 0/2] Introduce AEMIF driver for Davinci/Keystone archs
Date: Tue, 18 Feb 2014 09:41:23 -0500 [thread overview]
Message-ID: <53037113.3090105@ti.com> (raw)
In-Reply-To: <1391629574-18955-1-git-send-email-ivan.khoronzhuk@ti.com>
Greg,
On Wednesday 05 February 2014 02:46 PM, Ivan Khoronzhuk wrote:
> 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
>
Can you please have a look at the series ? It has been on the list for
sometime and all the outstanding comments are addressed so far. If
you are ok with it, I would like to get these queued up for 3.15
via your tree.
> Based on
> git://git.kernel.org/pub/scm/linux/kernel/git/ssantosh/linux-keystone.git
> keystone/master
>
> 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 | 429 +++++++++++++++++++++
> 4 files changed, 651 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/memory-controllers/ti-aemif.txt
> create mode 100644 drivers/memory/ti-aemif.c
>
next prev parent reply other threads:[~2014-02-18 14:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-05 19:46 [PATCH v4 0/2] Introduce AEMIF driver for Davinci/Keystone archs Ivan Khoronzhuk
2014-02-05 19:46 ` [PATCH v4 1/2] memory: ti-aemif: introduce AEMIF driver Ivan Khoronzhuk
2014-02-18 20:30 ` Greg KH
2014-02-19 10:32 ` Ivan Khoronzhuk
2014-02-19 14:34 ` Greg KH
2014-02-19 17:04 ` Ivan Khoronzhuk
2014-02-05 19:46 ` [PATCH v4 2/2] memory: ti-aemif: add bindings for " Ivan Khoronzhuk
2014-02-10 16:14 ` Santosh Shilimkar
2014-02-18 14:41 ` Santosh Shilimkar [this message]
2014-02-18 20:27 ` [PATCH v4 0/2] Introduce AEMIF driver for Davinci/Keystone archs Greg KH
2014-02-18 20:34 ` Santosh Shilimkar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53037113.3090105@ti.com \
--to=santosh.shilimkar@ti$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox