From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753441Ab3KZA4l (ORCPT ); Mon, 25 Nov 2013 19:56:41 -0500 Received: from comal.ext.ti.com ([198.47.26.152]:58285 "EHLO comal.ext.ti.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751691Ab3KZA4i (ORCPT ); Mon, 25 Nov 2013 19:56:38 -0500 Message-ID: <5293F19D.70901@ti.com> Date: Mon, 25 Nov 2013 19:55:57 -0500 From: Santosh Shilimkar User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: Sekhar Nori CC: "Khoronzhuk, Ivan" , Rob Landley , Russell King , Mark Rutland , "devicetree@vger.kernel.org" , "Strashko, Grygorii" , Pawel Moll , Stephen Warren , Ian Campbell , Kumar Gala , Rob Herring , "linux-kernel@vger.kernel.org" , "linux-mtd@lists.infradead.org" , "linux-arm-kernel@lists.infradead.org" Subject: Re: [PATCH 10/12] mtd: nand: davinci: don't set timings if AEMIF is used References: <1384187188-5776-1-git-send-email-ivan.khoronzhuk@ti.com>, <1384187188-5776-11-git-send-email-ivan.khoronzhuk@ti.com> <4F5844B3A985794BA902E12C070812375F8D53@DNCE04.ent.ti.com> <528307F0.6000805@ti.com> <52838941.4060207@ti.com> <5284ABB9.70608@ti.com> <5284DFE7.70308@ti.com> <528E3DD4.7030607@ti.com> <528F968F.40306@ti.com> <5291CB01.1010506@ti.com> In-Reply-To: <5291CB01.1010506@ti.com> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sunday 24 November 2013 04:46 AM, Sekhar Nori wrote: > On Friday 22 November 2013 11:08 PM, Santosh Shilimkar wrote: >> On Thursday 21 November 2013 12:07 PM, Nori, Sekhar wrote: >>> On 11/14/2013 8:06 PM, Santosh Shilimkar wrote: [..] >>> Yes, that would be the ideal way. But the reality is that there is close >>> to zero chance of all the DaVinci platforms using AEMIF ever getting >>> converted to DT. This means that we will never be able to get rid of >>> this piece of code. >>> >> Well that means some of those platforms support will get deprecated >> soon considering other basic frameworks like irq, timer wheel etc >> is assuming the DT direction. But its your call because if you >> want those platforms to live, you need to convert them to DT. >> >>> I do agree platform data is not the direction you want to take on ARM >>> but at the same time its not really a deprecated mechanism as far as the >>> broader kernel is concerned. >>> >>> So, can we consider adding platform data mechanism to the AEMIF driver? >>> >> Sorry but answer is "NO". If the above hack is really bothering you, >> we can actually rip out the above code in question and move it >> to mach-davinci. Infact thats the best direction to make the >> mtd nandn driver independent of any platform quirks(dt, pdata etc) >> >> Ivan already has a patch to do that and he is going to post >> that patch. With that patch, we won't need $subject patch. >> > > Okay I will wait for the patch. > Ivan has posted a patch already and you are copied on it. Regards, Santosh