From: arnd@arndb•de (Arnd Bergmann)
To: linux-arm-kernel@lists•infradead.org
Subject: RF231 transceiver on at91sam9g20ek board
Date: Fri, 22 Jun 2012 18:34:41 +0000 [thread overview]
Message-ID: <201206221834.41869.arnd@arndb.de> (raw)
In-Reply-To: <CAJmB2rDxv45OP4otn7rmQcpzCvLujKm0j9_OqNW6PoyHuarTLw@mail.gmail.com>
On Wednesday 20 June 2012, Alexander Smirnov wrote:
> I'm the developer of the IEEE 802.15.4 kernel branch, and currently
> I've faced with the problem regarding mach-at91 arch and hope you can
> advise me.
>
> I've been working with at86rf231 transceiver (RF231 extender)
> connected via SPI to at91sam9g20ek board. The driver works and tested
> for kernels up to 3.1 version (versions 3.2-latest haven't ever been
> tested yet).
> Several days ago I've ported the IEEE802.15.4 stack to the latest
> kernel and see some strange things: RF231 interrupt handler is
> permanently pulled right after driver's probe method (the RF231 chip
> is in disabled mode, so it can't generate interrupts at that moment).
> Also I've noticed that each ENTER key pressing in minicom generates a
> new interrupt. It looks like somebody else uses the same pin/pins for
> its needs...
>
> Do you have any ideas what can be changed since 3.1 kernel that this
> problem arose.
>
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.
Arnd
next prev parent reply other threads:[~2012-06-22 18:34 UTC|newest]
Thread overview: 6+ 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 [this message]
2012-06-28 7:47 ` Alexander Smirnov
2012-06-28 14:30 ` Arnd Bergmann
2012-06-28 15:08 ` Nicolas Ferre
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=201206221834.41869.arnd@arndb.de \
--to=arnd@arndb$(echo .)de \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox