public inbox for ecos-devel@sourceware.org
 help / color / mirror / Atom feed
From: Chris Holgate <chris@zynaptic.com>
To: ecos-devel@ecos.sourceware.org
Subject: STM32 - I/O pullup and EXTI issues, plus new SPI driver.
Date: Fri, 21 Nov 2008 15:06:00 -0000	[thread overview]
Message-ID: <1227280292.8476.47.camel@hercules.zynaptic.com> (raw)

Hi folks,

I came across a couple of HAL issues while putting together my new SPI
driver for the STM32.  I appreciate that the maintainers are overloaded
with eCos 3.0 work at the moment, so I'll defer to them as to whether
any of this needs fixing now and can provide more information/patches on
request.

1) It's not possible to set pullups on I/Os using the provided
functions.  This is a trivial one-line fix to stm32-misc.c.

2) External interrupts don't work as they stand.  This requires a few
changes to the STM32 var_intr.h.  If required I can tidy up my changes
there and provide a patch which I've tested using a single I/O
(EXTINT0), but which would probably benefit from a bit more testing
using other I/O configurations.

3) I've now got full register maps for the AFIO, DMA and SPI blocks.
For development purposes I've kept these in a separate file from the
STM32 var_io.h, but can provide the file for merging if required.

FYI, I now have a DMA-based SPI driver that is fully functional in
kernel mode, but will need one or two changes (and some testing!) to
make it play nicely in non-kernel mode.  Probably best to leave that
until the 3.0 release is done, though.

Chris.



             reply	other threads:[~2008-11-21 15:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-21 15:06 Chris Holgate [this message]
2008-11-21 15:15 ` Simon Kallweit
2008-11-21 15:52 ` Jonathan Larmour
2008-11-21 15:53 ` Nick Garnett
2008-11-21 17:08   ` Chris Holgate
2008-11-21 17:35     ` Nick Garnett
2008-11-22 12:53       ` Chris Holgate

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=1227280292.8476.47.camel@hercules.zynaptic.com \
    --to=chris@zynaptic.com \
    --cc=ecos-devel@ecos.sourceware.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 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 read-only IMAP folder(s) and NNTP newsgroup(s).