[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <50993511.3020906@ti.com>
Date: Tue, 6 Nov 2012 11:04:33 -0500
From: Murali Karicheri <m-karicheri2@...com>
To: Sekhar Nori <nsekhar@...com>
CC: Rob Herring <robherring2@...il.com>, <dwmw2@...radead.org>,
<artem.bityutskiy@...ux.intel.com>, <b32955@...escale.com>,
<shubhrajyoti@...com>, <wim@...ana.be>, <hs@...x.de>,
<linux-mtd@...ts.infradead.org>, <linux-kernel@...r.kernel.org>,
<grant.likely@...retlab.ca>, <rob@...dley.net>,
<gregkh@...uxfoundation.org>, <swarren@...dotorg.org>,
<hdoyu@...dia.com>, <santosh.shilimkar@...com>,
<devicetree-discuss@...ts.ozlabs.org>, <linux-doc@...r.kernel.org>,
<davinci-linux-open-source@...ux.davincidsp.com>
Subject: Re: [RFC PATCH 1/2] memory: davinci - add aemif controller platform
driver
On 11/06/2012 02:44 AM, Sekhar Nori wrote:
> On 11/6/2012 2:38 AM, Murali Karicheri wrote:
>> On 11/04/2012 08:52 AM, Rob Herring wrote:
>>> OMAP GPMC
>> Could you send me a link please?
> https://www.google.com/search?q=RFC+OMAP+GPMC+DT+bindings
>
> The patches series is sent by Daniel Mack. v3 was the last version sent.
>
> Thanks,
> Sekhar
>
>
One of the question I have on this is what is the final location of the
GPMC driver? The patch referred here is located inside the mach-omap2.
This will not work for us as AEMIF driver is used across multiple
architecture. range is also used in AEMIF bindings to refer the CS
memory map. So there is no issue here. I will fix the documentation. Or
Am I missing something?
Murali
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists