From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <5298B440.1020905@ti.com> Date: Fri, 29 Nov 2013 17:35:28 +0200 From: Grygorii Strashko MIME-Version: 1.0 To: Santosh Shilimkar , Ivan Khoronzhuk Subject: Re: [PATCH 1/2] memory: ti-aemif: introduce AEMIF driver References: <1384962416-14862-1-git-send-email-ivan.khoronzhuk@ti.com> <1384962416-14862-2-git-send-email-ivan.khoronzhuk@ti.com> <5298B370.3090405@ti.com> In-Reply-To: <5298B370.3090405@ti.com> Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit Cc: Mark Rutland , devicetree@vger.kernel.org, Russell King , Pawel Moll , Stephen Warren , gregkh@linuxfoundation.org, Ian Campbell , Kumar Gala , Rob Herring , linux-kernel@vger.kernel.org, linux-mtd@lists.infradead.org, Rob Landley , linux-arm-kernel@lists.infradead.org List-Id: Linux MTD discussion mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On 11/29/2013 05:32 PM, Santosh Shilimkar wrote: > On Wednesday 20 November 2013 10:46 AM, Ivan Khoronzhuk wrote: >> Add new AEMIF driver for EMIF16 Texas Instruments controller. >> The EMIF16 module 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 at any given time via four chip selects with 64M byte access [...] >> + return 0; >> +} >> + >> +static const struct of_device_id aemif_of_match[] = { >> + { .compatible = "ti,davinci-aemif", }, >> + { .compatible = "ti,keystone-aemif", }, >> + { .compatible = "ti,omap-L138-aemif", }, >> + {}, >> +}; >> + > Looks like you are yet to update the patches from > previous comments. Did I miss v2 or you haven't posted > that yet ? No. This is v2, actually :( (the mess was already noticed) it was posted after v1 (https://lkml.org/lkml/2013/11/11/352), but people continue commenting v1, for some reasons. Next version will be posted when bindings will be clarified finally. Regards, -grygorii From mboxrd@z Thu Jan 1 00:00:00 1970 From: grygorii.strashko@ti.com (Grygorii Strashko) Date: Fri, 29 Nov 2013 17:35:28 +0200 Subject: [PATCH 1/2] memory: ti-aemif: introduce AEMIF driver In-Reply-To: <5298B370.3090405@ti.com> References: <1384962416-14862-1-git-send-email-ivan.khoronzhuk@ti.com> <1384962416-14862-2-git-send-email-ivan.khoronzhuk@ti.com> <5298B370.3090405@ti.com> Message-ID: <5298B440.1020905@ti.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On 11/29/2013 05:32 PM, Santosh Shilimkar wrote: > On Wednesday 20 November 2013 10:46 AM, Ivan Khoronzhuk wrote: >> Add new AEMIF driver for EMIF16 Texas Instruments controller. >> The EMIF16 module 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 at any given time via four chip selects with 64M byte access [...] >> + return 0; >> +} >> + >> +static const struct of_device_id aemif_of_match[] = { >> + { .compatible = "ti,davinci-aemif", }, >> + { .compatible = "ti,keystone-aemif", }, >> + { .compatible = "ti,omap-L138-aemif", }, >> + {}, >> +}; >> + > Looks like you are yet to update the patches from > previous comments. Did I miss v2 or you haven't posted > that yet ? No. This is v2, actually :( (the mess was already noticed) it was posted after v1 (https://lkml.org/lkml/2013/11/11/352), but people continue commenting v1, for some reasons. Next version will be posted when bindings will be clarified finally. Regards, -grygorii From mboxrd@z Thu Jan 1 00:00:00 1970 From: Grygorii Strashko Subject: Re: [PATCH 1/2] memory: ti-aemif: introduce AEMIF driver Date: Fri, 29 Nov 2013 17:35:28 +0200 Message-ID: <5298B440.1020905@ti.com> References: <1384962416-14862-1-git-send-email-ivan.khoronzhuk@ti.com> <1384962416-14862-2-git-send-email-ivan.khoronzhuk@ti.com> <5298B370.3090405@ti.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <5298B370.3090405@ti.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "linux-mtd" Errors-To: linux-mtd-bounces+gldm-linux-mtd-36=gmane.org@lists.infradead.org To: Santosh Shilimkar , Ivan Khoronzhuk Cc: Mark Rutland , devicetree@vger.kernel.org, Russell King , Pawel Moll , Stephen Warren , gregkh@linuxfoundation.org, Ian Campbell , Kumar Gala , Rob Herring , linux-kernel@vger.kernel.org, linux-mtd@lists.infradead.org, Rob Landley , linux-arm-kernel@lists.infradead.org List-Id: devicetree@vger.kernel.org On 11/29/2013 05:32 PM, Santosh Shilimkar wrote: > On Wednesday 20 November 2013 10:46 AM, Ivan Khoronzhuk wrote: >> Add new AEMIF driver for EMIF16 Texas Instruments controller. >> The EMIF16 module 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 at any given time via four chip selects with 64M byte access [...] >> + return 0; >> +} >> + >> +static const struct of_device_id aemif_of_match[] = { >> + { .compatible = "ti,davinci-aemif", }, >> + { .compatible = "ti,keystone-aemif", }, >> + { .compatible = "ti,omap-L138-aemif", }, >> + {}, >> +}; >> + > Looks like you are yet to update the patches from > previous comments. Did I miss v2 or you haven't posted > that yet ? No. This is v2, actually :( (the mess was already noticed) it was posted after v1 (https://lkml.org/lkml/2013/11/11/352), but people continue commenting v1, for some reasons. Next version will be posted when bindings will be clarified finally. Regards, -grygorii ______________________________________________________ Linux MTD discussion mailing list http://lists.infradead.org/mailman/listinfo/linux-mtd/ From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757152Ab3K2Plx (ORCPT ); Fri, 29 Nov 2013 10:41:53 -0500 Received: from bear.ext.ti.com ([192.94.94.41]:41527 "EHLO bear.ext.ti.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752545Ab3K2Plw (ORCPT ); Fri, 29 Nov 2013 10:41:52 -0500 Message-ID: <5298B440.1020905@ti.com> Date: Fri, 29 Nov 2013 17:35:28 +0200 From: Grygorii Strashko User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0 MIME-Version: 1.0 To: Santosh Shilimkar , Ivan Khoronzhuk CC: Rob Landley , Russell King , , Pawel Moll , Mark Rutland , Rob Herring , Stephen Warren , Kumar Gala , Ian Campbell , , , , Subject: Re: [PATCH 1/2] memory: ti-aemif: introduce AEMIF driver References: <1384962416-14862-1-git-send-email-ivan.khoronzhuk@ti.com> <1384962416-14862-2-git-send-email-ivan.khoronzhuk@ti.com> <5298B370.3090405@ti.com> In-Reply-To: <5298B370.3090405@ti.com> Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit X-Originating-IP: [10.167.145.75] X-EXCLAIMER-MD-CONFIG: f9c360f5-3d1e-4c3c-8703-f45bf52eff6b Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 11/29/2013 05:32 PM, Santosh Shilimkar wrote: > On Wednesday 20 November 2013 10:46 AM, Ivan Khoronzhuk wrote: >> Add new AEMIF driver for EMIF16 Texas Instruments controller. >> The EMIF16 module 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 at any given time via four chip selects with 64M byte access [...] >> + return 0; >> +} >> + >> +static const struct of_device_id aemif_of_match[] = { >> + { .compatible = "ti,davinci-aemif", }, >> + { .compatible = "ti,keystone-aemif", }, >> + { .compatible = "ti,omap-L138-aemif", }, >> + {}, >> +}; >> + > Looks like you are yet to update the patches from > previous comments. Did I miss v2 or you haven't posted > that yet ? No. This is v2, actually :( (the mess was already noticed) it was posted after v1 (https://lkml.org/lkml/2013/11/11/352), but people continue commenting v1, for some reasons. Next version will be posted when bindings will be clarified finally. Regards, -grygorii