From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: RF231 transceiver on at91sam9g20ek board
Date: Thu, 28 Jun 2012 14:30:21 +0000 [thread overview]
Message-ID: <201206281430.21916.arnd@arndb.de> (raw)
In-Reply-To: <CAJmB2rBcRuNe0QfEGoJN1rQnRnr33gyE=nLt3Az=mGEWuR7mCg@mail.gmail.com>
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.
Arnd
next prev parent reply other threads:[~2012-06-28 14:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-20 11:52 RF231 transceiver on at91sam9g20ek board Alexander Smirnov
2012-06-22 18:34 ` Arnd Bergmann
2012-06-28 7:47 ` Alexander Smirnov
2012-06-28 14:30 ` Arnd Bergmann [this message]
2012-06-28 15:08 ` Nicolas Ferre
2012-06-28 15:08 ` Nicolas Ferre
2012-06-29 12:53 ` Alexander Smirnov
2012-06-29 12:53 ` Alexander Smirnov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201206281430.21916.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.