From: Sekhar Nori <nsekhar@ti.com>
To: Ivan Khoronzhuk <ivan.khoronzhuk@ti.com>,
<computersforpeace@gmail.com>, <dwmw2@infradead.org>
Cc: davinci-linux-open-source@linux.davincidsp.com,
linux-mtd@lists.infradead.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v5] ARM: davinci: aemif: get rid of davinci-nand driver dependency on aemif
Date: Wed, 5 Feb 2014 14:47:27 +0530 [thread overview]
Message-ID: <52F201A7.2040401@ti.com> (raw)
In-Reply-To: <1391079820-13018-1-git-send-email-ivan.khoronzhuk@ti.com>
Hi Brian,
On Thursday 30 January 2014 04:33 PM, Ivan Khoronzhuk wrote:
> The problem that the set timings code contains the call of Davinci
> platform function davinci_aemif_setup_timing() which is not
> accessible if kernel is built for another platform like Keystone.
>
> The Keysone platform is going to use TI AEMIF driver.
> If TI AEMIF is used we don't need to set timings and bus width.
> It is done by AEMIF driver.
>
> To get rid of davinci-nand driver dependency on aemif platform code
> we moved aemif code to davinci platform.
>
> The platform AEMIF code (aemif.c) has to be removed once Davinci
> will be converted to DT and use ti-aemif.c driver.
>
> Acked-by: Brian Norris <computersforpeace@gmail.com>
> Signed-off-by: Ivan Khoronzhuk <ivan.khoronzhuk@ti.com>
> [nsekhar@ti.com: fixed checkpatch error and a build breakage due to
> missing include, rebased onto l2-mtd/master]
> Signed-off-by: Sekhar Nori <nsekhar@ti.com>
Hope this patch looks good to you now. I would like to take it for v3.15
via DaVinci tree.
Thanks,
Sekhar
next prev parent reply other threads:[~2014-02-05 9:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-30 11:03 [PATCH v5] ARM: davinci: aemif: get rid of davinci-nand driver dependency on aemif Ivan Khoronzhuk
2014-02-05 9:17 ` Sekhar Nori [this message]
2014-02-10 18:17 ` Brian Norris
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=52F201A7.2040401@ti.com \
--to=nsekhar@ti.com \
--cc=computersforpeace@gmail.com \
--cc=davinci-linux-open-source@linux.davincidsp.com \
--cc=dwmw2@infradead.org \
--cc=ivan.khoronzhuk@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mtd@lists.infradead.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).