From: Bill Gatliff <bgat@billgatliff•com>
To: linuxppc-dev@ozlabs•org
Subject: Re: Sleep-capable GPIO slave-selects on MPC52xx?
Date: Tue, 12 Jan 2010 10:50:12 -0600 [thread overview]
Message-ID: <4B4CA844.8040301@billgatliff.com> (raw)
In-Reply-To: <4B4B866B.10207@billgatliff.com>
Bill Gatliff wrote:
>
> It looks like the current version of the MPC52xx SPI driver won't work
> with sleep-capable GPIOs for slave-selects. In particular, it looks
> like mpc52xx_spi_fsmstate_transfer() is an interrupt handler that calls
> mpc52xx_spi_chipsel(), which itself calls gpio_set_value(). Or, at
> least my kernel thinks so, since I get a barrage of oops-type output
> screaming at me whenever I hit the SPI device. :)
>
> Am I missing something, or is this a known (or at least now-identified)
> limitation of the current mpc52xx_spi.c?
>
So, nobody has any feedback on this? :)
Would using a threaded handler for the SPI interrupts be likely to work
here?
b.g.
--
Bill Gatliff
Embedded systems training and consulting
http://billgatliff.com
bgat@billgatliff•com
prev parent reply other threads:[~2010-01-12 16:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-11 20:13 Sleep-capable GPIO slave-selects on MPC52xx? Bill Gatliff
2010-01-12 16:50 ` Bill Gatliff [this message]
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=4B4CA844.8040301@billgatliff.com \
--to=bgat@billgatliff$(echo .)com \
--cc=linuxppc-dev@ozlabs$(echo .)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