Code generation involving __raw_readl and __raw_writel

[Måns Rullgård]

Mason <mpeg.blue at free.fr> writes:

> On 27/11/2014 17:51, Arnd Bergmann wrote:
>
>> On Thursday 27 November 2014 16:18:20 Måns Rullgård wrote:
>>
>>> That's great.  You mentioned working against 3.14.  Do you have any
>>> plans to move onto the current version?  That would be a prerequisite
>>> for upstream acceptance.
>> 
>> FWIW, it's also a good strategy to do the initial bringup on the latest
>> kernel and then backport to the older one for product work, otherwise
>> you end up doing the forward port twice, and it's almost always harder
>> than a backport.
>
> Hmmm, I was told to target 3.14, because that's what we plan to support.
>
> Maybe I can push one driver at a time?

Normally you would start with minimal chip support, just enough to
configure memory and a uart, then add drivers for various devices one by
one.

New ARM systems are expected to use DT, so you should also be switching
to that if you haven't already.

-- 
Måns Rullgård
mans at mansr.com