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 -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
