devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Santosh Shilimkar <santosh.shilimkar@ti.com>
To: Ivan Khoronzhuk <ivan.khoronzhuk@ti.com>
Cc: gregkh@linuxfoundation.org, galak@kernel.crashing.org,
	rob@landley.net, linux@arm.linux.org.uk,
	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 v5 2/2] memory: ti-aemif: add bindings for AEMIF driver
Date: Wed, 19 Feb 2014 09:13:19 -0500	[thread overview]
Message-ID: <5304BBFF.3070502@ti.com> (raw)
In-Reply-To: <1392817210-14312-3-git-send-email-ivan.khoronzhuk@ti.com>

On Wednesday 19 February 2014 08:40 AM, Ivan Khoronzhuk wrote:
> Add bindings for TI Async External Memory Interface (AEMIF) controller.
> 
> The Async External Memory Interface (EMIF16/AEMIF) controller is intended to
> provide a glue-less interface to a variety of asynchronous memory devices like
> ASRA M, NOR and NAND memory. A total of 256M bytes of any of these memories
> can be accessed via 4 chip selects with 64M byte access per chip select.
> 
> We are not encoding CS number in reg property, it's memory partition number.
> The CS number is encoded for Davinci NAND node using standalone property
> "ti,davinci-chipselect" and we need to provide two memory ranges to it,
> as result we can't encode CS number in "reg" for AEMIF child devices
> (NAND/NOR/etc), as it will break bindings compatibility.
> 
> In this patch, NAND node is used just as an example of child node.
> 
> Signed-off-by: Ivan Khoronzhuk <ivan.khoronzhuk@ti.com>
> ---

Acked-by: Santosh Shilimkar <santosh.shilimkar@ti.com>

  reply	other threads:[~2014-02-19 14:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-19 13:40 [PATCH v5 0/2] Introduce AEMIF driver for Davinci/Keystone archs Ivan Khoronzhuk
2014-02-19 13:40 ` [PATCH v5 1/2] memory: ti-aemif: introduce AEMIF driver Ivan Khoronzhuk
2014-02-19 13:40 ` [PATCH v5 2/2] memory: ti-aemif: add bindings for " Ivan Khoronzhuk
2014-02-19 14:13   ` Santosh Shilimkar [this message]
     [not found]   ` <1392817210-14312-3-git-send-email-ivan.khoronzhuk-l0cyMroinI0@public.gmane.org>
2014-02-19 18:11     ` Mark Rutland
     [not found]       ` <20140219181152.GG25079-NuALmloUBlrZROr8t4l/smS4ubULX0JqMm0uRHvK7Nw@public.gmane.org>
2014-02-20 12:44         ` Ivan Khoronzhuk
     [not found]           ` <5305F898.6020401-l0cyMroinI0@public.gmane.org>
2014-02-20 13:44             ` Rob Herring
2014-02-20 15:49               ` Ivan Khoronzhuk

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=5304BBFF.3070502@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).