From: Vitaly Wool <vwool@ru.mvista.com>
To: David Brownell <david-b@pacbell.net>
Cc: linux-kernel@vger.kernel.org,
spi-devel-general@lists.sourceforge.net, basicmark@yahoo.com,
stephen@streetfiresound.com, dpervushin@gmail.com
Subject: Re: [PATCH/RFC 0/2] simple SPI framework, refresh + ads7864 driver
Date: Tue, 04 Oct 2005 23:08:58 +0400 [thread overview]
Message-ID: <4342D34A.8040408@ru.mvista.com> (raw)
In-Reply-To: <20051004180237.9B4FDEE8F2@adsl-69-107-32-110.dsl.pltn13.pacbell.net>
Hi,
can you please describe the data flow in case of DMA transfer? Thanks!
Vitaly
David Brownell wrote:
>Following this will be two patches, refreshing the minimalist SPI stack
>I've sent before. Notable changes are:
>
> - Various updates to support real hardware, including reporting the
> IRQ associated with an SPI slave chip, providing void* handles for
> various flavors of board and controller state, dma_addr_t for I/O
> buffers, some control over protocol delays, and more.
>
> - New spi_alloc_master(). The driver model is happier if drivers
> don't allocate the class devices; this helps "rmmod" and friends,
> kind of handy for debugging drivers. It allocates controller
> specific memory not unlike alloc_netdev().
>
> - Various cleanup, notably removing Kconfig for all those drivers
> that don't yet exist. That was added purely to illustrate the
> potential scope of an SPI framework, when more folk were asking
> just why a Serial Peripheral Interface (*) was useful.
>
> - More kerneldoc. No Documentation/DocBook/spi.html though.
>
> - Now there's a real ADS7864 touchscreen/sensor driver; lightly
> tested, but it emits the right sort of input events and gives
> syfs access to the temperature, battery, and voltage sensors.
>
>This version seems real enough to integrate with.
>
>One goal is promote reuse of driver code -- for SPI controllers and
>slave chips connected using SPI -- while fitting them better into the
>driver model framework. Today, SPI devices only seem to get drivers
>that are board-specific; there's a fair amount of reinvent-the-wheel,
>and drivers that are unsuitable for upstream merging.
>
>I can now report this seems to be working with real controllers and
>real slave chips ... two of each to start with, but as yet there's no
>mix'n'match (with e.g. that touchscreen driver being used with a PXA
>SSP controller, not just OMAP MicroWire). That should just take a
>little bit of time and debugging.
>
>- Dave
>
>(*) And distinguish it from Singapore Paranormal Investigators. ;)
>
>-
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at http://www.tux.org/lkml/
>
>
>
>
next prev parent reply other threads:[~2005-10-04 19:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-04 18:02 [PATCH/RFC 0/2] simple SPI framework, refresh + ads7864 driver David Brownell
2005-10-04 19:08 ` Vitaly Wool [this message]
2005-10-05 7:56 ` Vitaly Wool
-- strict thread matches above, loose matches on Subject: below --
2005-10-04 20:18 David Brownell
2005-10-05 8:07 ` Vitaly Wool
2005-10-05 15:10 David Brownell
2005-10-13 19:37 ` Lee Revell
2005-10-05 15:18 David Brownell
2005-10-05 16:21 David Brownell
2005-10-05 16:24 ` Russell King
2005-10-05 17:27 ` David Brownell
2005-10-06 4:57 ` Vitaly Wool
2005-10-06 18:13 ` Mark Underwood
2005-10-06 18:20 ` Vitaly Wool
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=4342D34A.8040408@ru.mvista.com \
--to=vwool@ru.mvista.com \
--cc=basicmark@yahoo.com \
--cc=david-b@pacbell.net \
--cc=dpervushin@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=spi-devel-general@lists.sourceforge.net \
--cc=stephen@streetfiresound.com \
/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