All of lore.kernel.org
 help / color / mirror / Atom feed
From: Santosh Shilimkar <santosh.shilimkar@ti.com>
To: <gregkh@linuxfoundation.org>
Cc: mark.rutland@arm.com, devicetree@vger.kernel.org,
	grygorii.strashko@ti.com, linux@arm.linux.org.uk,
	pawel.moll@arm.com, swarren@wwwdotorg.org,
	ijc+devicetree@hellion.org.uk, nsekhar@ti.com,
	galak@kernel.crashing.org, rob.herring@calxeda.com,
	linux-kernel@vger.kernel.org, linux-mtd@lists.infradead.org,
	rob@landley.net, Ivan Khoronzhuk <ivan.khoronzhuk@ti.com>,
	dwmw2@infradead.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [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
> 

WARNING: multiple messages have this Message-ID (diff)
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
> 

WARNING: multiple messages have this Message-ID (diff)
From: Santosh Shilimkar <santosh.shilimkar-l0cyMroinI0@public.gmane.org>
To: gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org
Cc: Ivan Khoronzhuk <ivan.khoronzhuk-l0cyMroinI0@public.gmane.org>,
	rob-VoJi6FS/r0vR7s880joybQ@public.gmane.org,
	linux-lFZ/pmaqli7XmaaqVzeoHQ@public.gmane.org,
	galak-XVmvHMARGAS8U2dJNN8I7kB+6BGkLq7r@public.gmane.org,
	devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	pawel.moll-5wv7dgnIgG8@public.gmane.org,
	mark.rutland-5wv7dgnIgG8@public.gmane.org,
	rob.herring-bsGFqQB8/DxBDgjK7y7TUQ@public.gmane.org,
	swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org,
	ijc+devicetree-KcIKpvwj1kUDXYZnReoRVg@public.gmane.org,
	linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
	linux-mtd-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
	grygorii.strashko-l0cyMroinI0@public.gmane.org,
	dwmw2-wEGCiKHe2LqWVfeAwA7xHQ@public.gmane.org,
	nsekhar-l0cyMroinI0@public.gmane.org
Subject: Re: [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-l0cyMroinI0@public.gmane.org>

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
> 

--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

WARNING: multiple messages have this Message-ID (diff)
From: Santosh Shilimkar <santosh.shilimkar@ti.com>
To: <gregkh@linuxfoundation.org>
Cc: Ivan Khoronzhuk <ivan.khoronzhuk@ti.com>, <rob@landley.net>,
	<linux@arm.linux.org.uk>, <galak@kernel.crashing.org>,
	<devicetree@vger.kernel.org>, <pawel.moll@arm.com>,
	<mark.rutland@arm.com>, <rob.herring@calxeda.com>,
	<swarren@wwwdotorg.org>, <ijc+devicetree@hellion.org.uk>,
	<linux-kernel@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-mtd@lists.infradead.org>, <grygorii.strashko@ti.com>,
	<dwmw2@infradead.org>, <nsekhar@ti.com>
Subject: Re: [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
> 


  parent reply	other threads:[~2014-02-18 14:41 UTC|newest]

Thread overview: 43+ 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 ` Ivan Khoronzhuk
2014-02-05 19:46 ` Ivan Khoronzhuk
2014-02-05 19:46 ` Ivan Khoronzhuk
2014-02-05 19:46 ` [PATCH v4 1/2] memory: ti-aemif: introduce AEMIF driver Ivan Khoronzhuk
2014-02-05 19:46   ` Ivan Khoronzhuk
2014-02-05 19:46   ` Ivan Khoronzhuk
2014-02-05 19:46   ` Ivan Khoronzhuk
2014-02-18 20:30   ` Greg KH
2014-02-18 20:30     ` Greg KH
2014-02-18 20:30     ` Greg KH
2014-02-19 10:32     ` Ivan Khoronzhuk
2014-02-19 10:32       ` Ivan Khoronzhuk
2014-02-19 10:32       ` Ivan Khoronzhuk
2014-02-19 10:32       ` Ivan Khoronzhuk
2014-02-19 14:34       ` Greg KH
2014-02-19 14:34         ` Greg KH
2014-02-19 14:34         ` Greg KH
2014-02-19 14:34         ` Greg KH
2014-02-19 17:04         ` Ivan Khoronzhuk
2014-02-19 17:04           ` Ivan Khoronzhuk
2014-02-19 17:04           ` Ivan Khoronzhuk
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-05 19:46   ` Ivan Khoronzhuk
2014-02-05 19:46   ` Ivan Khoronzhuk
2014-02-05 19:46   ` Ivan Khoronzhuk
2014-02-10 16:14   ` Santosh Shilimkar
2014-02-10 16:14     ` Santosh Shilimkar
2014-02-10 16:14     ` Santosh Shilimkar
2014-02-10 16:14     ` Santosh Shilimkar
2014-02-18 14:41 ` Santosh Shilimkar [this message]
2014-02-18 14:41   ` [PATCH v4 0/2] Introduce AEMIF driver for Davinci/Keystone archs Santosh Shilimkar
2014-02-18 14:41   ` Santosh Shilimkar
2014-02-18 14:41   ` Santosh Shilimkar
2014-02-18 20:27   ` Greg KH
2014-02-18 20:27     ` Greg KH
2014-02-18 20:27     ` Greg KH
2014-02-18 20:27     ` Greg KH
2014-02-18 20:34     ` Santosh Shilimkar
2014-02-18 20:34       ` Santosh Shilimkar
2014-02-18 20:34       ` Santosh Shilimkar
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.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dwmw2@infradead.org \
    --cc=galak@kernel.crashing.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=grygorii.strashko@ti.com \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=ivan.khoronzhuk@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=linux@arm.linux.org.uk \
    --cc=mark.rutland@arm.com \
    --cc=nsekhar@ti.com \
    --cc=pawel.moll@arm.com \
    --cc=rob.herring@calxeda.com \
    --cc=rob@landley.net \
    --cc=swarren@wwwdotorg.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.