devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* Re: RF231 transceiver on at91sam9g20ek board
       [not found]     ` <201206281430.21916.arnd@arndb.de>
@ 2012-06-28 15:08       ` Nicolas Ferre
  2012-06-29 12:53         ` Alexander Smirnov
  0 siblings, 1 reply; 2+ messages in thread
From: Nicolas Ferre @ 2012-06-28 15:08 UTC (permalink / raw)
  To: Arnd Bergmann, Alexander Smirnov, plagnioj
  Cc: devicetree-discuss, linux, linux-arm-kernel

On 06/28/2012 04:30 PM, Arnd Bergmann :
> On Thursday 28 June 2012, Alexander Smirnov wrote:
>>>
>>> It might not be the problem you are faced with but note that at91
>>> is moving towards probing all devices using the device tree, so
>>> starting with linux-3.4 you should be defining the device in the
>>> at91sam9g20ek.dts file for your board and use the generic
>>> board-dt.c file. The platform_data gets replaced with
>>> calls to of_get_gpio() in that case.
>>
>> Thank you for the reply!
>>
>> Are you going to add SPI section to the device tree in the nearest
>> future or I can do it by myself and send you the patch? The reason is
>> that this week I merged at86rf230 driver to the 'net-next' tree, but
>> it won't work without platform data.
> 
> Jean-Christophe or Nicolas might now what the status is for atmel-spi.
> It seems like it would be trivial to just add the compatible string in
> the atmel-spi driver, which would let us probe all of its child devices
> using DT.

Dear Alexander,

There has been an attempt to move the spi-atmel.c driver to device tree.
You can check the status of the discussion in by searching the message
subjects:

[PATCH 1/4 v4] of_spi: add generic binding support to specify cs gpio
[PATCH 1/4 v5] of_spi: add generic binding support to specify cs gpio

I guess that you can take these patches as examples for moving to device
tree on your AT91 based board (beware you should set pin muxing in your
bootloader).

There is a "work in progress" snapshot of this work in at91 git tree/branch:
git://github.com/at91linux/linux-at91.git   ghnew/j/for-3.5-wip

commit: 5f31f2573e7e9369500118e1b8fd026392fc0982
commit: 93fd57e73502656a139879518b397711cc305c6a

Best regards,
-- 
Nicolas Ferre

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: RF231 transceiver on at91sam9g20ek board
  2012-06-28 15:08       ` RF231 transceiver on at91sam9g20ek board Nicolas Ferre
@ 2012-06-29 12:53         ` Alexander Smirnov
  0 siblings, 0 replies; 2+ messages in thread
From: Alexander Smirnov @ 2012-06-29 12:53 UTC (permalink / raw)
  To: Nicolas Ferre
  Cc: devicetree-discuss, plagnioj, linux-arm-kernel, Arnd Bergmann,
	linux

> Dear Alexander,
>
> There has been an attempt to move the spi-atmel.c driver to device tree.
> You can check the status of the discussion in by searching the message
> subjects:
>
> [PATCH 1/4 v4] of_spi: add generic binding support to specify cs gpio
> [PATCH 1/4 v5] of_spi: add generic binding support to specify cs gpio
>
> I guess that you can take these patches as examples for moving to device
> tree on your AT91 based board (beware you should set pin muxing in your
> bootloader).
>
> There is a "work in progress" snapshot of this work in at91 git tree/branch:
> git://github.com/at91linux/linux-at91.git   ghnew/j/for-3.5-wip
>
> commit: 5f31f2573e7e9369500118e1b8fd026392fc0982
> commit: 93fd57e73502656a139879518b397711cc305c6a

Dear at91 team,

thank you very much for the hints!

Alex

>
> Best regards,
> --
> Nicolas Ferre
>
>

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2012-06-29 12:53 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
     [not found] <CAJmB2rDxv45OP4otn7rmQcpzCvLujKm0j9_OqNW6PoyHuarTLw@mail.gmail.com>
     [not found] ` <201206221834.41869.arnd@arndb.de>
     [not found]   ` <CAJmB2rBcRuNe0QfEGoJN1rQnRnr33gyE=nLt3Az=mGEWuR7mCg@mail.gmail.com>
     [not found]     ` <201206281430.21916.arnd@arndb.de>
2012-06-28 15:08       ` RF231 transceiver on at91sam9g20ek board Nicolas Ferre
2012-06-29 12:53         ` Alexander Smirnov

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).