[U-Boot] [PATCH v7] dm: at91: Add driver model support for the spi driver

["Andreas Bießmann" <andreas@biessmann.org>]

Hi Jagan,

On 2016-08-19 14:10, Jagan Teki wrote:
> Hi Andreas,
> 
> On 19 August 2016 at 17:20, Andreas Bie?mann <andreas@biessmann.de> 
> wrote:
>> Hi Jagan,
>> 
>> On 2016-08-19 13:35, Jagan Teki wrote:
>>> 
>>> On 8 August 2016 at 06:14,  <Wenyou.Yang@microchip.com> wrote:
>>>> 
>>>> Hi Jagan,
>>>> 
>>>>> -----Original Message-----
>>>>> From: Jagan Teki [mailto:jagannadh.teki at gmail.com]
>>>>> Sent: 2016?8?6? 21:00
>>>>> To: Wenyou Yang <wenyou.yang@atmel.com>
>>>>> Cc: U-Boot Mailing List <u-boot@lists.denx.de>
>>>>> Subject: Re: [U-Boot] [PATCH v7] dm: at91: Add driver model support 
>>>>> for
>>>>> the spi
>>>>> driver
>>>>> 
>>>>> On 31 July 2016 at 17:05, Jagan Teki <jagannadh.teki@gmail.com> 
>>>>> wrote:
>>>>> > On 29 July 2016 at 06:08, Wenyou Yang <wenyou.yang@atmel.com> wrote:
>>>>> >> Add driver model support while retaining the existing legacy code.
>>>>> >> This allows the driver to support boards that have converted to
>>>>> >> driver model as well as those that have not.
>>>>> 
>>>>> Need some info - how many boards still pending to use this driver 
>>>>> to use
>>>>> it in dm?
>>>> 
>>>> 
>>>> For now, only sama5d2_xplained has used this drive in dm, other 
>>>> boards
>>>> with AT91 SoC has not used dm driver,
>>>> such as at91sam9g20ek, at91sam9x5ek, at91sam9m10g45ek, sama5d3xek.
>>>> sama5d4ek, ....
>>> 
>>> 
>>> Please convert these boards to dm as well, because driver still have
>>> non-dm code never know when it gets removed.
>> 
>> 
>> non-dm code has to live for some time since this is a shared driver 
>> for
>> avr32 and arm architecture of atmel SoC. Unfortunately avr32 still 
>> lacks dm
>> support in u-boot. I have some prepared patches but AFAIR there was a
>> problem with early malloc ... after that I had no time to get it done.
>> 
>> Beside that I also insist on converting the remaining at91 boards to 
>> dm.
>> Since there are some boards I would suggest a time frame until end of 
>> this
>> year.
> 
> OK, look like avr32 should be a blocker here since at91 boards can do
> at-least. What is the plan on avr32, shall I look in to it?

I hope I can look for it in next couple of month. So v2016.11 should be 
doable, maybe v2017.01. Do you have some avr32 hardware to verify it?

Andreas

> 
> thanks!