| 
									
										
											  
											
												[PATCH] spi: simple SPI framework
This is the core of a small SPI framework, implementing the model of a
queue of messages which complete asynchronously (with thin synchronous
wrappers on top).
  - It's still less than 2KB of ".text" (ARM).  If there's got to be a
    mid-layer for something so simple, that's the right size budget.  :)
  - The guts use board-specific SPI device tables to build the driver
    model tree.  (Hardware probing is rarely an option.)
  - This version of Kconfig includes no drivers.  At this writing there
    are two known master controller drivers (PXA/SSP, OMAP MicroWire)
    and three protocol drivers (CS8415a, ADS7846, DataFlash) with LKML
    mentions of other drivers in development.
  - No userspace API.  There are several implementations to compare.
    Implement them like any other driver, and bind them with sysfs.
The changes from last version posted to LKML (on 11-Nov-2005) are minor,
and include:
  - One bugfix (removes a FIXME), with the visible effect of making device
    names be "spiB.C" where B is the bus number and C is the chipselect.
  - The "caller provides DMA mappings" mechanism now has kerneldoc, for
    DMA drivers that want to be fancy.
  - Hey, the framework init can be subsys_init.  Even though board init
    logic fires earlier, at arch_init ... since the framework init is
    for driver support, and the board init support uses static init.
  - Various additional spec/doc clarifications based on discussions
    with other folk.  It adds a brief "thank you" at the end, for folk
    who've helped nudge this framework into existence.
As I've said before, I think that "protocol tweaking" is the main support
that this driver framework will need to evolve.
From: Mark Underwood <basicmark@yahoo.com>
  Update the SPI framework to remove a potential priority inversion case by
  reverting to kmalloc if the pre-allocated DMA-safe buffer isn't available.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
											
										 
											2006-01-08 13:34:19 -08:00
										 |  |  | /*
 | 
					
						
							|  |  |  |  * spi.c - SPI init/core code | 
					
						
							|  |  |  |  * | 
					
						
							|  |  |  |  * Copyright (C) 2005 David Brownell | 
					
						
							|  |  |  |  * | 
					
						
							|  |  |  |  * This program is free software; you can redistribute it and/or modify | 
					
						
							|  |  |  |  * it under the terms of the GNU General Public License as published by | 
					
						
							|  |  |  |  * the Free Software Foundation; either version 2 of the License, or | 
					
						
							|  |  |  |  * (at your option) any later version. | 
					
						
							|  |  |  |  * | 
					
						
							|  |  |  |  * This program is distributed in the hope that it will be useful, | 
					
						
							|  |  |  |  * but WITHOUT ANY WARRANTY; without even the implied warranty of | 
					
						
							|  |  |  |  * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the | 
					
						
							|  |  |  |  * GNU General Public License for more details. | 
					
						
							|  |  |  |  * | 
					
						
							|  |  |  |  * You should have received a copy of the GNU General Public License | 
					
						
							|  |  |  |  * along with this program; if not, write to the Free Software | 
					
						
							|  |  |  |  * Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA. | 
					
						
							|  |  |  |  */ | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | #include <linux/kernel.h>
 | 
					
						
							|  |  |  | #include <linux/device.h>
 | 
					
						
							|  |  |  | #include <linux/init.h>
 | 
					
						
							|  |  |  | #include <linux/cache.h>
 | 
					
						
							| 
									
										
										
										
											2007-07-17 04:04:16 -07:00
										 |  |  | #include <linux/mutex.h>
 | 
					
						
							| 
									
										
											  
											
												[PATCH] spi: simple SPI framework
This is the core of a small SPI framework, implementing the model of a
queue of messages which complete asynchronously (with thin synchronous
wrappers on top).
  - It's still less than 2KB of ".text" (ARM).  If there's got to be a
    mid-layer for something so simple, that's the right size budget.  :)
  - The guts use board-specific SPI device tables to build the driver
    model tree.  (Hardware probing is rarely an option.)
  - This version of Kconfig includes no drivers.  At this writing there
    are two known master controller drivers (PXA/SSP, OMAP MicroWire)
    and three protocol drivers (CS8415a, ADS7846, DataFlash) with LKML
    mentions of other drivers in development.
  - No userspace API.  There are several implementations to compare.
    Implement them like any other driver, and bind them with sysfs.
The changes from last version posted to LKML (on 11-Nov-2005) are minor,
and include:
  - One bugfix (removes a FIXME), with the visible effect of making device
    names be "spiB.C" where B is the bus number and C is the chipselect.
  - The "caller provides DMA mappings" mechanism now has kerneldoc, for
    DMA drivers that want to be fancy.
  - Hey, the framework init can be subsys_init.  Even though board init
    logic fires earlier, at arch_init ... since the framework init is
    for driver support, and the board init support uses static init.
  - Various additional spec/doc clarifications based on discussions
    with other folk.  It adds a brief "thank you" at the end, for folk
    who've helped nudge this framework into existence.
As I've said before, I think that "protocol tweaking" is the main support
that this driver framework will need to evolve.
From: Mark Underwood <basicmark@yahoo.com>
  Update the SPI framework to remove a potential priority inversion case by
  reverting to kmalloc if the pre-allocated DMA-safe buffer isn't available.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
											
										 
											2006-01-08 13:34:19 -08:00
										 |  |  | #include <linux/spi/spi.h>
 | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											2006-01-08 13:34:23 -08:00
										 |  |  | /* SPI bustype and spi_master class are registered after board init code
 | 
					
						
							|  |  |  |  * provides the SPI device tables, ensuring that both are present by the | 
					
						
							|  |  |  |  * time controller driver registration causes spi_devices to "enumerate". | 
					
						
							| 
									
										
											  
											
												[PATCH] spi: simple SPI framework
This is the core of a small SPI framework, implementing the model of a
queue of messages which complete asynchronously (with thin synchronous
wrappers on top).
  - It's still less than 2KB of ".text" (ARM).  If there's got to be a
    mid-layer for something so simple, that's the right size budget.  :)
  - The guts use board-specific SPI device tables to build the driver
    model tree.  (Hardware probing is rarely an option.)
  - This version of Kconfig includes no drivers.  At this writing there
    are two known master controller drivers (PXA/SSP, OMAP MicroWire)
    and three protocol drivers (CS8415a, ADS7846, DataFlash) with LKML
    mentions of other drivers in development.
  - No userspace API.  There are several implementations to compare.
    Implement them like any other driver, and bind them with sysfs.
The changes from last version posted to LKML (on 11-Nov-2005) are minor,
and include:
  - One bugfix (removes a FIXME), with the visible effect of making device
    names be "spiB.C" where B is the bus number and C is the chipselect.
  - The "caller provides DMA mappings" mechanism now has kerneldoc, for
    DMA drivers that want to be fancy.
  - Hey, the framework init can be subsys_init.  Even though board init
    logic fires earlier, at arch_init ... since the framework init is
    for driver support, and the board init support uses static init.
  - Various additional spec/doc clarifications based on discussions
    with other folk.  It adds a brief "thank you" at the end, for folk
    who've helped nudge this framework into existence.
As I've said before, I think that "protocol tweaking" is the main support
that this driver framework will need to evolve.
From: Mark Underwood <basicmark@yahoo.com>
  Update the SPI framework to remove a potential priority inversion case by
  reverting to kmalloc if the pre-allocated DMA-safe buffer isn't available.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
											
										 
											2006-01-08 13:34:19 -08:00
										 |  |  |  */ | 
					
						
							|  |  |  | static void spidev_release(struct device *dev) | 
					
						
							|  |  |  | { | 
					
						
							| 
									
										
										
										
											2007-02-12 00:52:45 -08:00
										 |  |  | 	struct spi_device	*spi = to_spi_device(dev); | 
					
						
							| 
									
										
											  
											
												[PATCH] spi: simple SPI framework
This is the core of a small SPI framework, implementing the model of a
queue of messages which complete asynchronously (with thin synchronous
wrappers on top).
  - It's still less than 2KB of ".text" (ARM).  If there's got to be a
    mid-layer for something so simple, that's the right size budget.  :)
  - The guts use board-specific SPI device tables to build the driver
    model tree.  (Hardware probing is rarely an option.)
  - This version of Kconfig includes no drivers.  At this writing there
    are two known master controller drivers (PXA/SSP, OMAP MicroWire)
    and three protocol drivers (CS8415a, ADS7846, DataFlash) with LKML
    mentions of other drivers in development.
  - No userspace API.  There are several implementations to compare.
    Implement them like any other driver, and bind them with sysfs.
The changes from last version posted to LKML (on 11-Nov-2005) are minor,
and include:
  - One bugfix (removes a FIXME), with the visible effect of making device
    names be "spiB.C" where B is the bus number and C is the chipselect.
  - The "caller provides DMA mappings" mechanism now has kerneldoc, for
    DMA drivers that want to be fancy.
  - Hey, the framework init can be subsys_init.  Even though board init
    logic fires earlier, at arch_init ... since the framework init is
    for driver support, and the board init support uses static init.
  - Various additional spec/doc clarifications based on discussions
    with other folk.  It adds a brief "thank you" at the end, for folk
    who've helped nudge this framework into existence.
As I've said before, I think that "protocol tweaking" is the main support
that this driver framework will need to evolve.
From: Mark Underwood <basicmark@yahoo.com>
  Update the SPI framework to remove a potential priority inversion case by
  reverting to kmalloc if the pre-allocated DMA-safe buffer isn't available.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
											
										 
											2006-01-08 13:34:19 -08:00
										 |  |  | 
 | 
					
						
							|  |  |  | 	/* spi masters may cleanup for released devices */ | 
					
						
							|  |  |  | 	if (spi->master->cleanup) | 
					
						
							|  |  |  | 		spi->master->cleanup(spi); | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											2006-01-08 13:34:25 -08:00
										 |  |  | 	spi_master_put(spi->master); | 
					
						
							| 
									
										
											  
											
												[PATCH] spi: simple SPI framework
This is the core of a small SPI framework, implementing the model of a
queue of messages which complete asynchronously (with thin synchronous
wrappers on top).
  - It's still less than 2KB of ".text" (ARM).  If there's got to be a
    mid-layer for something so simple, that's the right size budget.  :)
  - The guts use board-specific SPI device tables to build the driver
    model tree.  (Hardware probing is rarely an option.)
  - This version of Kconfig includes no drivers.  At this writing there
    are two known master controller drivers (PXA/SSP, OMAP MicroWire)
    and three protocol drivers (CS8415a, ADS7846, DataFlash) with LKML
    mentions of other drivers in development.
  - No userspace API.  There are several implementations to compare.
    Implement them like any other driver, and bind them with sysfs.
The changes from last version posted to LKML (on 11-Nov-2005) are minor,
and include:
  - One bugfix (removes a FIXME), with the visible effect of making device
    names be "spiB.C" where B is the bus number and C is the chipselect.
  - The "caller provides DMA mappings" mechanism now has kerneldoc, for
    DMA drivers that want to be fancy.
  - Hey, the framework init can be subsys_init.  Even though board init
    logic fires earlier, at arch_init ... since the framework init is
    for driver support, and the board init support uses static init.
  - Various additional spec/doc clarifications based on discussions
    with other folk.  It adds a brief "thank you" at the end, for folk
    who've helped nudge this framework into existence.
As I've said before, I think that "protocol tweaking" is the main support
that this driver framework will need to evolve.
From: Mark Underwood <basicmark@yahoo.com>
  Update the SPI framework to remove a potential priority inversion case by
  reverting to kmalloc if the pre-allocated DMA-safe buffer isn't available.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
											
										 
											2006-01-08 13:34:19 -08:00
										 |  |  | 	kfree(dev); | 
					
						
							|  |  |  | } | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | static ssize_t | 
					
						
							|  |  |  | modalias_show(struct device *dev, struct device_attribute *a, char *buf) | 
					
						
							|  |  |  | { | 
					
						
							|  |  |  | 	const struct spi_device	*spi = to_spi_device(dev); | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											2009-01-06 10:44:37 -08:00
										 |  |  | 	return sprintf(buf, "%s\n", spi->modalias); | 
					
						
							| 
									
										
											  
											
												[PATCH] spi: simple SPI framework
This is the core of a small SPI framework, implementing the model of a
queue of messages which complete asynchronously (with thin synchronous
wrappers on top).
  - It's still less than 2KB of ".text" (ARM).  If there's got to be a
    mid-layer for something so simple, that's the right size budget.  :)
  - The guts use board-specific SPI device tables to build the driver
    model tree.  (Hardware probing is rarely an option.)
  - This version of Kconfig includes no drivers.  At this writing there
    are two known master controller drivers (PXA/SSP, OMAP MicroWire)
    and three protocol drivers (CS8415a, ADS7846, DataFlash) with LKML
    mentions of other drivers in development.
  - No userspace API.  There are several implementations to compare.
    Implement them like any other driver, and bind them with sysfs.
The changes from last version posted to LKML (on 11-Nov-2005) are minor,
and include:
  - One bugfix (removes a FIXME), with the visible effect of making device
    names be "spiB.C" where B is the bus number and C is the chipselect.
  - The "caller provides DMA mappings" mechanism now has kerneldoc, for
    DMA drivers that want to be fancy.
  - Hey, the framework init can be subsys_init.  Even though board init
    logic fires earlier, at arch_init ... since the framework init is
    for driver support, and the board init support uses static init.
  - Various additional spec/doc clarifications based on discussions
    with other folk.  It adds a brief "thank you" at the end, for folk
    who've helped nudge this framework into existence.
As I've said before, I think that "protocol tweaking" is the main support
that this driver framework will need to evolve.
From: Mark Underwood <basicmark@yahoo.com>
  Update the SPI framework to remove a potential priority inversion case by
  reverting to kmalloc if the pre-allocated DMA-safe buffer isn't available.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
											
										 
											2006-01-08 13:34:19 -08:00
										 |  |  | } | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | static struct device_attribute spi_dev_attrs[] = { | 
					
						
							|  |  |  | 	__ATTR_RO(modalias), | 
					
						
							|  |  |  | 	__ATTR_NULL, | 
					
						
							|  |  |  | }; | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | /* modalias support makes "modprobe $MODALIAS" new-style hotplug work,
 | 
					
						
							|  |  |  |  * and the sysfs version makes coldplug work too. | 
					
						
							|  |  |  |  */ | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | static int spi_match_device(struct device *dev, struct device_driver *drv) | 
					
						
							|  |  |  | { | 
					
						
							|  |  |  | 	const struct spi_device	*spi = to_spi_device(dev); | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											2009-01-06 10:44:37 -08:00
										 |  |  | 	return strcmp(spi->modalias, drv->name) == 0; | 
					
						
							| 
									
										
											  
											
												[PATCH] spi: simple SPI framework
This is the core of a small SPI framework, implementing the model of a
queue of messages which complete asynchronously (with thin synchronous
wrappers on top).
  - It's still less than 2KB of ".text" (ARM).  If there's got to be a
    mid-layer for something so simple, that's the right size budget.  :)
  - The guts use board-specific SPI device tables to build the driver
    model tree.  (Hardware probing is rarely an option.)
  - This version of Kconfig includes no drivers.  At this writing there
    are two known master controller drivers (PXA/SSP, OMAP MicroWire)
    and three protocol drivers (CS8415a, ADS7846, DataFlash) with LKML
    mentions of other drivers in development.
  - No userspace API.  There are several implementations to compare.
    Implement them like any other driver, and bind them with sysfs.
The changes from last version posted to LKML (on 11-Nov-2005) are minor,
and include:
  - One bugfix (removes a FIXME), with the visible effect of making device
    names be "spiB.C" where B is the bus number and C is the chipselect.
  - The "caller provides DMA mappings" mechanism now has kerneldoc, for
    DMA drivers that want to be fancy.
  - Hey, the framework init can be subsys_init.  Even though board init
    logic fires earlier, at arch_init ... since the framework init is
    for driver support, and the board init support uses static init.
  - Various additional spec/doc clarifications based on discussions
    with other folk.  It adds a brief "thank you" at the end, for folk
    who've helped nudge this framework into existence.
As I've said before, I think that "protocol tweaking" is the main support
that this driver framework will need to evolve.
From: Mark Underwood <basicmark@yahoo.com>
  Update the SPI framework to remove a potential priority inversion case by
  reverting to kmalloc if the pre-allocated DMA-safe buffer isn't available.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
											
										 
											2006-01-08 13:34:19 -08:00
										 |  |  | } | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											2007-08-14 15:15:12 +02:00
										 |  |  | static int spi_uevent(struct device *dev, struct kobj_uevent_env *env) | 
					
						
							| 
									
										
											  
											
												[PATCH] spi: simple SPI framework
This is the core of a small SPI framework, implementing the model of a
queue of messages which complete asynchronously (with thin synchronous
wrappers on top).
  - It's still less than 2KB of ".text" (ARM).  If there's got to be a
    mid-layer for something so simple, that's the right size budget.  :)
  - The guts use board-specific SPI device tables to build the driver
    model tree.  (Hardware probing is rarely an option.)
  - This version of Kconfig includes no drivers.  At this writing there
    are two known master controller drivers (PXA/SSP, OMAP MicroWire)
    and three protocol drivers (CS8415a, ADS7846, DataFlash) with LKML
    mentions of other drivers in development.
  - No userspace API.  There are several implementations to compare.
    Implement them like any other driver, and bind them with sysfs.
The changes from last version posted to LKML (on 11-Nov-2005) are minor,
and include:
  - One bugfix (removes a FIXME), with the visible effect of making device
    names be "spiB.C" where B is the bus number and C is the chipselect.
  - The "caller provides DMA mappings" mechanism now has kerneldoc, for
    DMA drivers that want to be fancy.
  - Hey, the framework init can be subsys_init.  Even though board init
    logic fires earlier, at arch_init ... since the framework init is
    for driver support, and the board init support uses static init.
  - Various additional spec/doc clarifications based on discussions
    with other folk.  It adds a brief "thank you" at the end, for folk
    who've helped nudge this framework into existence.
As I've said before, I think that "protocol tweaking" is the main support
that this driver framework will need to evolve.
From: Mark Underwood <basicmark@yahoo.com>
  Update the SPI framework to remove a potential priority inversion case by
  reverting to kmalloc if the pre-allocated DMA-safe buffer isn't available.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
											
										 
											2006-01-08 13:34:19 -08:00
										 |  |  | { | 
					
						
							|  |  |  | 	const struct spi_device		*spi = to_spi_device(dev); | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											2007-08-14 15:15:12 +02:00
										 |  |  | 	add_uevent_var(env, "MODALIAS=%s", spi->modalias); | 
					
						
							| 
									
										
											  
											
												[PATCH] spi: simple SPI framework
This is the core of a small SPI framework, implementing the model of a
queue of messages which complete asynchronously (with thin synchronous
wrappers on top).
  - It's still less than 2KB of ".text" (ARM).  If there's got to be a
    mid-layer for something so simple, that's the right size budget.  :)
  - The guts use board-specific SPI device tables to build the driver
    model tree.  (Hardware probing is rarely an option.)
  - This version of Kconfig includes no drivers.  At this writing there
    are two known master controller drivers (PXA/SSP, OMAP MicroWire)
    and three protocol drivers (CS8415a, ADS7846, DataFlash) with LKML
    mentions of other drivers in development.
  - No userspace API.  There are several implementations to compare.
    Implement them like any other driver, and bind them with sysfs.
The changes from last version posted to LKML (on 11-Nov-2005) are minor,
and include:
  - One bugfix (removes a FIXME), with the visible effect of making device
    names be "spiB.C" where B is the bus number and C is the chipselect.
  - The "caller provides DMA mappings" mechanism now has kerneldoc, for
    DMA drivers that want to be fancy.
  - Hey, the framework init can be subsys_init.  Even though board init
    logic fires earlier, at arch_init ... since the framework init is
    for driver support, and the board init support uses static init.
  - Various additional spec/doc clarifications based on discussions
    with other folk.  It adds a brief "thank you" at the end, for folk
    who've helped nudge this framework into existence.
As I've said before, I think that "protocol tweaking" is the main support
that this driver framework will need to evolve.
From: Mark Underwood <basicmark@yahoo.com>
  Update the SPI framework to remove a potential priority inversion case by
  reverting to kmalloc if the pre-allocated DMA-safe buffer isn't available.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
											
										 
											2006-01-08 13:34:19 -08:00
										 |  |  | 	return 0; | 
					
						
							|  |  |  | } | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | #ifdef	CONFIG_PM
 | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | static int spi_suspend(struct device *dev, pm_message_t message) | 
					
						
							|  |  |  | { | 
					
						
							| 
									
										
										
										
											2008-02-06 01:38:10 -08:00
										 |  |  | 	int			value = 0; | 
					
						
							| 
									
										
										
										
											2006-01-08 13:34:23 -08:00
										 |  |  | 	struct spi_driver	*drv = to_spi_driver(dev->driver); | 
					
						
							| 
									
										
											  
											
												[PATCH] spi: simple SPI framework
This is the core of a small SPI framework, implementing the model of a
queue of messages which complete asynchronously (with thin synchronous
wrappers on top).
  - It's still less than 2KB of ".text" (ARM).  If there's got to be a
    mid-layer for something so simple, that's the right size budget.  :)
  - The guts use board-specific SPI device tables to build the driver
    model tree.  (Hardware probing is rarely an option.)
  - This version of Kconfig includes no drivers.  At this writing there
    are two known master controller drivers (PXA/SSP, OMAP MicroWire)
    and three protocol drivers (CS8415a, ADS7846, DataFlash) with LKML
    mentions of other drivers in development.
  - No userspace API.  There are several implementations to compare.
    Implement them like any other driver, and bind them with sysfs.
The changes from last version posted to LKML (on 11-Nov-2005) are minor,
and include:
  - One bugfix (removes a FIXME), with the visible effect of making device
    names be "spiB.C" where B is the bus number and C is the chipselect.
  - The "caller provides DMA mappings" mechanism now has kerneldoc, for
    DMA drivers that want to be fancy.
  - Hey, the framework init can be subsys_init.  Even though board init
    logic fires earlier, at arch_init ... since the framework init is
    for driver support, and the board init support uses static init.
  - Various additional spec/doc clarifications based on discussions
    with other folk.  It adds a brief "thank you" at the end, for folk
    who've helped nudge this framework into existence.
As I've said before, I think that "protocol tweaking" is the main support
that this driver framework will need to evolve.
From: Mark Underwood <basicmark@yahoo.com>
  Update the SPI framework to remove a potential priority inversion case by
  reverting to kmalloc if the pre-allocated DMA-safe buffer isn't available.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
											
										 
											2006-01-08 13:34:19 -08:00
										 |  |  | 
 | 
					
						
							|  |  |  | 	/* suspend will stop irqs and dma; no more i/o */ | 
					
						
							| 
									
										
										
										
											2008-02-06 01:38:10 -08:00
										 |  |  | 	if (drv) { | 
					
						
							|  |  |  | 		if (drv->suspend) | 
					
						
							|  |  |  | 			value = drv->suspend(to_spi_device(dev), message); | 
					
						
							|  |  |  | 		else | 
					
						
							|  |  |  | 			dev_dbg(dev, "... can't suspend\n"); | 
					
						
							|  |  |  | 	} | 
					
						
							| 
									
										
											  
											
												[PATCH] spi: simple SPI framework
This is the core of a small SPI framework, implementing the model of a
queue of messages which complete asynchronously (with thin synchronous
wrappers on top).
  - It's still less than 2KB of ".text" (ARM).  If there's got to be a
    mid-layer for something so simple, that's the right size budget.  :)
  - The guts use board-specific SPI device tables to build the driver
    model tree.  (Hardware probing is rarely an option.)
  - This version of Kconfig includes no drivers.  At this writing there
    are two known master controller drivers (PXA/SSP, OMAP MicroWire)
    and three protocol drivers (CS8415a, ADS7846, DataFlash) with LKML
    mentions of other drivers in development.
  - No userspace API.  There are several implementations to compare.
    Implement them like any other driver, and bind them with sysfs.
The changes from last version posted to LKML (on 11-Nov-2005) are minor,
and include:
  - One bugfix (removes a FIXME), with the visible effect of making device
    names be "spiB.C" where B is the bus number and C is the chipselect.
  - The "caller provides DMA mappings" mechanism now has kerneldoc, for
    DMA drivers that want to be fancy.
  - Hey, the framework init can be subsys_init.  Even though board init
    logic fires earlier, at arch_init ... since the framework init is
    for driver support, and the board init support uses static init.
  - Various additional spec/doc clarifications based on discussions
    with other folk.  It adds a brief "thank you" at the end, for folk
    who've helped nudge this framework into existence.
As I've said before, I think that "protocol tweaking" is the main support
that this driver framework will need to evolve.
From: Mark Underwood <basicmark@yahoo.com>
  Update the SPI framework to remove a potential priority inversion case by
  reverting to kmalloc if the pre-allocated DMA-safe buffer isn't available.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
											
										 
											2006-01-08 13:34:19 -08:00
										 |  |  | 	return value; | 
					
						
							|  |  |  | } | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | static int spi_resume(struct device *dev) | 
					
						
							|  |  |  | { | 
					
						
							| 
									
										
										
										
											2008-02-06 01:38:10 -08:00
										 |  |  | 	int			value = 0; | 
					
						
							| 
									
										
										
										
											2006-01-08 13:34:23 -08:00
										 |  |  | 	struct spi_driver	*drv = to_spi_driver(dev->driver); | 
					
						
							| 
									
										
											  
											
												[PATCH] spi: simple SPI framework
This is the core of a small SPI framework, implementing the model of a
queue of messages which complete asynchronously (with thin synchronous
wrappers on top).
  - It's still less than 2KB of ".text" (ARM).  If there's got to be a
    mid-layer for something so simple, that's the right size budget.  :)
  - The guts use board-specific SPI device tables to build the driver
    model tree.  (Hardware probing is rarely an option.)
  - This version of Kconfig includes no drivers.  At this writing there
    are two known master controller drivers (PXA/SSP, OMAP MicroWire)
    and three protocol drivers (CS8415a, ADS7846, DataFlash) with LKML
    mentions of other drivers in development.
  - No userspace API.  There are several implementations to compare.
    Implement them like any other driver, and bind them with sysfs.
The changes from last version posted to LKML (on 11-Nov-2005) are minor,
and include:
  - One bugfix (removes a FIXME), with the visible effect of making device
    names be "spiB.C" where B is the bus number and C is the chipselect.
  - The "caller provides DMA mappings" mechanism now has kerneldoc, for
    DMA drivers that want to be fancy.
  - Hey, the framework init can be subsys_init.  Even though board init
    logic fires earlier, at arch_init ... since the framework init is
    for driver support, and the board init support uses static init.
  - Various additional spec/doc clarifications based on discussions
    with other folk.  It adds a brief "thank you" at the end, for folk
    who've helped nudge this framework into existence.
As I've said before, I think that "protocol tweaking" is the main support
that this driver framework will need to evolve.
From: Mark Underwood <basicmark@yahoo.com>
  Update the SPI framework to remove a potential priority inversion case by
  reverting to kmalloc if the pre-allocated DMA-safe buffer isn't available.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
											
										 
											2006-01-08 13:34:19 -08:00
										 |  |  | 
 | 
					
						
							|  |  |  | 	/* resume may restart the i/o queue */ | 
					
						
							| 
									
										
										
										
											2008-02-06 01:38:10 -08:00
										 |  |  | 	if (drv) { | 
					
						
							|  |  |  | 		if (drv->resume) | 
					
						
							|  |  |  | 			value = drv->resume(to_spi_device(dev)); | 
					
						
							|  |  |  | 		else | 
					
						
							|  |  |  | 			dev_dbg(dev, "... can't resume\n"); | 
					
						
							|  |  |  | 	} | 
					
						
							| 
									
										
											  
											
												[PATCH] spi: simple SPI framework
This is the core of a small SPI framework, implementing the model of a
queue of messages which complete asynchronously (with thin synchronous
wrappers on top).
  - It's still less than 2KB of ".text" (ARM).  If there's got to be a
    mid-layer for something so simple, that's the right size budget.  :)
  - The guts use board-specific SPI device tables to build the driver
    model tree.  (Hardware probing is rarely an option.)
  - This version of Kconfig includes no drivers.  At this writing there
    are two known master controller drivers (PXA/SSP, OMAP MicroWire)
    and three protocol drivers (CS8415a, ADS7846, DataFlash) with LKML
    mentions of other drivers in development.
  - No userspace API.  There are several implementations to compare.
    Implement them like any other driver, and bind them with sysfs.
The changes from last version posted to LKML (on 11-Nov-2005) are minor,
and include:
  - One bugfix (removes a FIXME), with the visible effect of making device
    names be "spiB.C" where B is the bus number and C is the chipselect.
  - The "caller provides DMA mappings" mechanism now has kerneldoc, for
    DMA drivers that want to be fancy.
  - Hey, the framework init can be subsys_init.  Even though board init
    logic fires earlier, at arch_init ... since the framework init is
    for driver support, and the board init support uses static init.
  - Various additional spec/doc clarifications based on discussions
    with other folk.  It adds a brief "thank you" at the end, for folk
    who've helped nudge this framework into existence.
As I've said before, I think that "protocol tweaking" is the main support
that this driver framework will need to evolve.
From: Mark Underwood <basicmark@yahoo.com>
  Update the SPI framework to remove a potential priority inversion case by
  reverting to kmalloc if the pre-allocated DMA-safe buffer isn't available.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
											
										 
											2006-01-08 13:34:19 -08:00
										 |  |  | 	return value; | 
					
						
							|  |  |  | } | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | #else
 | 
					
						
							|  |  |  | #define spi_suspend	NULL
 | 
					
						
							|  |  |  | #define spi_resume	NULL
 | 
					
						
							|  |  |  | #endif
 | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | struct bus_type spi_bus_type = { | 
					
						
							|  |  |  | 	.name		= "spi", | 
					
						
							|  |  |  | 	.dev_attrs	= spi_dev_attrs, | 
					
						
							|  |  |  | 	.match		= spi_match_device, | 
					
						
							|  |  |  | 	.uevent		= spi_uevent, | 
					
						
							|  |  |  | 	.suspend	= spi_suspend, | 
					
						
							|  |  |  | 	.resume		= spi_resume, | 
					
						
							|  |  |  | }; | 
					
						
							|  |  |  | EXPORT_SYMBOL_GPL(spi_bus_type); | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											2006-01-08 13:34:23 -08:00
										 |  |  | 
 | 
					
						
							|  |  |  | static int spi_drv_probe(struct device *dev) | 
					
						
							|  |  |  | { | 
					
						
							|  |  |  | 	const struct spi_driver		*sdrv = to_spi_driver(dev->driver); | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | 	return sdrv->probe(to_spi_device(dev)); | 
					
						
							|  |  |  | } | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | static int spi_drv_remove(struct device *dev) | 
					
						
							|  |  |  | { | 
					
						
							|  |  |  | 	const struct spi_driver		*sdrv = to_spi_driver(dev->driver); | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | 	return sdrv->remove(to_spi_device(dev)); | 
					
						
							|  |  |  | } | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | static void spi_drv_shutdown(struct device *dev) | 
					
						
							|  |  |  | { | 
					
						
							|  |  |  | 	const struct spi_driver		*sdrv = to_spi_driver(dev->driver); | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | 	sdrv->shutdown(to_spi_device(dev)); | 
					
						
							|  |  |  | } | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											2007-05-08 00:32:21 -07:00
										 |  |  | /**
 | 
					
						
							|  |  |  |  * spi_register_driver - register a SPI driver | 
					
						
							|  |  |  |  * @sdrv: the driver to register | 
					
						
							|  |  |  |  * Context: can sleep | 
					
						
							|  |  |  |  */ | 
					
						
							| 
									
										
										
										
											2006-01-08 13:34:23 -08:00
										 |  |  | int spi_register_driver(struct spi_driver *sdrv) | 
					
						
							|  |  |  | { | 
					
						
							|  |  |  | 	sdrv->driver.bus = &spi_bus_type; | 
					
						
							|  |  |  | 	if (sdrv->probe) | 
					
						
							|  |  |  | 		sdrv->driver.probe = spi_drv_probe; | 
					
						
							|  |  |  | 	if (sdrv->remove) | 
					
						
							|  |  |  | 		sdrv->driver.remove = spi_drv_remove; | 
					
						
							|  |  |  | 	if (sdrv->shutdown) | 
					
						
							|  |  |  | 		sdrv->driver.shutdown = spi_drv_shutdown; | 
					
						
							|  |  |  | 	return driver_register(&sdrv->driver); | 
					
						
							|  |  |  | } | 
					
						
							|  |  |  | EXPORT_SYMBOL_GPL(spi_register_driver); | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
											  
											
												[PATCH] spi: simple SPI framework
This is the core of a small SPI framework, implementing the model of a
queue of messages which complete asynchronously (with thin synchronous
wrappers on top).
  - It's still less than 2KB of ".text" (ARM).  If there's got to be a
    mid-layer for something so simple, that's the right size budget.  :)
  - The guts use board-specific SPI device tables to build the driver
    model tree.  (Hardware probing is rarely an option.)
  - This version of Kconfig includes no drivers.  At this writing there
    are two known master controller drivers (PXA/SSP, OMAP MicroWire)
    and three protocol drivers (CS8415a, ADS7846, DataFlash) with LKML
    mentions of other drivers in development.
  - No userspace API.  There are several implementations to compare.
    Implement them like any other driver, and bind them with sysfs.
The changes from last version posted to LKML (on 11-Nov-2005) are minor,
and include:
  - One bugfix (removes a FIXME), with the visible effect of making device
    names be "spiB.C" where B is the bus number and C is the chipselect.
  - The "caller provides DMA mappings" mechanism now has kerneldoc, for
    DMA drivers that want to be fancy.
  - Hey, the framework init can be subsys_init.  Even though board init
    logic fires earlier, at arch_init ... since the framework init is
    for driver support, and the board init support uses static init.
  - Various additional spec/doc clarifications based on discussions
    with other folk.  It adds a brief "thank you" at the end, for folk
    who've helped nudge this framework into existence.
As I've said before, I think that "protocol tweaking" is the main support
that this driver framework will need to evolve.
From: Mark Underwood <basicmark@yahoo.com>
  Update the SPI framework to remove a potential priority inversion case by
  reverting to kmalloc if the pre-allocated DMA-safe buffer isn't available.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
											
										 
											2006-01-08 13:34:19 -08:00
										 |  |  | /*-------------------------------------------------------------------------*/ | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | /* SPI devices should normally not be created by SPI device drivers; that
 | 
					
						
							|  |  |  |  * would make them board-specific.  Similarly with SPI master drivers. | 
					
						
							|  |  |  |  * Device registration normally goes into like arch/.../mach.../board-YYY.c | 
					
						
							|  |  |  |  * with other readonly (flashable) information about mainboard devices. | 
					
						
							|  |  |  |  */ | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | struct boardinfo { | 
					
						
							|  |  |  | 	struct list_head	list; | 
					
						
							|  |  |  | 	unsigned		n_board_info; | 
					
						
							|  |  |  | 	struct spi_board_info	board_info[0]; | 
					
						
							|  |  |  | }; | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | static LIST_HEAD(board_list); | 
					
						
							| 
									
										
										
										
											2007-07-17 04:04:16 -07:00
										 |  |  | static DEFINE_MUTEX(board_lock); | 
					
						
							| 
									
										
											  
											
												[PATCH] spi: simple SPI framework
This is the core of a small SPI framework, implementing the model of a
queue of messages which complete asynchronously (with thin synchronous
wrappers on top).
  - It's still less than 2KB of ".text" (ARM).  If there's got to be a
    mid-layer for something so simple, that's the right size budget.  :)
  - The guts use board-specific SPI device tables to build the driver
    model tree.  (Hardware probing is rarely an option.)
  - This version of Kconfig includes no drivers.  At this writing there
    are two known master controller drivers (PXA/SSP, OMAP MicroWire)
    and three protocol drivers (CS8415a, ADS7846, DataFlash) with LKML
    mentions of other drivers in development.
  - No userspace API.  There are several implementations to compare.
    Implement them like any other driver, and bind them with sysfs.
The changes from last version posted to LKML (on 11-Nov-2005) are minor,
and include:
  - One bugfix (removes a FIXME), with the visible effect of making device
    names be "spiB.C" where B is the bus number and C is the chipselect.
  - The "caller provides DMA mappings" mechanism now has kerneldoc, for
    DMA drivers that want to be fancy.
  - Hey, the framework init can be subsys_init.  Even though board init
    logic fires earlier, at arch_init ... since the framework init is
    for driver support, and the board init support uses static init.
  - Various additional spec/doc clarifications based on discussions
    with other folk.  It adds a brief "thank you" at the end, for folk
    who've helped nudge this framework into existence.
As I've said before, I think that "protocol tweaking" is the main support
that this driver framework will need to evolve.
From: Mark Underwood <basicmark@yahoo.com>
  Update the SPI framework to remove a potential priority inversion case by
  reverting to kmalloc if the pre-allocated DMA-safe buffer isn't available.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
											
										 
											2006-01-08 13:34:19 -08:00
										 |  |  | 
 | 
					
						
							| 
									
										
										
										
											2008-05-15 16:50:22 -06:00
										 |  |  | /**
 | 
					
						
							|  |  |  |  * spi_alloc_device - Allocate a new SPI device | 
					
						
							|  |  |  |  * @master: Controller to which device is connected | 
					
						
							|  |  |  |  * Context: can sleep | 
					
						
							|  |  |  |  * | 
					
						
							|  |  |  |  * Allows a driver to allocate and initialize a spi_device without | 
					
						
							|  |  |  |  * registering it immediately.  This allows a driver to directly | 
					
						
							|  |  |  |  * fill the spi_device with device parameters before calling | 
					
						
							|  |  |  |  * spi_add_device() on it. | 
					
						
							|  |  |  |  * | 
					
						
							|  |  |  |  * Caller is responsible to call spi_add_device() on the returned | 
					
						
							|  |  |  |  * spi_device structure to add it to the SPI master.  If the caller | 
					
						
							|  |  |  |  * needs to discard the spi_device without adding it, then it should | 
					
						
							|  |  |  |  * call spi_dev_put() on it. | 
					
						
							|  |  |  |  * | 
					
						
							|  |  |  |  * Returns a pointer to the new device, or NULL. | 
					
						
							|  |  |  |  */ | 
					
						
							|  |  |  | struct spi_device *spi_alloc_device(struct spi_master *master) | 
					
						
							|  |  |  | { | 
					
						
							|  |  |  | 	struct spi_device	*spi; | 
					
						
							|  |  |  | 	struct device		*dev = master->dev.parent; | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | 	if (!spi_master_get(master)) | 
					
						
							|  |  |  | 		return NULL; | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | 	spi = kzalloc(sizeof *spi, GFP_KERNEL); | 
					
						
							|  |  |  | 	if (!spi) { | 
					
						
							|  |  |  | 		dev_err(dev, "cannot alloc spi_device\n"); | 
					
						
							|  |  |  | 		spi_master_put(master); | 
					
						
							|  |  |  | 		return NULL; | 
					
						
							|  |  |  | 	} | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | 	spi->master = master; | 
					
						
							|  |  |  | 	spi->dev.parent = dev; | 
					
						
							|  |  |  | 	spi->dev.bus = &spi_bus_type; | 
					
						
							|  |  |  | 	spi->dev.release = spidev_release; | 
					
						
							|  |  |  | 	device_initialize(&spi->dev); | 
					
						
							|  |  |  | 	return spi; | 
					
						
							|  |  |  | } | 
					
						
							|  |  |  | EXPORT_SYMBOL_GPL(spi_alloc_device); | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | /**
 | 
					
						
							|  |  |  |  * spi_add_device - Add spi_device allocated with spi_alloc_device | 
					
						
							|  |  |  |  * @spi: spi_device to register | 
					
						
							|  |  |  |  * | 
					
						
							|  |  |  |  * Companion function to spi_alloc_device.  Devices allocated with | 
					
						
							|  |  |  |  * spi_alloc_device can be added onto the spi bus with this function. | 
					
						
							|  |  |  |  * | 
					
						
							| 
									
										
										
										
											2008-08-15 00:40:44 -07:00
										 |  |  |  * Returns 0 on success; negative errno on failure | 
					
						
							| 
									
										
										
										
											2008-05-15 16:50:22 -06:00
										 |  |  |  */ | 
					
						
							|  |  |  | int spi_add_device(struct spi_device *spi) | 
					
						
							|  |  |  | { | 
					
						
							| 
									
										
										
										
											2008-08-15 00:40:44 -07:00
										 |  |  | 	static DEFINE_MUTEX(spi_add_lock); | 
					
						
							| 
									
										
										
										
											2008-05-15 16:50:22 -06:00
										 |  |  | 	struct device *dev = spi->master->dev.parent; | 
					
						
							|  |  |  | 	int status; | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | 	/* Chipselects are numbered 0..max; validate. */ | 
					
						
							|  |  |  | 	if (spi->chip_select >= spi->master->num_chipselect) { | 
					
						
							|  |  |  | 		dev_err(dev, "cs%d >= max %d\n", | 
					
						
							|  |  |  | 			spi->chip_select, | 
					
						
							|  |  |  | 			spi->master->num_chipselect); | 
					
						
							|  |  |  | 		return -EINVAL; | 
					
						
							|  |  |  | 	} | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | 	/* Set the bus ID string */ | 
					
						
							| 
									
										
										
										
											2009-01-06 10:44:37 -08:00
										 |  |  | 	dev_set_name(&spi->dev, "%s.%u", dev_name(&spi->master->dev), | 
					
						
							| 
									
										
										
										
											2008-05-15 16:50:22 -06:00
										 |  |  | 			spi->chip_select); | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											2008-08-15 00:40:44 -07:00
										 |  |  | 
 | 
					
						
							|  |  |  | 	/* We need to make sure there's no other device with this
 | 
					
						
							|  |  |  | 	 * chipselect **BEFORE** we call setup(), else we'll trash | 
					
						
							|  |  |  | 	 * its configuration.  Lock against concurrent add() calls. | 
					
						
							|  |  |  | 	 */ | 
					
						
							|  |  |  | 	mutex_lock(&spi_add_lock); | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											2009-01-06 10:44:37 -08:00
										 |  |  | 	if (bus_find_device_by_name(&spi_bus_type, NULL, dev_name(&spi->dev)) | 
					
						
							| 
									
										
										
										
											2008-08-15 00:40:44 -07:00
										 |  |  | 			!= NULL) { | 
					
						
							|  |  |  | 		dev_err(dev, "chipselect %d already in use\n", | 
					
						
							|  |  |  | 				spi->chip_select); | 
					
						
							|  |  |  | 		status = -EBUSY; | 
					
						
							|  |  |  | 		goto done; | 
					
						
							|  |  |  | 	} | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | 	/* Drivers may modify this initial i/o setup, but will
 | 
					
						
							|  |  |  | 	 * normally rely on the device being setup.  Devices | 
					
						
							|  |  |  | 	 * using SPI_CS_HIGH can't coexist well otherwise... | 
					
						
							|  |  |  | 	 */ | 
					
						
							| 
									
										
										
										
											2009-06-17 16:26:03 -07:00
										 |  |  | 	status = spi_setup(spi); | 
					
						
							| 
									
										
										
										
											2008-05-15 16:50:22 -06:00
										 |  |  | 	if (status < 0) { | 
					
						
							|  |  |  | 		dev_err(dev, "can't %s %s, status %d\n", | 
					
						
							| 
									
										
										
										
											2009-01-06 10:44:37 -08:00
										 |  |  | 				"setup", dev_name(&spi->dev), status); | 
					
						
							| 
									
										
										
										
											2008-08-15 00:40:44 -07:00
										 |  |  | 		goto done; | 
					
						
							| 
									
										
										
										
											2008-05-15 16:50:22 -06:00
										 |  |  | 	} | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											2008-08-15 00:40:44 -07:00
										 |  |  | 	/* Device may be bound to an active driver when this returns */ | 
					
						
							| 
									
										
										
										
											2008-05-15 16:50:22 -06:00
										 |  |  | 	status = device_add(&spi->dev); | 
					
						
							| 
									
										
										
										
											2008-08-15 00:40:44 -07:00
										 |  |  | 	if (status < 0) | 
					
						
							| 
									
										
										
										
											2008-05-15 16:50:22 -06:00
										 |  |  | 		dev_err(dev, "can't %s %s, status %d\n", | 
					
						
							| 
									
										
										
										
											2009-01-06 10:44:37 -08:00
										 |  |  | 				"add", dev_name(&spi->dev), status); | 
					
						
							| 
									
										
										
										
											2008-08-15 00:40:44 -07:00
										 |  |  | 	else | 
					
						
							| 
									
										
										
										
											2009-01-06 10:44:37 -08:00
										 |  |  | 		dev_dbg(dev, "registered child %s\n", dev_name(&spi->dev)); | 
					
						
							| 
									
										
										
										
											2008-05-15 16:50:22 -06:00
										 |  |  | 
 | 
					
						
							| 
									
										
										
										
											2008-08-15 00:40:44 -07:00
										 |  |  | done: | 
					
						
							|  |  |  | 	mutex_unlock(&spi_add_lock); | 
					
						
							|  |  |  | 	return status; | 
					
						
							| 
									
										
										
										
											2008-05-15 16:50:22 -06:00
										 |  |  | } | 
					
						
							|  |  |  | EXPORT_SYMBOL_GPL(spi_add_device); | 
					
						
							| 
									
										
											  
											
												[PATCH] spi: simple SPI framework
This is the core of a small SPI framework, implementing the model of a
queue of messages which complete asynchronously (with thin synchronous
wrappers on top).
  - It's still less than 2KB of ".text" (ARM).  If there's got to be a
    mid-layer for something so simple, that's the right size budget.  :)
  - The guts use board-specific SPI device tables to build the driver
    model tree.  (Hardware probing is rarely an option.)
  - This version of Kconfig includes no drivers.  At this writing there
    are two known master controller drivers (PXA/SSP, OMAP MicroWire)
    and three protocol drivers (CS8415a, ADS7846, DataFlash) with LKML
    mentions of other drivers in development.
  - No userspace API.  There are several implementations to compare.
    Implement them like any other driver, and bind them with sysfs.
The changes from last version posted to LKML (on 11-Nov-2005) are minor,
and include:
  - One bugfix (removes a FIXME), with the visible effect of making device
    names be "spiB.C" where B is the bus number and C is the chipselect.
  - The "caller provides DMA mappings" mechanism now has kerneldoc, for
    DMA drivers that want to be fancy.
  - Hey, the framework init can be subsys_init.  Even though board init
    logic fires earlier, at arch_init ... since the framework init is
    for driver support, and the board init support uses static init.
  - Various additional spec/doc clarifications based on discussions
    with other folk.  It adds a brief "thank you" at the end, for folk
    who've helped nudge this framework into existence.
As I've said before, I think that "protocol tweaking" is the main support
that this driver framework will need to evolve.
From: Mark Underwood <basicmark@yahoo.com>
  Update the SPI framework to remove a potential priority inversion case by
  reverting to kmalloc if the pre-allocated DMA-safe buffer isn't available.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
											
										 
											2006-01-08 13:34:19 -08:00
										 |  |  | 
 | 
					
						
							| 
									
										
										
										
											2007-05-08 00:32:21 -07:00
										 |  |  | /**
 | 
					
						
							|  |  |  |  * spi_new_device - instantiate one new SPI device | 
					
						
							|  |  |  |  * @master: Controller to which device is connected | 
					
						
							|  |  |  |  * @chip: Describes the SPI device | 
					
						
							|  |  |  |  * Context: can sleep | 
					
						
							|  |  |  |  * | 
					
						
							|  |  |  |  * On typical mainboards, this is purely internal; and it's not needed | 
					
						
							| 
									
										
											  
											
												[PATCH] spi: simple SPI framework
This is the core of a small SPI framework, implementing the model of a
queue of messages which complete asynchronously (with thin synchronous
wrappers on top).
  - It's still less than 2KB of ".text" (ARM).  If there's got to be a
    mid-layer for something so simple, that's the right size budget.  :)
  - The guts use board-specific SPI device tables to build the driver
    model tree.  (Hardware probing is rarely an option.)
  - This version of Kconfig includes no drivers.  At this writing there
    are two known master controller drivers (PXA/SSP, OMAP MicroWire)
    and three protocol drivers (CS8415a, ADS7846, DataFlash) with LKML
    mentions of other drivers in development.
  - No userspace API.  There are several implementations to compare.
    Implement them like any other driver, and bind them with sysfs.
The changes from last version posted to LKML (on 11-Nov-2005) are minor,
and include:
  - One bugfix (removes a FIXME), with the visible effect of making device
    names be "spiB.C" where B is the bus number and C is the chipselect.
  - The "caller provides DMA mappings" mechanism now has kerneldoc, for
    DMA drivers that want to be fancy.
  - Hey, the framework init can be subsys_init.  Even though board init
    logic fires earlier, at arch_init ... since the framework init is
    for driver support, and the board init support uses static init.
  - Various additional spec/doc clarifications based on discussions
    with other folk.  It adds a brief "thank you" at the end, for folk
    who've helped nudge this framework into existence.
As I've said before, I think that "protocol tweaking" is the main support
that this driver framework will need to evolve.
From: Mark Underwood <basicmark@yahoo.com>
  Update the SPI framework to remove a potential priority inversion case by
  reverting to kmalloc if the pre-allocated DMA-safe buffer isn't available.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
											
										 
											2006-01-08 13:34:19 -08:00
										 |  |  |  * after board init creates the hard-wired devices.  Some development | 
					
						
							|  |  |  |  * platforms may not be able to use spi_register_board_info though, and | 
					
						
							|  |  |  |  * this is exported so that for example a USB or parport based adapter | 
					
						
							|  |  |  |  * driver could add devices (which it would learn about out-of-band). | 
					
						
							| 
									
										
										
										
											2007-07-31 00:39:45 -07:00
										 |  |  |  * | 
					
						
							|  |  |  |  * Returns the new device, or NULL. | 
					
						
							| 
									
										
											  
											
												[PATCH] spi: simple SPI framework
This is the core of a small SPI framework, implementing the model of a
queue of messages which complete asynchronously (with thin synchronous
wrappers on top).
  - It's still less than 2KB of ".text" (ARM).  If there's got to be a
    mid-layer for something so simple, that's the right size budget.  :)
  - The guts use board-specific SPI device tables to build the driver
    model tree.  (Hardware probing is rarely an option.)
  - This version of Kconfig includes no drivers.  At this writing there
    are two known master controller drivers (PXA/SSP, OMAP MicroWire)
    and three protocol drivers (CS8415a, ADS7846, DataFlash) with LKML
    mentions of other drivers in development.
  - No userspace API.  There are several implementations to compare.
    Implement them like any other driver, and bind them with sysfs.
The changes from last version posted to LKML (on 11-Nov-2005) are minor,
and include:
  - One bugfix (removes a FIXME), with the visible effect of making device
    names be "spiB.C" where B is the bus number and C is the chipselect.
  - The "caller provides DMA mappings" mechanism now has kerneldoc, for
    DMA drivers that want to be fancy.
  - Hey, the framework init can be subsys_init.  Even though board init
    logic fires earlier, at arch_init ... since the framework init is
    for driver support, and the board init support uses static init.
  - Various additional spec/doc clarifications based on discussions
    with other folk.  It adds a brief "thank you" at the end, for folk
    who've helped nudge this framework into existence.
As I've said before, I think that "protocol tweaking" is the main support
that this driver framework will need to evolve.
From: Mark Underwood <basicmark@yahoo.com>
  Update the SPI framework to remove a potential priority inversion case by
  reverting to kmalloc if the pre-allocated DMA-safe buffer isn't available.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
											
										 
											2006-01-08 13:34:19 -08:00
										 |  |  |  */ | 
					
						
							| 
									
										
										
										
											2007-03-26 21:32:23 -08:00
										 |  |  | struct spi_device *spi_new_device(struct spi_master *master, | 
					
						
							|  |  |  | 				  struct spi_board_info *chip) | 
					
						
							| 
									
										
											  
											
												[PATCH] spi: simple SPI framework
This is the core of a small SPI framework, implementing the model of a
queue of messages which complete asynchronously (with thin synchronous
wrappers on top).
  - It's still less than 2KB of ".text" (ARM).  If there's got to be a
    mid-layer for something so simple, that's the right size budget.  :)
  - The guts use board-specific SPI device tables to build the driver
    model tree.  (Hardware probing is rarely an option.)
  - This version of Kconfig includes no drivers.  At this writing there
    are two known master controller drivers (PXA/SSP, OMAP MicroWire)
    and three protocol drivers (CS8415a, ADS7846, DataFlash) with LKML
    mentions of other drivers in development.
  - No userspace API.  There are several implementations to compare.
    Implement them like any other driver, and bind them with sysfs.
The changes from last version posted to LKML (on 11-Nov-2005) are minor,
and include:
  - One bugfix (removes a FIXME), with the visible effect of making device
    names be "spiB.C" where B is the bus number and C is the chipselect.
  - The "caller provides DMA mappings" mechanism now has kerneldoc, for
    DMA drivers that want to be fancy.
  - Hey, the framework init can be subsys_init.  Even though board init
    logic fires earlier, at arch_init ... since the framework init is
    for driver support, and the board init support uses static init.
  - Various additional spec/doc clarifications based on discussions
    with other folk.  It adds a brief "thank you" at the end, for folk
    who've helped nudge this framework into existence.
As I've said before, I think that "protocol tweaking" is the main support
that this driver framework will need to evolve.
From: Mark Underwood <basicmark@yahoo.com>
  Update the SPI framework to remove a potential priority inversion case by
  reverting to kmalloc if the pre-allocated DMA-safe buffer isn't available.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
											
										 
											2006-01-08 13:34:19 -08:00
										 |  |  | { | 
					
						
							|  |  |  | 	struct spi_device	*proxy; | 
					
						
							|  |  |  | 	int			status; | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											2007-07-31 00:39:45 -07:00
										 |  |  | 	/* NOTE:  caller did any chip->bus_num checks necessary.
 | 
					
						
							|  |  |  | 	 * | 
					
						
							|  |  |  | 	 * Also, unless we change the return value convention to use | 
					
						
							|  |  |  | 	 * error-or-pointer (not NULL-or-pointer), troubleshootability | 
					
						
							|  |  |  | 	 * suggests syslogged diagnostics are best here (ugh). | 
					
						
							|  |  |  | 	 */ | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											2008-05-15 16:50:22 -06:00
										 |  |  | 	proxy = spi_alloc_device(master); | 
					
						
							|  |  |  | 	if (!proxy) | 
					
						
							| 
									
										
											  
											
												[PATCH] spi: simple SPI framework
This is the core of a small SPI framework, implementing the model of a
queue of messages which complete asynchronously (with thin synchronous
wrappers on top).
  - It's still less than 2KB of ".text" (ARM).  If there's got to be a
    mid-layer for something so simple, that's the right size budget.  :)
  - The guts use board-specific SPI device tables to build the driver
    model tree.  (Hardware probing is rarely an option.)
  - This version of Kconfig includes no drivers.  At this writing there
    are two known master controller drivers (PXA/SSP, OMAP MicroWire)
    and three protocol drivers (CS8415a, ADS7846, DataFlash) with LKML
    mentions of other drivers in development.
  - No userspace API.  There are several implementations to compare.
    Implement them like any other driver, and bind them with sysfs.
The changes from last version posted to LKML (on 11-Nov-2005) are minor,
and include:
  - One bugfix (removes a FIXME), with the visible effect of making device
    names be "spiB.C" where B is the bus number and C is the chipselect.
  - The "caller provides DMA mappings" mechanism now has kerneldoc, for
    DMA drivers that want to be fancy.
  - Hey, the framework init can be subsys_init.  Even though board init
    logic fires earlier, at arch_init ... since the framework init is
    for driver support, and the board init support uses static init.
  - Various additional spec/doc clarifications based on discussions
    with other folk.  It adds a brief "thank you" at the end, for folk
    who've helped nudge this framework into existence.
As I've said before, I think that "protocol tweaking" is the main support
that this driver framework will need to evolve.
From: Mark Underwood <basicmark@yahoo.com>
  Update the SPI framework to remove a potential priority inversion case by
  reverting to kmalloc if the pre-allocated DMA-safe buffer isn't available.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
											
										 
											2006-01-08 13:34:19 -08:00
										 |  |  | 		return NULL; | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											2008-07-23 21:29:55 -07:00
										 |  |  | 	WARN_ON(strlen(chip->modalias) >= sizeof(proxy->modalias)); | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
											  
											
												[PATCH] spi: simple SPI framework
This is the core of a small SPI framework, implementing the model of a
queue of messages which complete asynchronously (with thin synchronous
wrappers on top).
  - It's still less than 2KB of ".text" (ARM).  If there's got to be a
    mid-layer for something so simple, that's the right size budget.  :)
  - The guts use board-specific SPI device tables to build the driver
    model tree.  (Hardware probing is rarely an option.)
  - This version of Kconfig includes no drivers.  At this writing there
    are two known master controller drivers (PXA/SSP, OMAP MicroWire)
    and three protocol drivers (CS8415a, ADS7846, DataFlash) with LKML
    mentions of other drivers in development.
  - No userspace API.  There are several implementations to compare.
    Implement them like any other driver, and bind them with sysfs.
The changes from last version posted to LKML (on 11-Nov-2005) are minor,
and include:
  - One bugfix (removes a FIXME), with the visible effect of making device
    names be "spiB.C" where B is the bus number and C is the chipselect.
  - The "caller provides DMA mappings" mechanism now has kerneldoc, for
    DMA drivers that want to be fancy.
  - Hey, the framework init can be subsys_init.  Even though board init
    logic fires earlier, at arch_init ... since the framework init is
    for driver support, and the board init support uses static init.
  - Various additional spec/doc clarifications based on discussions
    with other folk.  It adds a brief "thank you" at the end, for folk
    who've helped nudge this framework into existence.
As I've said before, I think that "protocol tweaking" is the main support
that this driver framework will need to evolve.
From: Mark Underwood <basicmark@yahoo.com>
  Update the SPI framework to remove a potential priority inversion case by
  reverting to kmalloc if the pre-allocated DMA-safe buffer isn't available.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
											
										 
											2006-01-08 13:34:19 -08:00
										 |  |  | 	proxy->chip_select = chip->chip_select; | 
					
						
							|  |  |  | 	proxy->max_speed_hz = chip->max_speed_hz; | 
					
						
							| 
									
										
										
										
											2006-06-28 07:47:15 -07:00
										 |  |  | 	proxy->mode = chip->mode; | 
					
						
							| 
									
										
											  
											
												[PATCH] spi: simple SPI framework
This is the core of a small SPI framework, implementing the model of a
queue of messages which complete asynchronously (with thin synchronous
wrappers on top).
  - It's still less than 2KB of ".text" (ARM).  If there's got to be a
    mid-layer for something so simple, that's the right size budget.  :)
  - The guts use board-specific SPI device tables to build the driver
    model tree.  (Hardware probing is rarely an option.)
  - This version of Kconfig includes no drivers.  At this writing there
    are two known master controller drivers (PXA/SSP, OMAP MicroWire)
    and three protocol drivers (CS8415a, ADS7846, DataFlash) with LKML
    mentions of other drivers in development.
  - No userspace API.  There are several implementations to compare.
    Implement them like any other driver, and bind them with sysfs.
The changes from last version posted to LKML (on 11-Nov-2005) are minor,
and include:
  - One bugfix (removes a FIXME), with the visible effect of making device
    names be "spiB.C" where B is the bus number and C is the chipselect.
  - The "caller provides DMA mappings" mechanism now has kerneldoc, for
    DMA drivers that want to be fancy.
  - Hey, the framework init can be subsys_init.  Even though board init
    logic fires earlier, at arch_init ... since the framework init is
    for driver support, and the board init support uses static init.
  - Various additional spec/doc clarifications based on discussions
    with other folk.  It adds a brief "thank you" at the end, for folk
    who've helped nudge this framework into existence.
As I've said before, I think that "protocol tweaking" is the main support
that this driver framework will need to evolve.
From: Mark Underwood <basicmark@yahoo.com>
  Update the SPI framework to remove a potential priority inversion case by
  reverting to kmalloc if the pre-allocated DMA-safe buffer isn't available.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
											
										 
											2006-01-08 13:34:19 -08:00
										 |  |  | 	proxy->irq = chip->irq; | 
					
						
							| 
									
										
										
										
											2008-07-23 21:29:55 -07:00
										 |  |  | 	strlcpy(proxy->modalias, chip->modalias, sizeof(proxy->modalias)); | 
					
						
							| 
									
										
											  
											
												[PATCH] spi: simple SPI framework
This is the core of a small SPI framework, implementing the model of a
queue of messages which complete asynchronously (with thin synchronous
wrappers on top).
  - It's still less than 2KB of ".text" (ARM).  If there's got to be a
    mid-layer for something so simple, that's the right size budget.  :)
  - The guts use board-specific SPI device tables to build the driver
    model tree.  (Hardware probing is rarely an option.)
  - This version of Kconfig includes no drivers.  At this writing there
    are two known master controller drivers (PXA/SSP, OMAP MicroWire)
    and three protocol drivers (CS8415a, ADS7846, DataFlash) with LKML
    mentions of other drivers in development.
  - No userspace API.  There are several implementations to compare.
    Implement them like any other driver, and bind them with sysfs.
The changes from last version posted to LKML (on 11-Nov-2005) are minor,
and include:
  - One bugfix (removes a FIXME), with the visible effect of making device
    names be "spiB.C" where B is the bus number and C is the chipselect.
  - The "caller provides DMA mappings" mechanism now has kerneldoc, for
    DMA drivers that want to be fancy.
  - Hey, the framework init can be subsys_init.  Even though board init
    logic fires earlier, at arch_init ... since the framework init is
    for driver support, and the board init support uses static init.
  - Various additional spec/doc clarifications based on discussions
    with other folk.  It adds a brief "thank you" at the end, for folk
    who've helped nudge this framework into existence.
As I've said before, I think that "protocol tweaking" is the main support
that this driver framework will need to evolve.
From: Mark Underwood <basicmark@yahoo.com>
  Update the SPI framework to remove a potential priority inversion case by
  reverting to kmalloc if the pre-allocated DMA-safe buffer isn't available.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
											
										 
											2006-01-08 13:34:19 -08:00
										 |  |  | 	proxy->dev.platform_data = (void *) chip->platform_data; | 
					
						
							|  |  |  | 	proxy->controller_data = chip->controller_data; | 
					
						
							|  |  |  | 	proxy->controller_state = NULL; | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											2008-05-15 16:50:22 -06:00
										 |  |  | 	status = spi_add_device(proxy); | 
					
						
							| 
									
										
											  
											
												[PATCH] spi: simple SPI framework
This is the core of a small SPI framework, implementing the model of a
queue of messages which complete asynchronously (with thin synchronous
wrappers on top).
  - It's still less than 2KB of ".text" (ARM).  If there's got to be a
    mid-layer for something so simple, that's the right size budget.  :)
  - The guts use board-specific SPI device tables to build the driver
    model tree.  (Hardware probing is rarely an option.)
  - This version of Kconfig includes no drivers.  At this writing there
    are two known master controller drivers (PXA/SSP, OMAP MicroWire)
    and three protocol drivers (CS8415a, ADS7846, DataFlash) with LKML
    mentions of other drivers in development.
  - No userspace API.  There are several implementations to compare.
    Implement them like any other driver, and bind them with sysfs.
The changes from last version posted to LKML (on 11-Nov-2005) are minor,
and include:
  - One bugfix (removes a FIXME), with the visible effect of making device
    names be "spiB.C" where B is the bus number and C is the chipselect.
  - The "caller provides DMA mappings" mechanism now has kerneldoc, for
    DMA drivers that want to be fancy.
  - Hey, the framework init can be subsys_init.  Even though board init
    logic fires earlier, at arch_init ... since the framework init is
    for driver support, and the board init support uses static init.
  - Various additional spec/doc clarifications based on discussions
    with other folk.  It adds a brief "thank you" at the end, for folk
    who've helped nudge this framework into existence.
As I've said before, I think that "protocol tweaking" is the main support
that this driver framework will need to evolve.
From: Mark Underwood <basicmark@yahoo.com>
  Update the SPI framework to remove a potential priority inversion case by
  reverting to kmalloc if the pre-allocated DMA-safe buffer isn't available.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
											
										 
											2006-01-08 13:34:19 -08:00
										 |  |  | 	if (status < 0) { | 
					
						
							| 
									
										
										
										
											2008-05-15 16:50:22 -06:00
										 |  |  | 		spi_dev_put(proxy); | 
					
						
							|  |  |  | 		return NULL; | 
					
						
							| 
									
										
											  
											
												[PATCH] spi: simple SPI framework
This is the core of a small SPI framework, implementing the model of a
queue of messages which complete asynchronously (with thin synchronous
wrappers on top).
  - It's still less than 2KB of ".text" (ARM).  If there's got to be a
    mid-layer for something so simple, that's the right size budget.  :)
  - The guts use board-specific SPI device tables to build the driver
    model tree.  (Hardware probing is rarely an option.)
  - This version of Kconfig includes no drivers.  At this writing there
    are two known master controller drivers (PXA/SSP, OMAP MicroWire)
    and three protocol drivers (CS8415a, ADS7846, DataFlash) with LKML
    mentions of other drivers in development.
  - No userspace API.  There are several implementations to compare.
    Implement them like any other driver, and bind them with sysfs.
The changes from last version posted to LKML (on 11-Nov-2005) are minor,
and include:
  - One bugfix (removes a FIXME), with the visible effect of making device
    names be "spiB.C" where B is the bus number and C is the chipselect.
  - The "caller provides DMA mappings" mechanism now has kerneldoc, for
    DMA drivers that want to be fancy.
  - Hey, the framework init can be subsys_init.  Even though board init
    logic fires earlier, at arch_init ... since the framework init is
    for driver support, and the board init support uses static init.
  - Various additional spec/doc clarifications based on discussions
    with other folk.  It adds a brief "thank you" at the end, for folk
    who've helped nudge this framework into existence.
As I've said before, I think that "protocol tweaking" is the main support
that this driver framework will need to evolve.
From: Mark Underwood <basicmark@yahoo.com>
  Update the SPI framework to remove a potential priority inversion case by
  reverting to kmalloc if the pre-allocated DMA-safe buffer isn't available.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
											
										 
											2006-01-08 13:34:19 -08:00
										 |  |  | 	} | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | 	return proxy; | 
					
						
							|  |  |  | } | 
					
						
							|  |  |  | EXPORT_SYMBOL_GPL(spi_new_device); | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											2007-05-08 00:32:21 -07:00
										 |  |  | /**
 | 
					
						
							|  |  |  |  * spi_register_board_info - register SPI devices for a given board | 
					
						
							|  |  |  |  * @info: array of chip descriptors | 
					
						
							|  |  |  |  * @n: how many descriptors are provided | 
					
						
							|  |  |  |  * Context: can sleep | 
					
						
							|  |  |  |  * | 
					
						
							| 
									
										
											  
											
												[PATCH] spi: simple SPI framework
This is the core of a small SPI framework, implementing the model of a
queue of messages which complete asynchronously (with thin synchronous
wrappers on top).
  - It's still less than 2KB of ".text" (ARM).  If there's got to be a
    mid-layer for something so simple, that's the right size budget.  :)
  - The guts use board-specific SPI device tables to build the driver
    model tree.  (Hardware probing is rarely an option.)
  - This version of Kconfig includes no drivers.  At this writing there
    are two known master controller drivers (PXA/SSP, OMAP MicroWire)
    and three protocol drivers (CS8415a, ADS7846, DataFlash) with LKML
    mentions of other drivers in development.
  - No userspace API.  There are several implementations to compare.
    Implement them like any other driver, and bind them with sysfs.
The changes from last version posted to LKML (on 11-Nov-2005) are minor,
and include:
  - One bugfix (removes a FIXME), with the visible effect of making device
    names be "spiB.C" where B is the bus number and C is the chipselect.
  - The "caller provides DMA mappings" mechanism now has kerneldoc, for
    DMA drivers that want to be fancy.
  - Hey, the framework init can be subsys_init.  Even though board init
    logic fires earlier, at arch_init ... since the framework init is
    for driver support, and the board init support uses static init.
  - Various additional spec/doc clarifications based on discussions
    with other folk.  It adds a brief "thank you" at the end, for folk
    who've helped nudge this framework into existence.
As I've said before, I think that "protocol tweaking" is the main support
that this driver framework will need to evolve.
From: Mark Underwood <basicmark@yahoo.com>
  Update the SPI framework to remove a potential priority inversion case by
  reverting to kmalloc if the pre-allocated DMA-safe buffer isn't available.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
											
										 
											2006-01-08 13:34:19 -08:00
										 |  |  |  * Board-specific early init code calls this (probably during arch_initcall) | 
					
						
							|  |  |  |  * with segments of the SPI device table.  Any device nodes are created later, | 
					
						
							|  |  |  |  * after the relevant parent SPI controller (bus_num) is defined.  We keep | 
					
						
							|  |  |  |  * this table of devices forever, so that reloading a controller driver will | 
					
						
							|  |  |  |  * not make Linux forget about these hard-wired devices. | 
					
						
							|  |  |  |  * | 
					
						
							|  |  |  |  * Other code can also call this, e.g. a particular add-on board might provide | 
					
						
							|  |  |  |  * SPI devices through its expansion connector, so code initializing that board | 
					
						
							|  |  |  |  * would naturally declare its SPI devices. | 
					
						
							|  |  |  |  * | 
					
						
							|  |  |  |  * The board info passed can safely be __initdata ... but be careful of | 
					
						
							|  |  |  |  * any embedded pointers (platform_data, etc), they're copied as-is. | 
					
						
							|  |  |  |  */ | 
					
						
							|  |  |  | int __init | 
					
						
							|  |  |  | spi_register_board_info(struct spi_board_info const *info, unsigned n) | 
					
						
							|  |  |  | { | 
					
						
							|  |  |  | 	struct boardinfo	*bi; | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											2006-01-08 13:34:23 -08:00
										 |  |  | 	bi = kmalloc(sizeof(*bi) + n * sizeof *info, GFP_KERNEL); | 
					
						
							| 
									
										
											  
											
												[PATCH] spi: simple SPI framework
This is the core of a small SPI framework, implementing the model of a
queue of messages which complete asynchronously (with thin synchronous
wrappers on top).
  - It's still less than 2KB of ".text" (ARM).  If there's got to be a
    mid-layer for something so simple, that's the right size budget.  :)
  - The guts use board-specific SPI device tables to build the driver
    model tree.  (Hardware probing is rarely an option.)
  - This version of Kconfig includes no drivers.  At this writing there
    are two known master controller drivers (PXA/SSP, OMAP MicroWire)
    and three protocol drivers (CS8415a, ADS7846, DataFlash) with LKML
    mentions of other drivers in development.
  - No userspace API.  There are several implementations to compare.
    Implement them like any other driver, and bind them with sysfs.
The changes from last version posted to LKML (on 11-Nov-2005) are minor,
and include:
  - One bugfix (removes a FIXME), with the visible effect of making device
    names be "spiB.C" where B is the bus number and C is the chipselect.
  - The "caller provides DMA mappings" mechanism now has kerneldoc, for
    DMA drivers that want to be fancy.
  - Hey, the framework init can be subsys_init.  Even though board init
    logic fires earlier, at arch_init ... since the framework init is
    for driver support, and the board init support uses static init.
  - Various additional spec/doc clarifications based on discussions
    with other folk.  It adds a brief "thank you" at the end, for folk
    who've helped nudge this framework into existence.
As I've said before, I think that "protocol tweaking" is the main support
that this driver framework will need to evolve.
From: Mark Underwood <basicmark@yahoo.com>
  Update the SPI framework to remove a potential priority inversion case by
  reverting to kmalloc if the pre-allocated DMA-safe buffer isn't available.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
											
										 
											2006-01-08 13:34:19 -08:00
										 |  |  | 	if (!bi) | 
					
						
							|  |  |  | 		return -ENOMEM; | 
					
						
							|  |  |  | 	bi->n_board_info = n; | 
					
						
							| 
									
										
										
										
											2006-01-08 13:34:23 -08:00
										 |  |  | 	memcpy(bi->board_info, info, n * sizeof *info); | 
					
						
							| 
									
										
											  
											
												[PATCH] spi: simple SPI framework
This is the core of a small SPI framework, implementing the model of a
queue of messages which complete asynchronously (with thin synchronous
wrappers on top).
  - It's still less than 2KB of ".text" (ARM).  If there's got to be a
    mid-layer for something so simple, that's the right size budget.  :)
  - The guts use board-specific SPI device tables to build the driver
    model tree.  (Hardware probing is rarely an option.)
  - This version of Kconfig includes no drivers.  At this writing there
    are two known master controller drivers (PXA/SSP, OMAP MicroWire)
    and three protocol drivers (CS8415a, ADS7846, DataFlash) with LKML
    mentions of other drivers in development.
  - No userspace API.  There are several implementations to compare.
    Implement them like any other driver, and bind them with sysfs.
The changes from last version posted to LKML (on 11-Nov-2005) are minor,
and include:
  - One bugfix (removes a FIXME), with the visible effect of making device
    names be "spiB.C" where B is the bus number and C is the chipselect.
  - The "caller provides DMA mappings" mechanism now has kerneldoc, for
    DMA drivers that want to be fancy.
  - Hey, the framework init can be subsys_init.  Even though board init
    logic fires earlier, at arch_init ... since the framework init is
    for driver support, and the board init support uses static init.
  - Various additional spec/doc clarifications based on discussions
    with other folk.  It adds a brief "thank you" at the end, for folk
    who've helped nudge this framework into existence.
As I've said before, I think that "protocol tweaking" is the main support
that this driver framework will need to evolve.
From: Mark Underwood <basicmark@yahoo.com>
  Update the SPI framework to remove a potential priority inversion case by
  reverting to kmalloc if the pre-allocated DMA-safe buffer isn't available.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
											
										 
											2006-01-08 13:34:19 -08:00
										 |  |  | 
 | 
					
						
							| 
									
										
										
										
											2007-07-17 04:04:16 -07:00
										 |  |  | 	mutex_lock(&board_lock); | 
					
						
							| 
									
										
											  
											
												[PATCH] spi: simple SPI framework
This is the core of a small SPI framework, implementing the model of a
queue of messages which complete asynchronously (with thin synchronous
wrappers on top).
  - It's still less than 2KB of ".text" (ARM).  If there's got to be a
    mid-layer for something so simple, that's the right size budget.  :)
  - The guts use board-specific SPI device tables to build the driver
    model tree.  (Hardware probing is rarely an option.)
  - This version of Kconfig includes no drivers.  At this writing there
    are two known master controller drivers (PXA/SSP, OMAP MicroWire)
    and three protocol drivers (CS8415a, ADS7846, DataFlash) with LKML
    mentions of other drivers in development.
  - No userspace API.  There are several implementations to compare.
    Implement them like any other driver, and bind them with sysfs.
The changes from last version posted to LKML (on 11-Nov-2005) are minor,
and include:
  - One bugfix (removes a FIXME), with the visible effect of making device
    names be "spiB.C" where B is the bus number and C is the chipselect.
  - The "caller provides DMA mappings" mechanism now has kerneldoc, for
    DMA drivers that want to be fancy.
  - Hey, the framework init can be subsys_init.  Even though board init
    logic fires earlier, at arch_init ... since the framework init is
    for driver support, and the board init support uses static init.
  - Various additional spec/doc clarifications based on discussions
    with other folk.  It adds a brief "thank you" at the end, for folk
    who've helped nudge this framework into existence.
As I've said before, I think that "protocol tweaking" is the main support
that this driver framework will need to evolve.
From: Mark Underwood <basicmark@yahoo.com>
  Update the SPI framework to remove a potential priority inversion case by
  reverting to kmalloc if the pre-allocated DMA-safe buffer isn't available.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
											
										 
											2006-01-08 13:34:19 -08:00
										 |  |  | 	list_add_tail(&bi->list, &board_list); | 
					
						
							| 
									
										
										
										
											2007-07-17 04:04:16 -07:00
										 |  |  | 	mutex_unlock(&board_lock); | 
					
						
							| 
									
										
											  
											
												[PATCH] spi: simple SPI framework
This is the core of a small SPI framework, implementing the model of a
queue of messages which complete asynchronously (with thin synchronous
wrappers on top).
  - It's still less than 2KB of ".text" (ARM).  If there's got to be a
    mid-layer for something so simple, that's the right size budget.  :)
  - The guts use board-specific SPI device tables to build the driver
    model tree.  (Hardware probing is rarely an option.)
  - This version of Kconfig includes no drivers.  At this writing there
    are two known master controller drivers (PXA/SSP, OMAP MicroWire)
    and three protocol drivers (CS8415a, ADS7846, DataFlash) with LKML
    mentions of other drivers in development.
  - No userspace API.  There are several implementations to compare.
    Implement them like any other driver, and bind them with sysfs.
The changes from last version posted to LKML (on 11-Nov-2005) are minor,
and include:
  - One bugfix (removes a FIXME), with the visible effect of making device
    names be "spiB.C" where B is the bus number and C is the chipselect.
  - The "caller provides DMA mappings" mechanism now has kerneldoc, for
    DMA drivers that want to be fancy.
  - Hey, the framework init can be subsys_init.  Even though board init
    logic fires earlier, at arch_init ... since the framework init is
    for driver support, and the board init support uses static init.
  - Various additional spec/doc clarifications based on discussions
    with other folk.  It adds a brief "thank you" at the end, for folk
    who've helped nudge this framework into existence.
As I've said before, I think that "protocol tweaking" is the main support
that this driver framework will need to evolve.
From: Mark Underwood <basicmark@yahoo.com>
  Update the SPI framework to remove a potential priority inversion case by
  reverting to kmalloc if the pre-allocated DMA-safe buffer isn't available.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
											
										 
											2006-01-08 13:34:19 -08:00
										 |  |  | 	return 0; | 
					
						
							|  |  |  | } | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | /* FIXME someone should add support for a __setup("spi", ...) that
 | 
					
						
							|  |  |  |  * creates board info from kernel command lines | 
					
						
							|  |  |  |  */ | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											2007-07-21 04:37:52 -07:00
										 |  |  | static void scan_boardinfo(struct spi_master *master) | 
					
						
							| 
									
										
											  
											
												[PATCH] spi: simple SPI framework
This is the core of a small SPI framework, implementing the model of a
queue of messages which complete asynchronously (with thin synchronous
wrappers on top).
  - It's still less than 2KB of ".text" (ARM).  If there's got to be a
    mid-layer for something so simple, that's the right size budget.  :)
  - The guts use board-specific SPI device tables to build the driver
    model tree.  (Hardware probing is rarely an option.)
  - This version of Kconfig includes no drivers.  At this writing there
    are two known master controller drivers (PXA/SSP, OMAP MicroWire)
    and three protocol drivers (CS8415a, ADS7846, DataFlash) with LKML
    mentions of other drivers in development.
  - No userspace API.  There are several implementations to compare.
    Implement them like any other driver, and bind them with sysfs.
The changes from last version posted to LKML (on 11-Nov-2005) are minor,
and include:
  - One bugfix (removes a FIXME), with the visible effect of making device
    names be "spiB.C" where B is the bus number and C is the chipselect.
  - The "caller provides DMA mappings" mechanism now has kerneldoc, for
    DMA drivers that want to be fancy.
  - Hey, the framework init can be subsys_init.  Even though board init
    logic fires earlier, at arch_init ... since the framework init is
    for driver support, and the board init support uses static init.
  - Various additional spec/doc clarifications based on discussions
    with other folk.  It adds a brief "thank you" at the end, for folk
    who've helped nudge this framework into existence.
As I've said before, I think that "protocol tweaking" is the main support
that this driver framework will need to evolve.
From: Mark Underwood <basicmark@yahoo.com>
  Update the SPI framework to remove a potential priority inversion case by
  reverting to kmalloc if the pre-allocated DMA-safe buffer isn't available.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
											
										 
											2006-01-08 13:34:19 -08:00
										 |  |  | { | 
					
						
							|  |  |  | 	struct boardinfo	*bi; | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											2007-07-17 04:04:16 -07:00
										 |  |  | 	mutex_lock(&board_lock); | 
					
						
							| 
									
										
											  
											
												[PATCH] spi: simple SPI framework
This is the core of a small SPI framework, implementing the model of a
queue of messages which complete asynchronously (with thin synchronous
wrappers on top).
  - It's still less than 2KB of ".text" (ARM).  If there's got to be a
    mid-layer for something so simple, that's the right size budget.  :)
  - The guts use board-specific SPI device tables to build the driver
    model tree.  (Hardware probing is rarely an option.)
  - This version of Kconfig includes no drivers.  At this writing there
    are two known master controller drivers (PXA/SSP, OMAP MicroWire)
    and three protocol drivers (CS8415a, ADS7846, DataFlash) with LKML
    mentions of other drivers in development.
  - No userspace API.  There are several implementations to compare.
    Implement them like any other driver, and bind them with sysfs.
The changes from last version posted to LKML (on 11-Nov-2005) are minor,
and include:
  - One bugfix (removes a FIXME), with the visible effect of making device
    names be "spiB.C" where B is the bus number and C is the chipselect.
  - The "caller provides DMA mappings" mechanism now has kerneldoc, for
    DMA drivers that want to be fancy.
  - Hey, the framework init can be subsys_init.  Even though board init
    logic fires earlier, at arch_init ... since the framework init is
    for driver support, and the board init support uses static init.
  - Various additional spec/doc clarifications based on discussions
    with other folk.  It adds a brief "thank you" at the end, for folk
    who've helped nudge this framework into existence.
As I've said before, I think that "protocol tweaking" is the main support
that this driver framework will need to evolve.
From: Mark Underwood <basicmark@yahoo.com>
  Update the SPI framework to remove a potential priority inversion case by
  reverting to kmalloc if the pre-allocated DMA-safe buffer isn't available.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
											
										 
											2006-01-08 13:34:19 -08:00
										 |  |  | 	list_for_each_entry(bi, &board_list, list) { | 
					
						
							|  |  |  | 		struct spi_board_info	*chip = bi->board_info; | 
					
						
							|  |  |  | 		unsigned		n; | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | 		for (n = bi->n_board_info; n > 0; n--, chip++) { | 
					
						
							|  |  |  | 			if (chip->bus_num != master->bus_num) | 
					
						
							|  |  |  | 				continue; | 
					
						
							| 
									
										
										
										
											2007-07-31 00:39:45 -07:00
										 |  |  | 			/* NOTE: this relies on spi_new_device to
 | 
					
						
							|  |  |  | 			 * issue diagnostics when given bogus inputs | 
					
						
							| 
									
										
											  
											
												[PATCH] spi: simple SPI framework
This is the core of a small SPI framework, implementing the model of a
queue of messages which complete asynchronously (with thin synchronous
wrappers on top).
  - It's still less than 2KB of ".text" (ARM).  If there's got to be a
    mid-layer for something so simple, that's the right size budget.  :)
  - The guts use board-specific SPI device tables to build the driver
    model tree.  (Hardware probing is rarely an option.)
  - This version of Kconfig includes no drivers.  At this writing there
    are two known master controller drivers (PXA/SSP, OMAP MicroWire)
    and three protocol drivers (CS8415a, ADS7846, DataFlash) with LKML
    mentions of other drivers in development.
  - No userspace API.  There are several implementations to compare.
    Implement them like any other driver, and bind them with sysfs.
The changes from last version posted to LKML (on 11-Nov-2005) are minor,
and include:
  - One bugfix (removes a FIXME), with the visible effect of making device
    names be "spiB.C" where B is the bus number and C is the chipselect.
  - The "caller provides DMA mappings" mechanism now has kerneldoc, for
    DMA drivers that want to be fancy.
  - Hey, the framework init can be subsys_init.  Even though board init
    logic fires earlier, at arch_init ... since the framework init is
    for driver support, and the board init support uses static init.
  - Various additional spec/doc clarifications based on discussions
    with other folk.  It adds a brief "thank you" at the end, for folk
    who've helped nudge this framework into existence.
As I've said before, I think that "protocol tweaking" is the main support
that this driver framework will need to evolve.
From: Mark Underwood <basicmark@yahoo.com>
  Update the SPI framework to remove a potential priority inversion case by
  reverting to kmalloc if the pre-allocated DMA-safe buffer isn't available.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
											
										 
											2006-01-08 13:34:19 -08:00
										 |  |  | 			 */ | 
					
						
							|  |  |  | 			(void) spi_new_device(master, chip); | 
					
						
							|  |  |  | 		} | 
					
						
							|  |  |  | 	} | 
					
						
							| 
									
										
										
										
											2007-07-17 04:04:16 -07:00
										 |  |  | 	mutex_unlock(&board_lock); | 
					
						
							| 
									
										
											  
											
												[PATCH] spi: simple SPI framework
This is the core of a small SPI framework, implementing the model of a
queue of messages which complete asynchronously (with thin synchronous
wrappers on top).
  - It's still less than 2KB of ".text" (ARM).  If there's got to be a
    mid-layer for something so simple, that's the right size budget.  :)
  - The guts use board-specific SPI device tables to build the driver
    model tree.  (Hardware probing is rarely an option.)
  - This version of Kconfig includes no drivers.  At this writing there
    are two known master controller drivers (PXA/SSP, OMAP MicroWire)
    and three protocol drivers (CS8415a, ADS7846, DataFlash) with LKML
    mentions of other drivers in development.
  - No userspace API.  There are several implementations to compare.
    Implement them like any other driver, and bind them with sysfs.
The changes from last version posted to LKML (on 11-Nov-2005) are minor,
and include:
  - One bugfix (removes a FIXME), with the visible effect of making device
    names be "spiB.C" where B is the bus number and C is the chipselect.
  - The "caller provides DMA mappings" mechanism now has kerneldoc, for
    DMA drivers that want to be fancy.
  - Hey, the framework init can be subsys_init.  Even though board init
    logic fires earlier, at arch_init ... since the framework init is
    for driver support, and the board init support uses static init.
  - Various additional spec/doc clarifications based on discussions
    with other folk.  It adds a brief "thank you" at the end, for folk
    who've helped nudge this framework into existence.
As I've said before, I think that "protocol tweaking" is the main support
that this driver framework will need to evolve.
From: Mark Underwood <basicmark@yahoo.com>
  Update the SPI framework to remove a potential priority inversion case by
  reverting to kmalloc if the pre-allocated DMA-safe buffer isn't available.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
											
										 
											2006-01-08 13:34:19 -08:00
										 |  |  | } | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | /*-------------------------------------------------------------------------*/ | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											2007-10-16 01:27:48 -07:00
										 |  |  | static void spi_master_release(struct device *dev) | 
					
						
							| 
									
										
											  
											
												[PATCH] spi: simple SPI framework
This is the core of a small SPI framework, implementing the model of a
queue of messages which complete asynchronously (with thin synchronous
wrappers on top).
  - It's still less than 2KB of ".text" (ARM).  If there's got to be a
    mid-layer for something so simple, that's the right size budget.  :)
  - The guts use board-specific SPI device tables to build the driver
    model tree.  (Hardware probing is rarely an option.)
  - This version of Kconfig includes no drivers.  At this writing there
    are two known master controller drivers (PXA/SSP, OMAP MicroWire)
    and three protocol drivers (CS8415a, ADS7846, DataFlash) with LKML
    mentions of other drivers in development.
  - No userspace API.  There are several implementations to compare.
    Implement them like any other driver, and bind them with sysfs.
The changes from last version posted to LKML (on 11-Nov-2005) are minor,
and include:
  - One bugfix (removes a FIXME), with the visible effect of making device
    names be "spiB.C" where B is the bus number and C is the chipselect.
  - The "caller provides DMA mappings" mechanism now has kerneldoc, for
    DMA drivers that want to be fancy.
  - Hey, the framework init can be subsys_init.  Even though board init
    logic fires earlier, at arch_init ... since the framework init is
    for driver support, and the board init support uses static init.
  - Various additional spec/doc clarifications based on discussions
    with other folk.  It adds a brief "thank you" at the end, for folk
    who've helped nudge this framework into existence.
As I've said before, I think that "protocol tweaking" is the main support
that this driver framework will need to evolve.
From: Mark Underwood <basicmark@yahoo.com>
  Update the SPI framework to remove a potential priority inversion case by
  reverting to kmalloc if the pre-allocated DMA-safe buffer isn't available.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
											
										 
											2006-01-08 13:34:19 -08:00
										 |  |  | { | 
					
						
							|  |  |  | 	struct spi_master *master; | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											2007-10-16 01:27:48 -07:00
										 |  |  | 	master = container_of(dev, struct spi_master, dev); | 
					
						
							| 
									
										
											  
											
												[PATCH] spi: simple SPI framework
This is the core of a small SPI framework, implementing the model of a
queue of messages which complete asynchronously (with thin synchronous
wrappers on top).
  - It's still less than 2KB of ".text" (ARM).  If there's got to be a
    mid-layer for something so simple, that's the right size budget.  :)
  - The guts use board-specific SPI device tables to build the driver
    model tree.  (Hardware probing is rarely an option.)
  - This version of Kconfig includes no drivers.  At this writing there
    are two known master controller drivers (PXA/SSP, OMAP MicroWire)
    and three protocol drivers (CS8415a, ADS7846, DataFlash) with LKML
    mentions of other drivers in development.
  - No userspace API.  There are several implementations to compare.
    Implement them like any other driver, and bind them with sysfs.
The changes from last version posted to LKML (on 11-Nov-2005) are minor,
and include:
  - One bugfix (removes a FIXME), with the visible effect of making device
    names be "spiB.C" where B is the bus number and C is the chipselect.
  - The "caller provides DMA mappings" mechanism now has kerneldoc, for
    DMA drivers that want to be fancy.
  - Hey, the framework init can be subsys_init.  Even though board init
    logic fires earlier, at arch_init ... since the framework init is
    for driver support, and the board init support uses static init.
  - Various additional spec/doc clarifications based on discussions
    with other folk.  It adds a brief "thank you" at the end, for folk
    who've helped nudge this framework into existence.
As I've said before, I think that "protocol tweaking" is the main support
that this driver framework will need to evolve.
From: Mark Underwood <basicmark@yahoo.com>
  Update the SPI framework to remove a potential priority inversion case by
  reverting to kmalloc if the pre-allocated DMA-safe buffer isn't available.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
											
										 
											2006-01-08 13:34:19 -08:00
										 |  |  | 	kfree(master); | 
					
						
							|  |  |  | } | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | static struct class spi_master_class = { | 
					
						
							|  |  |  | 	.name		= "spi_master", | 
					
						
							|  |  |  | 	.owner		= THIS_MODULE, | 
					
						
							| 
									
										
										
										
											2007-10-16 01:27:48 -07:00
										 |  |  | 	.dev_release	= spi_master_release, | 
					
						
							| 
									
										
											  
											
												[PATCH] spi: simple SPI framework
This is the core of a small SPI framework, implementing the model of a
queue of messages which complete asynchronously (with thin synchronous
wrappers on top).
  - It's still less than 2KB of ".text" (ARM).  If there's got to be a
    mid-layer for something so simple, that's the right size budget.  :)
  - The guts use board-specific SPI device tables to build the driver
    model tree.  (Hardware probing is rarely an option.)
  - This version of Kconfig includes no drivers.  At this writing there
    are two known master controller drivers (PXA/SSP, OMAP MicroWire)
    and three protocol drivers (CS8415a, ADS7846, DataFlash) with LKML
    mentions of other drivers in development.
  - No userspace API.  There are several implementations to compare.
    Implement them like any other driver, and bind them with sysfs.
The changes from last version posted to LKML (on 11-Nov-2005) are minor,
and include:
  - One bugfix (removes a FIXME), with the visible effect of making device
    names be "spiB.C" where B is the bus number and C is the chipselect.
  - The "caller provides DMA mappings" mechanism now has kerneldoc, for
    DMA drivers that want to be fancy.
  - Hey, the framework init can be subsys_init.  Even though board init
    logic fires earlier, at arch_init ... since the framework init is
    for driver support, and the board init support uses static init.
  - Various additional spec/doc clarifications based on discussions
    with other folk.  It adds a brief "thank you" at the end, for folk
    who've helped nudge this framework into existence.
As I've said before, I think that "protocol tweaking" is the main support
that this driver framework will need to evolve.
From: Mark Underwood <basicmark@yahoo.com>
  Update the SPI framework to remove a potential priority inversion case by
  reverting to kmalloc if the pre-allocated DMA-safe buffer isn't available.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
											
										 
											2006-01-08 13:34:19 -08:00
										 |  |  | }; | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | /**
 | 
					
						
							|  |  |  |  * spi_alloc_master - allocate SPI master controller | 
					
						
							|  |  |  |  * @dev: the controller, possibly using the platform_bus | 
					
						
							| 
									
										
										
										
											2007-05-08 00:32:21 -07:00
										 |  |  |  * @size: how much zeroed driver-private data to allocate; the pointer to this | 
					
						
							| 
									
										
										
										
											2007-10-16 01:27:48 -07:00
										 |  |  |  *	memory is in the driver_data field of the returned device, | 
					
						
							| 
									
										
										
										
											2006-01-08 13:34:25 -08:00
										 |  |  |  *	accessible with spi_master_get_devdata(). | 
					
						
							| 
									
										
										
										
											2007-05-08 00:32:21 -07:00
										 |  |  |  * Context: can sleep | 
					
						
							| 
									
										
											  
											
												[PATCH] spi: simple SPI framework
This is the core of a small SPI framework, implementing the model of a
queue of messages which complete asynchronously (with thin synchronous
wrappers on top).
  - It's still less than 2KB of ".text" (ARM).  If there's got to be a
    mid-layer for something so simple, that's the right size budget.  :)
  - The guts use board-specific SPI device tables to build the driver
    model tree.  (Hardware probing is rarely an option.)
  - This version of Kconfig includes no drivers.  At this writing there
    are two known master controller drivers (PXA/SSP, OMAP MicroWire)
    and three protocol drivers (CS8415a, ADS7846, DataFlash) with LKML
    mentions of other drivers in development.
  - No userspace API.  There are several implementations to compare.
    Implement them like any other driver, and bind them with sysfs.
The changes from last version posted to LKML (on 11-Nov-2005) are minor,
and include:
  - One bugfix (removes a FIXME), with the visible effect of making device
    names be "spiB.C" where B is the bus number and C is the chipselect.
  - The "caller provides DMA mappings" mechanism now has kerneldoc, for
    DMA drivers that want to be fancy.
  - Hey, the framework init can be subsys_init.  Even though board init
    logic fires earlier, at arch_init ... since the framework init is
    for driver support, and the board init support uses static init.
  - Various additional spec/doc clarifications based on discussions
    with other folk.  It adds a brief "thank you" at the end, for folk
    who've helped nudge this framework into existence.
As I've said before, I think that "protocol tweaking" is the main support
that this driver framework will need to evolve.
From: Mark Underwood <basicmark@yahoo.com>
  Update the SPI framework to remove a potential priority inversion case by
  reverting to kmalloc if the pre-allocated DMA-safe buffer isn't available.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
											
										 
											2006-01-08 13:34:19 -08:00
										 |  |  |  * | 
					
						
							|  |  |  |  * This call is used only by SPI master controller drivers, which are the | 
					
						
							|  |  |  |  * only ones directly touching chip registers.  It's how they allocate | 
					
						
							| 
									
										
										
										
											2006-05-20 15:00:14 -07:00
										 |  |  |  * an spi_master structure, prior to calling spi_register_master(). | 
					
						
							| 
									
										
											  
											
												[PATCH] spi: simple SPI framework
This is the core of a small SPI framework, implementing the model of a
queue of messages which complete asynchronously (with thin synchronous
wrappers on top).
  - It's still less than 2KB of ".text" (ARM).  If there's got to be a
    mid-layer for something so simple, that's the right size budget.  :)
  - The guts use board-specific SPI device tables to build the driver
    model tree.  (Hardware probing is rarely an option.)
  - This version of Kconfig includes no drivers.  At this writing there
    are two known master controller drivers (PXA/SSP, OMAP MicroWire)
    and three protocol drivers (CS8415a, ADS7846, DataFlash) with LKML
    mentions of other drivers in development.
  - No userspace API.  There are several implementations to compare.
    Implement them like any other driver, and bind them with sysfs.
The changes from last version posted to LKML (on 11-Nov-2005) are minor,
and include:
  - One bugfix (removes a FIXME), with the visible effect of making device
    names be "spiB.C" where B is the bus number and C is the chipselect.
  - The "caller provides DMA mappings" mechanism now has kerneldoc, for
    DMA drivers that want to be fancy.
  - Hey, the framework init can be subsys_init.  Even though board init
    logic fires earlier, at arch_init ... since the framework init is
    for driver support, and the board init support uses static init.
  - Various additional spec/doc clarifications based on discussions
    with other folk.  It adds a brief "thank you" at the end, for folk
    who've helped nudge this framework into existence.
As I've said before, I think that "protocol tweaking" is the main support
that this driver framework will need to evolve.
From: Mark Underwood <basicmark@yahoo.com>
  Update the SPI framework to remove a potential priority inversion case by
  reverting to kmalloc if the pre-allocated DMA-safe buffer isn't available.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
											
										 
											2006-01-08 13:34:19 -08:00
										 |  |  |  * | 
					
						
							|  |  |  |  * This must be called from context that can sleep.  It returns the SPI | 
					
						
							|  |  |  |  * master structure on success, else NULL. | 
					
						
							|  |  |  |  * | 
					
						
							|  |  |  |  * The caller is responsible for assigning the bus number and initializing | 
					
						
							| 
									
										
										
										
											2006-05-20 15:00:14 -07:00
										 |  |  |  * the master's methods before calling spi_register_master(); and (after errors | 
					
						
							| 
									
										
										
										
											2006-01-08 13:34:25 -08:00
										 |  |  |  * adding the device) calling spi_master_put() to prevent a memory leak. | 
					
						
							| 
									
										
											  
											
												[PATCH] spi: simple SPI framework
This is the core of a small SPI framework, implementing the model of a
queue of messages which complete asynchronously (with thin synchronous
wrappers on top).
  - It's still less than 2KB of ".text" (ARM).  If there's got to be a
    mid-layer for something so simple, that's the right size budget.  :)
  - The guts use board-specific SPI device tables to build the driver
    model tree.  (Hardware probing is rarely an option.)
  - This version of Kconfig includes no drivers.  At this writing there
    are two known master controller drivers (PXA/SSP, OMAP MicroWire)
    and three protocol drivers (CS8415a, ADS7846, DataFlash) with LKML
    mentions of other drivers in development.
  - No userspace API.  There are several implementations to compare.
    Implement them like any other driver, and bind them with sysfs.
The changes from last version posted to LKML (on 11-Nov-2005) are minor,
and include:
  - One bugfix (removes a FIXME), with the visible effect of making device
    names be "spiB.C" where B is the bus number and C is the chipselect.
  - The "caller provides DMA mappings" mechanism now has kerneldoc, for
    DMA drivers that want to be fancy.
  - Hey, the framework init can be subsys_init.  Even though board init
    logic fires earlier, at arch_init ... since the framework init is
    for driver support, and the board init support uses static init.
  - Various additional spec/doc clarifications based on discussions
    with other folk.  It adds a brief "thank you" at the end, for folk
    who've helped nudge this framework into existence.
As I've said before, I think that "protocol tweaking" is the main support
that this driver framework will need to evolve.
From: Mark Underwood <basicmark@yahoo.com>
  Update the SPI framework to remove a potential priority inversion case by
  reverting to kmalloc if the pre-allocated DMA-safe buffer isn't available.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
											
										 
											2006-01-08 13:34:19 -08:00
										 |  |  |  */ | 
					
						
							| 
									
										
										
										
											2007-03-26 21:32:23 -08:00
										 |  |  | struct spi_master *spi_alloc_master(struct device *dev, unsigned size) | 
					
						
							| 
									
										
											  
											
												[PATCH] spi: simple SPI framework
This is the core of a small SPI framework, implementing the model of a
queue of messages which complete asynchronously (with thin synchronous
wrappers on top).
  - It's still less than 2KB of ".text" (ARM).  If there's got to be a
    mid-layer for something so simple, that's the right size budget.  :)
  - The guts use board-specific SPI device tables to build the driver
    model tree.  (Hardware probing is rarely an option.)
  - This version of Kconfig includes no drivers.  At this writing there
    are two known master controller drivers (PXA/SSP, OMAP MicroWire)
    and three protocol drivers (CS8415a, ADS7846, DataFlash) with LKML
    mentions of other drivers in development.
  - No userspace API.  There are several implementations to compare.
    Implement them like any other driver, and bind them with sysfs.
The changes from last version posted to LKML (on 11-Nov-2005) are minor,
and include:
  - One bugfix (removes a FIXME), with the visible effect of making device
    names be "spiB.C" where B is the bus number and C is the chipselect.
  - The "caller provides DMA mappings" mechanism now has kerneldoc, for
    DMA drivers that want to be fancy.
  - Hey, the framework init can be subsys_init.  Even though board init
    logic fires earlier, at arch_init ... since the framework init is
    for driver support, and the board init support uses static init.
  - Various additional spec/doc clarifications based on discussions
    with other folk.  It adds a brief "thank you" at the end, for folk
    who've helped nudge this framework into existence.
As I've said before, I think that "protocol tweaking" is the main support
that this driver framework will need to evolve.
From: Mark Underwood <basicmark@yahoo.com>
  Update the SPI framework to remove a potential priority inversion case by
  reverting to kmalloc if the pre-allocated DMA-safe buffer isn't available.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
											
										 
											2006-01-08 13:34:19 -08:00
										 |  |  | { | 
					
						
							|  |  |  | 	struct spi_master	*master; | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											2006-01-08 13:34:25 -08:00
										 |  |  | 	if (!dev) | 
					
						
							|  |  |  | 		return NULL; | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											2006-12-06 20:33:17 -08:00
										 |  |  | 	master = kzalloc(size + sizeof *master, GFP_KERNEL); | 
					
						
							| 
									
										
											  
											
												[PATCH] spi: simple SPI framework
This is the core of a small SPI framework, implementing the model of a
queue of messages which complete asynchronously (with thin synchronous
wrappers on top).
  - It's still less than 2KB of ".text" (ARM).  If there's got to be a
    mid-layer for something so simple, that's the right size budget.  :)
  - The guts use board-specific SPI device tables to build the driver
    model tree.  (Hardware probing is rarely an option.)
  - This version of Kconfig includes no drivers.  At this writing there
    are two known master controller drivers (PXA/SSP, OMAP MicroWire)
    and three protocol drivers (CS8415a, ADS7846, DataFlash) with LKML
    mentions of other drivers in development.
  - No userspace API.  There are several implementations to compare.
    Implement them like any other driver, and bind them with sysfs.
The changes from last version posted to LKML (on 11-Nov-2005) are minor,
and include:
  - One bugfix (removes a FIXME), with the visible effect of making device
    names be "spiB.C" where B is the bus number and C is the chipselect.
  - The "caller provides DMA mappings" mechanism now has kerneldoc, for
    DMA drivers that want to be fancy.
  - Hey, the framework init can be subsys_init.  Even though board init
    logic fires earlier, at arch_init ... since the framework init is
    for driver support, and the board init support uses static init.
  - Various additional spec/doc clarifications based on discussions
    with other folk.  It adds a brief "thank you" at the end, for folk
    who've helped nudge this framework into existence.
As I've said before, I think that "protocol tweaking" is the main support
that this driver framework will need to evolve.
From: Mark Underwood <basicmark@yahoo.com>
  Update the SPI framework to remove a potential priority inversion case by
  reverting to kmalloc if the pre-allocated DMA-safe buffer isn't available.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
											
										 
											2006-01-08 13:34:19 -08:00
										 |  |  | 	if (!master) | 
					
						
							|  |  |  | 		return NULL; | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											2007-10-16 01:27:48 -07:00
										 |  |  | 	device_initialize(&master->dev); | 
					
						
							|  |  |  | 	master->dev.class = &spi_master_class; | 
					
						
							|  |  |  | 	master->dev.parent = get_device(dev); | 
					
						
							| 
									
										
										
										
											2006-01-08 13:34:25 -08:00
										 |  |  | 	spi_master_set_devdata(master, &master[1]); | 
					
						
							| 
									
										
											  
											
												[PATCH] spi: simple SPI framework
This is the core of a small SPI framework, implementing the model of a
queue of messages which complete asynchronously (with thin synchronous
wrappers on top).
  - It's still less than 2KB of ".text" (ARM).  If there's got to be a
    mid-layer for something so simple, that's the right size budget.  :)
  - The guts use board-specific SPI device tables to build the driver
    model tree.  (Hardware probing is rarely an option.)
  - This version of Kconfig includes no drivers.  At this writing there
    are two known master controller drivers (PXA/SSP, OMAP MicroWire)
    and three protocol drivers (CS8415a, ADS7846, DataFlash) with LKML
    mentions of other drivers in development.
  - No userspace API.  There are several implementations to compare.
    Implement them like any other driver, and bind them with sysfs.
The changes from last version posted to LKML (on 11-Nov-2005) are minor,
and include:
  - One bugfix (removes a FIXME), with the visible effect of making device
    names be "spiB.C" where B is the bus number and C is the chipselect.
  - The "caller provides DMA mappings" mechanism now has kerneldoc, for
    DMA drivers that want to be fancy.
  - Hey, the framework init can be subsys_init.  Even though board init
    logic fires earlier, at arch_init ... since the framework init is
    for driver support, and the board init support uses static init.
  - Various additional spec/doc clarifications based on discussions
    with other folk.  It adds a brief "thank you" at the end, for folk
    who've helped nudge this framework into existence.
As I've said before, I think that "protocol tweaking" is the main support
that this driver framework will need to evolve.
From: Mark Underwood <basicmark@yahoo.com>
  Update the SPI framework to remove a potential priority inversion case by
  reverting to kmalloc if the pre-allocated DMA-safe buffer isn't available.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
											
										 
											2006-01-08 13:34:19 -08:00
										 |  |  | 
 | 
					
						
							|  |  |  | 	return master; | 
					
						
							|  |  |  | } | 
					
						
							|  |  |  | EXPORT_SYMBOL_GPL(spi_alloc_master); | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | /**
 | 
					
						
							|  |  |  |  * spi_register_master - register SPI master controller | 
					
						
							|  |  |  |  * @master: initialized master, originally from spi_alloc_master() | 
					
						
							| 
									
										
										
										
											2007-05-08 00:32:21 -07:00
										 |  |  |  * Context: can sleep | 
					
						
							| 
									
										
											  
											
												[PATCH] spi: simple SPI framework
This is the core of a small SPI framework, implementing the model of a
queue of messages which complete asynchronously (with thin synchronous
wrappers on top).
  - It's still less than 2KB of ".text" (ARM).  If there's got to be a
    mid-layer for something so simple, that's the right size budget.  :)
  - The guts use board-specific SPI device tables to build the driver
    model tree.  (Hardware probing is rarely an option.)
  - This version of Kconfig includes no drivers.  At this writing there
    are two known master controller drivers (PXA/SSP, OMAP MicroWire)
    and three protocol drivers (CS8415a, ADS7846, DataFlash) with LKML
    mentions of other drivers in development.
  - No userspace API.  There are several implementations to compare.
    Implement them like any other driver, and bind them with sysfs.
The changes from last version posted to LKML (on 11-Nov-2005) are minor,
and include:
  - One bugfix (removes a FIXME), with the visible effect of making device
    names be "spiB.C" where B is the bus number and C is the chipselect.
  - The "caller provides DMA mappings" mechanism now has kerneldoc, for
    DMA drivers that want to be fancy.
  - Hey, the framework init can be subsys_init.  Even though board init
    logic fires earlier, at arch_init ... since the framework init is
    for driver support, and the board init support uses static init.
  - Various additional spec/doc clarifications based on discussions
    with other folk.  It adds a brief "thank you" at the end, for folk
    who've helped nudge this framework into existence.
As I've said before, I think that "protocol tweaking" is the main support
that this driver framework will need to evolve.
From: Mark Underwood <basicmark@yahoo.com>
  Update the SPI framework to remove a potential priority inversion case by
  reverting to kmalloc if the pre-allocated DMA-safe buffer isn't available.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
											
										 
											2006-01-08 13:34:19 -08:00
										 |  |  |  * | 
					
						
							|  |  |  |  * SPI master controllers connect to their drivers using some non-SPI bus, | 
					
						
							|  |  |  |  * such as the platform bus.  The final stage of probe() in that code | 
					
						
							|  |  |  |  * includes calling spi_register_master() to hook up to this SPI bus glue. | 
					
						
							|  |  |  |  * | 
					
						
							|  |  |  |  * SPI controllers use board specific (often SOC specific) bus numbers, | 
					
						
							|  |  |  |  * and board-specific addressing for SPI devices combines those numbers | 
					
						
							|  |  |  |  * with chip select numbers.  Since SPI does not directly support dynamic | 
					
						
							|  |  |  |  * device identification, boards need configuration tables telling which | 
					
						
							|  |  |  |  * chip is at which address. | 
					
						
							|  |  |  |  * | 
					
						
							|  |  |  |  * This must be called from context that can sleep.  It returns zero on | 
					
						
							|  |  |  |  * success, else a negative error code (dropping the master's refcount). | 
					
						
							| 
									
										
										
										
											2006-01-08 13:34:25 -08:00
										 |  |  |  * After a successful return, the caller is responsible for calling | 
					
						
							|  |  |  |  * spi_unregister_master(). | 
					
						
							| 
									
										
											  
											
												[PATCH] spi: simple SPI framework
This is the core of a small SPI framework, implementing the model of a
queue of messages which complete asynchronously (with thin synchronous
wrappers on top).
  - It's still less than 2KB of ".text" (ARM).  If there's got to be a
    mid-layer for something so simple, that's the right size budget.  :)
  - The guts use board-specific SPI device tables to build the driver
    model tree.  (Hardware probing is rarely an option.)
  - This version of Kconfig includes no drivers.  At this writing there
    are two known master controller drivers (PXA/SSP, OMAP MicroWire)
    and three protocol drivers (CS8415a, ADS7846, DataFlash) with LKML
    mentions of other drivers in development.
  - No userspace API.  There are several implementations to compare.
    Implement them like any other driver, and bind them with sysfs.
The changes from last version posted to LKML (on 11-Nov-2005) are minor,
and include:
  - One bugfix (removes a FIXME), with the visible effect of making device
    names be "spiB.C" where B is the bus number and C is the chipselect.
  - The "caller provides DMA mappings" mechanism now has kerneldoc, for
    DMA drivers that want to be fancy.
  - Hey, the framework init can be subsys_init.  Even though board init
    logic fires earlier, at arch_init ... since the framework init is
    for driver support, and the board init support uses static init.
  - Various additional spec/doc clarifications based on discussions
    with other folk.  It adds a brief "thank you" at the end, for folk
    who've helped nudge this framework into existence.
As I've said before, I think that "protocol tweaking" is the main support
that this driver framework will need to evolve.
From: Mark Underwood <basicmark@yahoo.com>
  Update the SPI framework to remove a potential priority inversion case by
  reverting to kmalloc if the pre-allocated DMA-safe buffer isn't available.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
											
										 
											2006-01-08 13:34:19 -08:00
										 |  |  |  */ | 
					
						
							| 
									
										
										
										
											2007-03-26 21:32:23 -08:00
										 |  |  | int spi_register_master(struct spi_master *master) | 
					
						
							| 
									
										
											  
											
												[PATCH] spi: simple SPI framework
This is the core of a small SPI framework, implementing the model of a
queue of messages which complete asynchronously (with thin synchronous
wrappers on top).
  - It's still less than 2KB of ".text" (ARM).  If there's got to be a
    mid-layer for something so simple, that's the right size budget.  :)
  - The guts use board-specific SPI device tables to build the driver
    model tree.  (Hardware probing is rarely an option.)
  - This version of Kconfig includes no drivers.  At this writing there
    are two known master controller drivers (PXA/SSP, OMAP MicroWire)
    and three protocol drivers (CS8415a, ADS7846, DataFlash) with LKML
    mentions of other drivers in development.
  - No userspace API.  There are several implementations to compare.
    Implement them like any other driver, and bind them with sysfs.
The changes from last version posted to LKML (on 11-Nov-2005) are minor,
and include:
  - One bugfix (removes a FIXME), with the visible effect of making device
    names be "spiB.C" where B is the bus number and C is the chipselect.
  - The "caller provides DMA mappings" mechanism now has kerneldoc, for
    DMA drivers that want to be fancy.
  - Hey, the framework init can be subsys_init.  Even though board init
    logic fires earlier, at arch_init ... since the framework init is
    for driver support, and the board init support uses static init.
  - Various additional spec/doc clarifications based on discussions
    with other folk.  It adds a brief "thank you" at the end, for folk
    who've helped nudge this framework into existence.
As I've said before, I think that "protocol tweaking" is the main support
that this driver framework will need to evolve.
From: Mark Underwood <basicmark@yahoo.com>
  Update the SPI framework to remove a potential priority inversion case by
  reverting to kmalloc if the pre-allocated DMA-safe buffer isn't available.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
											
										 
											2006-01-08 13:34:19 -08:00
										 |  |  | { | 
					
						
							| 
									
										
										
										
											2007-06-03 13:50:40 -07:00
										 |  |  | 	static atomic_t		dyn_bus_id = ATOMIC_INIT((1<<15) - 1); | 
					
						
							| 
									
										
										
										
											2007-10-16 01:27:48 -07:00
										 |  |  | 	struct device		*dev = master->dev.parent; | 
					
						
							| 
									
										
											  
											
												[PATCH] spi: simple SPI framework
This is the core of a small SPI framework, implementing the model of a
queue of messages which complete asynchronously (with thin synchronous
wrappers on top).
  - It's still less than 2KB of ".text" (ARM).  If there's got to be a
    mid-layer for something so simple, that's the right size budget.  :)
  - The guts use board-specific SPI device tables to build the driver
    model tree.  (Hardware probing is rarely an option.)
  - This version of Kconfig includes no drivers.  At this writing there
    are two known master controller drivers (PXA/SSP, OMAP MicroWire)
    and three protocol drivers (CS8415a, ADS7846, DataFlash) with LKML
    mentions of other drivers in development.
  - No userspace API.  There are several implementations to compare.
    Implement them like any other driver, and bind them with sysfs.
The changes from last version posted to LKML (on 11-Nov-2005) are minor,
and include:
  - One bugfix (removes a FIXME), with the visible effect of making device
    names be "spiB.C" where B is the bus number and C is the chipselect.
  - The "caller provides DMA mappings" mechanism now has kerneldoc, for
    DMA drivers that want to be fancy.
  - Hey, the framework init can be subsys_init.  Even though board init
    logic fires earlier, at arch_init ... since the framework init is
    for driver support, and the board init support uses static init.
  - Various additional spec/doc clarifications based on discussions
    with other folk.  It adds a brief "thank you" at the end, for folk
    who've helped nudge this framework into existence.
As I've said before, I think that "protocol tweaking" is the main support
that this driver framework will need to evolve.
From: Mark Underwood <basicmark@yahoo.com>
  Update the SPI framework to remove a potential priority inversion case by
  reverting to kmalloc if the pre-allocated DMA-safe buffer isn't available.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
											
										 
											2006-01-08 13:34:19 -08:00
										 |  |  | 	int			status = -ENODEV; | 
					
						
							|  |  |  | 	int			dynamic = 0; | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											2006-01-08 13:34:25 -08:00
										 |  |  | 	if (!dev) | 
					
						
							|  |  |  | 		return -ENODEV; | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											2007-07-31 00:39:45 -07:00
										 |  |  | 	/* even if it's just one always-selected device, there must
 | 
					
						
							|  |  |  | 	 * be at least one chipselect | 
					
						
							|  |  |  | 	 */ | 
					
						
							|  |  |  | 	if (master->num_chipselect == 0) | 
					
						
							|  |  |  | 		return -EINVAL; | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
											  
											
												[PATCH] spi: simple SPI framework
This is the core of a small SPI framework, implementing the model of a
queue of messages which complete asynchronously (with thin synchronous
wrappers on top).
  - It's still less than 2KB of ".text" (ARM).  If there's got to be a
    mid-layer for something so simple, that's the right size budget.  :)
  - The guts use board-specific SPI device tables to build the driver
    model tree.  (Hardware probing is rarely an option.)
  - This version of Kconfig includes no drivers.  At this writing there
    are two known master controller drivers (PXA/SSP, OMAP MicroWire)
    and three protocol drivers (CS8415a, ADS7846, DataFlash) with LKML
    mentions of other drivers in development.
  - No userspace API.  There are several implementations to compare.
    Implement them like any other driver, and bind them with sysfs.
The changes from last version posted to LKML (on 11-Nov-2005) are minor,
and include:
  - One bugfix (removes a FIXME), with the visible effect of making device
    names be "spiB.C" where B is the bus number and C is the chipselect.
  - The "caller provides DMA mappings" mechanism now has kerneldoc, for
    DMA drivers that want to be fancy.
  - Hey, the framework init can be subsys_init.  Even though board init
    logic fires earlier, at arch_init ... since the framework init is
    for driver support, and the board init support uses static init.
  - Various additional spec/doc clarifications based on discussions
    with other folk.  It adds a brief "thank you" at the end, for folk
    who've helped nudge this framework into existence.
As I've said before, I think that "protocol tweaking" is the main support
that this driver framework will need to evolve.
From: Mark Underwood <basicmark@yahoo.com>
  Update the SPI framework to remove a potential priority inversion case by
  reverting to kmalloc if the pre-allocated DMA-safe buffer isn't available.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
											
										 
											2006-01-08 13:34:19 -08:00
										 |  |  | 	/* convention:  dynamically assigned bus IDs count down from the max */ | 
					
						
							| 
									
										
										
										
											2006-04-03 15:49:04 -07:00
										 |  |  | 	if (master->bus_num < 0) { | 
					
						
							| 
									
										
										
										
											2007-07-31 00:39:45 -07:00
										 |  |  | 		/* FIXME switch to an IDR based scheme, something like
 | 
					
						
							|  |  |  | 		 * I2C now uses, so we can't run out of "dynamic" IDs | 
					
						
							|  |  |  | 		 */ | 
					
						
							| 
									
										
											  
											
												[PATCH] spi: simple SPI framework
This is the core of a small SPI framework, implementing the model of a
queue of messages which complete asynchronously (with thin synchronous
wrappers on top).
  - It's still less than 2KB of ".text" (ARM).  If there's got to be a
    mid-layer for something so simple, that's the right size budget.  :)
  - The guts use board-specific SPI device tables to build the driver
    model tree.  (Hardware probing is rarely an option.)
  - This version of Kconfig includes no drivers.  At this writing there
    are two known master controller drivers (PXA/SSP, OMAP MicroWire)
    and three protocol drivers (CS8415a, ADS7846, DataFlash) with LKML
    mentions of other drivers in development.
  - No userspace API.  There are several implementations to compare.
    Implement them like any other driver, and bind them with sysfs.
The changes from last version posted to LKML (on 11-Nov-2005) are minor,
and include:
  - One bugfix (removes a FIXME), with the visible effect of making device
    names be "spiB.C" where B is the bus number and C is the chipselect.
  - The "caller provides DMA mappings" mechanism now has kerneldoc, for
    DMA drivers that want to be fancy.
  - Hey, the framework init can be subsys_init.  Even though board init
    logic fires earlier, at arch_init ... since the framework init is
    for driver support, and the board init support uses static init.
  - Various additional spec/doc clarifications based on discussions
    with other folk.  It adds a brief "thank you" at the end, for folk
    who've helped nudge this framework into existence.
As I've said before, I think that "protocol tweaking" is the main support
that this driver framework will need to evolve.
From: Mark Underwood <basicmark@yahoo.com>
  Update the SPI framework to remove a potential priority inversion case by
  reverting to kmalloc if the pre-allocated DMA-safe buffer isn't available.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
											
										 
											2006-01-08 13:34:19 -08:00
										 |  |  | 		master->bus_num = atomic_dec_return(&dyn_bus_id); | 
					
						
							| 
									
										
										
										
											2006-01-08 13:34:23 -08:00
										 |  |  | 		dynamic = 1; | 
					
						
							| 
									
										
											  
											
												[PATCH] spi: simple SPI framework
This is the core of a small SPI framework, implementing the model of a
queue of messages which complete asynchronously (with thin synchronous
wrappers on top).
  - It's still less than 2KB of ".text" (ARM).  If there's got to be a
    mid-layer for something so simple, that's the right size budget.  :)
  - The guts use board-specific SPI device tables to build the driver
    model tree.  (Hardware probing is rarely an option.)
  - This version of Kconfig includes no drivers.  At this writing there
    are two known master controller drivers (PXA/SSP, OMAP MicroWire)
    and three protocol drivers (CS8415a, ADS7846, DataFlash) with LKML
    mentions of other drivers in development.
  - No userspace API.  There are several implementations to compare.
    Implement them like any other driver, and bind them with sysfs.
The changes from last version posted to LKML (on 11-Nov-2005) are minor,
and include:
  - One bugfix (removes a FIXME), with the visible effect of making device
    names be "spiB.C" where B is the bus number and C is the chipselect.
  - The "caller provides DMA mappings" mechanism now has kerneldoc, for
    DMA drivers that want to be fancy.
  - Hey, the framework init can be subsys_init.  Even though board init
    logic fires earlier, at arch_init ... since the framework init is
    for driver support, and the board init support uses static init.
  - Various additional spec/doc clarifications based on discussions
    with other folk.  It adds a brief "thank you" at the end, for folk
    who've helped nudge this framework into existence.
As I've said before, I think that "protocol tweaking" is the main support
that this driver framework will need to evolve.
From: Mark Underwood <basicmark@yahoo.com>
  Update the SPI framework to remove a potential priority inversion case by
  reverting to kmalloc if the pre-allocated DMA-safe buffer isn't available.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
											
										 
											2006-01-08 13:34:19 -08:00
										 |  |  | 	} | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | 	/* register the device, then userspace will see it.
 | 
					
						
							|  |  |  | 	 * registration fails if the bus ID is in use. | 
					
						
							|  |  |  | 	 */ | 
					
						
							| 
									
										
										
										
											2009-01-06 10:44:37 -08:00
										 |  |  | 	dev_set_name(&master->dev, "spi%u", master->bus_num); | 
					
						
							| 
									
										
										
										
											2007-10-16 01:27:48 -07:00
										 |  |  | 	status = device_add(&master->dev); | 
					
						
							| 
									
										
										
										
											2006-01-08 13:34:23 -08:00
										 |  |  | 	if (status < 0) | 
					
						
							| 
									
										
											  
											
												[PATCH] spi: simple SPI framework
This is the core of a small SPI framework, implementing the model of a
queue of messages which complete asynchronously (with thin synchronous
wrappers on top).
  - It's still less than 2KB of ".text" (ARM).  If there's got to be a
    mid-layer for something so simple, that's the right size budget.  :)
  - The guts use board-specific SPI device tables to build the driver
    model tree.  (Hardware probing is rarely an option.)
  - This version of Kconfig includes no drivers.  At this writing there
    are two known master controller drivers (PXA/SSP, OMAP MicroWire)
    and three protocol drivers (CS8415a, ADS7846, DataFlash) with LKML
    mentions of other drivers in development.
  - No userspace API.  There are several implementations to compare.
    Implement them like any other driver, and bind them with sysfs.
The changes from last version posted to LKML (on 11-Nov-2005) are minor,
and include:
  - One bugfix (removes a FIXME), with the visible effect of making device
    names be "spiB.C" where B is the bus number and C is the chipselect.
  - The "caller provides DMA mappings" mechanism now has kerneldoc, for
    DMA drivers that want to be fancy.
  - Hey, the framework init can be subsys_init.  Even though board init
    logic fires earlier, at arch_init ... since the framework init is
    for driver support, and the board init support uses static init.
  - Various additional spec/doc clarifications based on discussions
    with other folk.  It adds a brief "thank you" at the end, for folk
    who've helped nudge this framework into existence.
As I've said before, I think that "protocol tweaking" is the main support
that this driver framework will need to evolve.
From: Mark Underwood <basicmark@yahoo.com>
  Update the SPI framework to remove a potential priority inversion case by
  reverting to kmalloc if the pre-allocated DMA-safe buffer isn't available.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
											
										 
											2006-01-08 13:34:19 -08:00
										 |  |  | 		goto done; | 
					
						
							| 
									
										
										
										
											2009-01-06 10:44:37 -08:00
										 |  |  | 	dev_dbg(dev, "registered master %s%s\n", dev_name(&master->dev), | 
					
						
							| 
									
										
											  
											
												[PATCH] spi: simple SPI framework
This is the core of a small SPI framework, implementing the model of a
queue of messages which complete asynchronously (with thin synchronous
wrappers on top).
  - It's still less than 2KB of ".text" (ARM).  If there's got to be a
    mid-layer for something so simple, that's the right size budget.  :)
  - The guts use board-specific SPI device tables to build the driver
    model tree.  (Hardware probing is rarely an option.)
  - This version of Kconfig includes no drivers.  At this writing there
    are two known master controller drivers (PXA/SSP, OMAP MicroWire)
    and three protocol drivers (CS8415a, ADS7846, DataFlash) with LKML
    mentions of other drivers in development.
  - No userspace API.  There are several implementations to compare.
    Implement them like any other driver, and bind them with sysfs.
The changes from last version posted to LKML (on 11-Nov-2005) are minor,
and include:
  - One bugfix (removes a FIXME), with the visible effect of making device
    names be "spiB.C" where B is the bus number and C is the chipselect.
  - The "caller provides DMA mappings" mechanism now has kerneldoc, for
    DMA drivers that want to be fancy.
  - Hey, the framework init can be subsys_init.  Even though board init
    logic fires earlier, at arch_init ... since the framework init is
    for driver support, and the board init support uses static init.
  - Various additional spec/doc clarifications based on discussions
    with other folk.  It adds a brief "thank you" at the end, for folk
    who've helped nudge this framework into existence.
As I've said before, I think that "protocol tweaking" is the main support
that this driver framework will need to evolve.
From: Mark Underwood <basicmark@yahoo.com>
  Update the SPI framework to remove a potential priority inversion case by
  reverting to kmalloc if the pre-allocated DMA-safe buffer isn't available.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
											
										 
											2006-01-08 13:34:19 -08:00
										 |  |  | 			dynamic ? " (dynamic)" : ""); | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | 	/* populate children from any spi device tables */ | 
					
						
							|  |  |  | 	scan_boardinfo(master); | 
					
						
							|  |  |  | 	status = 0; | 
					
						
							|  |  |  | done: | 
					
						
							|  |  |  | 	return status; | 
					
						
							|  |  |  | } | 
					
						
							|  |  |  | EXPORT_SYMBOL_GPL(spi_register_master); | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											2007-11-14 16:59:22 -08:00
										 |  |  | static int __unregister(struct device *dev, void *master_dev) | 
					
						
							| 
									
										
											  
											
												[PATCH] spi: simple SPI framework
This is the core of a small SPI framework, implementing the model of a
queue of messages which complete asynchronously (with thin synchronous
wrappers on top).
  - It's still less than 2KB of ".text" (ARM).  If there's got to be a
    mid-layer for something so simple, that's the right size budget.  :)
  - The guts use board-specific SPI device tables to build the driver
    model tree.  (Hardware probing is rarely an option.)
  - This version of Kconfig includes no drivers.  At this writing there
    are two known master controller drivers (PXA/SSP, OMAP MicroWire)
    and three protocol drivers (CS8415a, ADS7846, DataFlash) with LKML
    mentions of other drivers in development.
  - No userspace API.  There are several implementations to compare.
    Implement them like any other driver, and bind them with sysfs.
The changes from last version posted to LKML (on 11-Nov-2005) are minor,
and include:
  - One bugfix (removes a FIXME), with the visible effect of making device
    names be "spiB.C" where B is the bus number and C is the chipselect.
  - The "caller provides DMA mappings" mechanism now has kerneldoc, for
    DMA drivers that want to be fancy.
  - Hey, the framework init can be subsys_init.  Even though board init
    logic fires earlier, at arch_init ... since the framework init is
    for driver support, and the board init support uses static init.
  - Various additional spec/doc clarifications based on discussions
    with other folk.  It adds a brief "thank you" at the end, for folk
    who've helped nudge this framework into existence.
As I've said before, I think that "protocol tweaking" is the main support
that this driver framework will need to evolve.
From: Mark Underwood <basicmark@yahoo.com>
  Update the SPI framework to remove a potential priority inversion case by
  reverting to kmalloc if the pre-allocated DMA-safe buffer isn't available.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
											
										 
											2006-01-08 13:34:19 -08:00
										 |  |  | { | 
					
						
							|  |  |  | 	/* note: before about 2.6.14-rc1 this would corrupt memory: */ | 
					
						
							| 
									
										
										
										
											2007-11-14 16:59:22 -08:00
										 |  |  | 	if (dev != master_dev) | 
					
						
							|  |  |  | 		spi_unregister_device(to_spi_device(dev)); | 
					
						
							| 
									
										
											  
											
												[PATCH] spi: simple SPI framework
This is the core of a small SPI framework, implementing the model of a
queue of messages which complete asynchronously (with thin synchronous
wrappers on top).
  - It's still less than 2KB of ".text" (ARM).  If there's got to be a
    mid-layer for something so simple, that's the right size budget.  :)
  - The guts use board-specific SPI device tables to build the driver
    model tree.  (Hardware probing is rarely an option.)
  - This version of Kconfig includes no drivers.  At this writing there
    are two known master controller drivers (PXA/SSP, OMAP MicroWire)
    and three protocol drivers (CS8415a, ADS7846, DataFlash) with LKML
    mentions of other drivers in development.
  - No userspace API.  There are several implementations to compare.
    Implement them like any other driver, and bind them with sysfs.
The changes from last version posted to LKML (on 11-Nov-2005) are minor,
and include:
  - One bugfix (removes a FIXME), with the visible effect of making device
    names be "spiB.C" where B is the bus number and C is the chipselect.
  - The "caller provides DMA mappings" mechanism now has kerneldoc, for
    DMA drivers that want to be fancy.
  - Hey, the framework init can be subsys_init.  Even though board init
    logic fires earlier, at arch_init ... since the framework init is
    for driver support, and the board init support uses static init.
  - Various additional spec/doc clarifications based on discussions
    with other folk.  It adds a brief "thank you" at the end, for folk
    who've helped nudge this framework into existence.
As I've said before, I think that "protocol tweaking" is the main support
that this driver framework will need to evolve.
From: Mark Underwood <basicmark@yahoo.com>
  Update the SPI framework to remove a potential priority inversion case by
  reverting to kmalloc if the pre-allocated DMA-safe buffer isn't available.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
											
										 
											2006-01-08 13:34:19 -08:00
										 |  |  | 	return 0; | 
					
						
							|  |  |  | } | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | /**
 | 
					
						
							|  |  |  |  * spi_unregister_master - unregister SPI master controller | 
					
						
							|  |  |  |  * @master: the master being unregistered | 
					
						
							| 
									
										
										
										
											2007-05-08 00:32:21 -07:00
										 |  |  |  * Context: can sleep | 
					
						
							| 
									
										
											  
											
												[PATCH] spi: simple SPI framework
This is the core of a small SPI framework, implementing the model of a
queue of messages which complete asynchronously (with thin synchronous
wrappers on top).
  - It's still less than 2KB of ".text" (ARM).  If there's got to be a
    mid-layer for something so simple, that's the right size budget.  :)
  - The guts use board-specific SPI device tables to build the driver
    model tree.  (Hardware probing is rarely an option.)
  - This version of Kconfig includes no drivers.  At this writing there
    are two known master controller drivers (PXA/SSP, OMAP MicroWire)
    and three protocol drivers (CS8415a, ADS7846, DataFlash) with LKML
    mentions of other drivers in development.
  - No userspace API.  There are several implementations to compare.
    Implement them like any other driver, and bind them with sysfs.
The changes from last version posted to LKML (on 11-Nov-2005) are minor,
and include:
  - One bugfix (removes a FIXME), with the visible effect of making device
    names be "spiB.C" where B is the bus number and C is the chipselect.
  - The "caller provides DMA mappings" mechanism now has kerneldoc, for
    DMA drivers that want to be fancy.
  - Hey, the framework init can be subsys_init.  Even though board init
    logic fires earlier, at arch_init ... since the framework init is
    for driver support, and the board init support uses static init.
  - Various additional spec/doc clarifications based on discussions
    with other folk.  It adds a brief "thank you" at the end, for folk
    who've helped nudge this framework into existence.
As I've said before, I think that "protocol tweaking" is the main support
that this driver framework will need to evolve.
From: Mark Underwood <basicmark@yahoo.com>
  Update the SPI framework to remove a potential priority inversion case by
  reverting to kmalloc if the pre-allocated DMA-safe buffer isn't available.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
											
										 
											2006-01-08 13:34:19 -08:00
										 |  |  |  * | 
					
						
							|  |  |  |  * This call is used only by SPI master controller drivers, which are the | 
					
						
							|  |  |  |  * only ones directly touching chip registers. | 
					
						
							|  |  |  |  * | 
					
						
							|  |  |  |  * This must be called from context that can sleep. | 
					
						
							|  |  |  |  */ | 
					
						
							|  |  |  | void spi_unregister_master(struct spi_master *master) | 
					
						
							|  |  |  | { | 
					
						
							| 
									
										
										
										
											2006-12-06 20:35:35 -08:00
										 |  |  | 	int dummy; | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											2007-11-14 16:59:22 -08:00
										 |  |  | 	dummy = device_for_each_child(master->dev.parent, &master->dev, | 
					
						
							|  |  |  | 					__unregister); | 
					
						
							| 
									
										
										
										
											2007-10-16 01:27:48 -07:00
										 |  |  | 	device_unregister(&master->dev); | 
					
						
							| 
									
										
											  
											
												[PATCH] spi: simple SPI framework
This is the core of a small SPI framework, implementing the model of a
queue of messages which complete asynchronously (with thin synchronous
wrappers on top).
  - It's still less than 2KB of ".text" (ARM).  If there's got to be a
    mid-layer for something so simple, that's the right size budget.  :)
  - The guts use board-specific SPI device tables to build the driver
    model tree.  (Hardware probing is rarely an option.)
  - This version of Kconfig includes no drivers.  At this writing there
    are two known master controller drivers (PXA/SSP, OMAP MicroWire)
    and three protocol drivers (CS8415a, ADS7846, DataFlash) with LKML
    mentions of other drivers in development.
  - No userspace API.  There are several implementations to compare.
    Implement them like any other driver, and bind them with sysfs.
The changes from last version posted to LKML (on 11-Nov-2005) are minor,
and include:
  - One bugfix (removes a FIXME), with the visible effect of making device
    names be "spiB.C" where B is the bus number and C is the chipselect.
  - The "caller provides DMA mappings" mechanism now has kerneldoc, for
    DMA drivers that want to be fancy.
  - Hey, the framework init can be subsys_init.  Even though board init
    logic fires earlier, at arch_init ... since the framework init is
    for driver support, and the board init support uses static init.
  - Various additional spec/doc clarifications based on discussions
    with other folk.  It adds a brief "thank you" at the end, for folk
    who've helped nudge this framework into existence.
As I've said before, I think that "protocol tweaking" is the main support
that this driver framework will need to evolve.
From: Mark Underwood <basicmark@yahoo.com>
  Update the SPI framework to remove a potential priority inversion case by
  reverting to kmalloc if the pre-allocated DMA-safe buffer isn't available.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
											
										 
											2006-01-08 13:34:19 -08:00
										 |  |  | } | 
					
						
							|  |  |  | EXPORT_SYMBOL_GPL(spi_unregister_master); | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											2008-01-22 15:14:18 +08:00
										 |  |  | static int __spi_master_match(struct device *dev, void *data) | 
					
						
							|  |  |  | { | 
					
						
							|  |  |  | 	struct spi_master *m; | 
					
						
							|  |  |  | 	u16 *bus_num = data; | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | 	m = container_of(dev, struct spi_master, dev); | 
					
						
							|  |  |  | 	return m->bus_num == *bus_num; | 
					
						
							|  |  |  | } | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
											  
											
												[PATCH] spi: simple SPI framework
This is the core of a small SPI framework, implementing the model of a
queue of messages which complete asynchronously (with thin synchronous
wrappers on top).
  - It's still less than 2KB of ".text" (ARM).  If there's got to be a
    mid-layer for something so simple, that's the right size budget.  :)
  - The guts use board-specific SPI device tables to build the driver
    model tree.  (Hardware probing is rarely an option.)
  - This version of Kconfig includes no drivers.  At this writing there
    are two known master controller drivers (PXA/SSP, OMAP MicroWire)
    and three protocol drivers (CS8415a, ADS7846, DataFlash) with LKML
    mentions of other drivers in development.
  - No userspace API.  There are several implementations to compare.
    Implement them like any other driver, and bind them with sysfs.
The changes from last version posted to LKML (on 11-Nov-2005) are minor,
and include:
  - One bugfix (removes a FIXME), with the visible effect of making device
    names be "spiB.C" where B is the bus number and C is the chipselect.
  - The "caller provides DMA mappings" mechanism now has kerneldoc, for
    DMA drivers that want to be fancy.
  - Hey, the framework init can be subsys_init.  Even though board init
    logic fires earlier, at arch_init ... since the framework init is
    for driver support, and the board init support uses static init.
  - Various additional spec/doc clarifications based on discussions
    with other folk.  It adds a brief "thank you" at the end, for folk
    who've helped nudge this framework into existence.
As I've said before, I think that "protocol tweaking" is the main support
that this driver framework will need to evolve.
From: Mark Underwood <basicmark@yahoo.com>
  Update the SPI framework to remove a potential priority inversion case by
  reverting to kmalloc if the pre-allocated DMA-safe buffer isn't available.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
											
										 
											2006-01-08 13:34:19 -08:00
										 |  |  | /**
 | 
					
						
							|  |  |  |  * spi_busnum_to_master - look up master associated with bus_num | 
					
						
							|  |  |  |  * @bus_num: the master's bus number | 
					
						
							| 
									
										
										
										
											2007-05-08 00:32:21 -07:00
										 |  |  |  * Context: can sleep | 
					
						
							| 
									
										
											  
											
												[PATCH] spi: simple SPI framework
This is the core of a small SPI framework, implementing the model of a
queue of messages which complete asynchronously (with thin synchronous
wrappers on top).
  - It's still less than 2KB of ".text" (ARM).  If there's got to be a
    mid-layer for something so simple, that's the right size budget.  :)
  - The guts use board-specific SPI device tables to build the driver
    model tree.  (Hardware probing is rarely an option.)
  - This version of Kconfig includes no drivers.  At this writing there
    are two known master controller drivers (PXA/SSP, OMAP MicroWire)
    and three protocol drivers (CS8415a, ADS7846, DataFlash) with LKML
    mentions of other drivers in development.
  - No userspace API.  There are several implementations to compare.
    Implement them like any other driver, and bind them with sysfs.
The changes from last version posted to LKML (on 11-Nov-2005) are minor,
and include:
  - One bugfix (removes a FIXME), with the visible effect of making device
    names be "spiB.C" where B is the bus number and C is the chipselect.
  - The "caller provides DMA mappings" mechanism now has kerneldoc, for
    DMA drivers that want to be fancy.
  - Hey, the framework init can be subsys_init.  Even though board init
    logic fires earlier, at arch_init ... since the framework init is
    for driver support, and the board init support uses static init.
  - Various additional spec/doc clarifications based on discussions
    with other folk.  It adds a brief "thank you" at the end, for folk
    who've helped nudge this framework into existence.
As I've said before, I think that "protocol tweaking" is the main support
that this driver framework will need to evolve.
From: Mark Underwood <basicmark@yahoo.com>
  Update the SPI framework to remove a potential priority inversion case by
  reverting to kmalloc if the pre-allocated DMA-safe buffer isn't available.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
											
										 
											2006-01-08 13:34:19 -08:00
										 |  |  |  * | 
					
						
							|  |  |  |  * This call may be used with devices that are registered after | 
					
						
							|  |  |  |  * arch init time.  It returns a refcounted pointer to the relevant | 
					
						
							|  |  |  |  * spi_master (which the caller must release), or NULL if there is | 
					
						
							|  |  |  |  * no such master registered. | 
					
						
							|  |  |  |  */ | 
					
						
							|  |  |  | struct spi_master *spi_busnum_to_master(u16 bus_num) | 
					
						
							|  |  |  | { | 
					
						
							| 
									
										
										
										
											2007-10-16 01:27:48 -07:00
										 |  |  | 	struct device		*dev; | 
					
						
							| 
									
										
										
										
											2007-01-26 00:56:54 -08:00
										 |  |  | 	struct spi_master	*master = NULL; | 
					
						
							| 
									
										
										
										
											2008-01-22 15:14:18 +08:00
										 |  |  | 
 | 
					
						
							| 
									
										
										
										
											2008-05-22 17:21:08 -04:00
										 |  |  | 	dev = class_find_device(&spi_master_class, NULL, &bus_num, | 
					
						
							| 
									
										
										
										
											2008-01-22 15:14:18 +08:00
										 |  |  | 				__spi_master_match); | 
					
						
							|  |  |  | 	if (dev) | 
					
						
							|  |  |  | 		master = container_of(dev, struct spi_master, dev); | 
					
						
							|  |  |  | 	/* reference got in class_find_device */ | 
					
						
							| 
									
										
										
										
											2007-01-26 00:56:54 -08:00
										 |  |  | 	return master; | 
					
						
							| 
									
										
											  
											
												[PATCH] spi: simple SPI framework
This is the core of a small SPI framework, implementing the model of a
queue of messages which complete asynchronously (with thin synchronous
wrappers on top).
  - It's still less than 2KB of ".text" (ARM).  If there's got to be a
    mid-layer for something so simple, that's the right size budget.  :)
  - The guts use board-specific SPI device tables to build the driver
    model tree.  (Hardware probing is rarely an option.)
  - This version of Kconfig includes no drivers.  At this writing there
    are two known master controller drivers (PXA/SSP, OMAP MicroWire)
    and three protocol drivers (CS8415a, ADS7846, DataFlash) with LKML
    mentions of other drivers in development.
  - No userspace API.  There are several implementations to compare.
    Implement them like any other driver, and bind them with sysfs.
The changes from last version posted to LKML (on 11-Nov-2005) are minor,
and include:
  - One bugfix (removes a FIXME), with the visible effect of making device
    names be "spiB.C" where B is the bus number and C is the chipselect.
  - The "caller provides DMA mappings" mechanism now has kerneldoc, for
    DMA drivers that want to be fancy.
  - Hey, the framework init can be subsys_init.  Even though board init
    logic fires earlier, at arch_init ... since the framework init is
    for driver support, and the board init support uses static init.
  - Various additional spec/doc clarifications based on discussions
    with other folk.  It adds a brief "thank you" at the end, for folk
    who've helped nudge this framework into existence.
As I've said before, I think that "protocol tweaking" is the main support
that this driver framework will need to evolve.
From: Mark Underwood <basicmark@yahoo.com>
  Update the SPI framework to remove a potential priority inversion case by
  reverting to kmalloc if the pre-allocated DMA-safe buffer isn't available.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
											
										 
											2006-01-08 13:34:19 -08:00
										 |  |  | } | 
					
						
							|  |  |  | EXPORT_SYMBOL_GPL(spi_busnum_to_master); | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | /*-------------------------------------------------------------------------*/ | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											2009-06-17 16:26:03 -07:00
										 |  |  | /* Core methods for SPI master protocol drivers.  Some of the
 | 
					
						
							|  |  |  |  * other core methods are currently defined as inline functions. | 
					
						
							|  |  |  |  */ | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | /**
 | 
					
						
							|  |  |  |  * spi_setup - setup SPI mode and clock rate | 
					
						
							|  |  |  |  * @spi: the device whose settings are being modified | 
					
						
							|  |  |  |  * Context: can sleep, and no requests are queued to the device | 
					
						
							|  |  |  |  * | 
					
						
							|  |  |  |  * SPI protocol drivers may need to update the transfer mode if the | 
					
						
							|  |  |  |  * device doesn't work with its default.  They may likewise need | 
					
						
							|  |  |  |  * to update clock rates or word sizes from initial values.  This function | 
					
						
							|  |  |  |  * changes those settings, and must be called from a context that can sleep. | 
					
						
							|  |  |  |  * Except for SPI_CS_HIGH, which takes effect immediately, the changes take | 
					
						
							|  |  |  |  * effect the next time the device is selected and data is transferred to | 
					
						
							|  |  |  |  * or from it.  When this function returns, the spi device is deselected. | 
					
						
							|  |  |  |  * | 
					
						
							|  |  |  |  * Note that this call will fail if the protocol driver specifies an option | 
					
						
							|  |  |  |  * that the underlying controller or its driver does not support.  For | 
					
						
							|  |  |  |  * example, not all hardware supports wire transfers using nine bit words, | 
					
						
							|  |  |  |  * LSB-first wire encoding, or active-high chipselects. | 
					
						
							|  |  |  |  */ | 
					
						
							|  |  |  | int spi_setup(struct spi_device *spi) | 
					
						
							|  |  |  | { | 
					
						
							| 
									
										
										
										
											2009-06-17 16:26:04 -07:00
										 |  |  | 	unsigned	bad_bits; | 
					
						
							| 
									
										
										
										
											2009-06-17 16:26:03 -07:00
										 |  |  | 	int		status; | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											2009-06-17 16:26:04 -07:00
										 |  |  | 	/* help drivers fail *cleanly* when they need options
 | 
					
						
							|  |  |  | 	 * that aren't supported with their current master | 
					
						
							|  |  |  | 	 */ | 
					
						
							|  |  |  | 	bad_bits = spi->mode & ~spi->master->mode_bits; | 
					
						
							|  |  |  | 	if (bad_bits) { | 
					
						
							|  |  |  | 		dev_dbg(&spi->dev, "setup: unsupported mode bits %x\n", | 
					
						
							|  |  |  | 			bad_bits); | 
					
						
							|  |  |  | 		return -EINVAL; | 
					
						
							|  |  |  | 	} | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											2009-06-17 16:26:03 -07:00
										 |  |  | 	if (!spi->bits_per_word) | 
					
						
							|  |  |  | 		spi->bits_per_word = 8; | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | 	status = spi->master->setup(spi); | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | 	dev_dbg(&spi->dev, "setup mode %d, %s%s%s%s" | 
					
						
							|  |  |  | 				"%u bits/w, %u Hz max --> %d\n", | 
					
						
							|  |  |  | 			(int) (spi->mode & (SPI_CPOL | SPI_CPHA)), | 
					
						
							|  |  |  | 			(spi->mode & SPI_CS_HIGH) ? "cs_high, " : "", | 
					
						
							|  |  |  | 			(spi->mode & SPI_LSB_FIRST) ? "lsb, " : "", | 
					
						
							|  |  |  | 			(spi->mode & SPI_3WIRE) ? "3wire, " : "", | 
					
						
							|  |  |  | 			(spi->mode & SPI_LOOP) ? "loopback, " : "", | 
					
						
							|  |  |  | 			spi->bits_per_word, spi->max_speed_hz, | 
					
						
							|  |  |  | 			status); | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | 	return status; | 
					
						
							|  |  |  | } | 
					
						
							|  |  |  | EXPORT_SYMBOL_GPL(spi_setup); | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | /*-------------------------------------------------------------------------*/ | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | /* Utility methods for SPI master protocol drivers, layered on
 | 
					
						
							|  |  |  |  * top of the core.  Some other utility methods are defined as | 
					
						
							|  |  |  |  * inline functions. | 
					
						
							|  |  |  |  */ | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											2006-01-11 11:23:49 -08:00
										 |  |  | static void spi_complete(void *arg) | 
					
						
							|  |  |  | { | 
					
						
							|  |  |  | 	complete(arg); | 
					
						
							|  |  |  | } | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
											  
											
												[PATCH] spi: simple SPI framework
This is the core of a small SPI framework, implementing the model of a
queue of messages which complete asynchronously (with thin synchronous
wrappers on top).
  - It's still less than 2KB of ".text" (ARM).  If there's got to be a
    mid-layer for something so simple, that's the right size budget.  :)
  - The guts use board-specific SPI device tables to build the driver
    model tree.  (Hardware probing is rarely an option.)
  - This version of Kconfig includes no drivers.  At this writing there
    are two known master controller drivers (PXA/SSP, OMAP MicroWire)
    and three protocol drivers (CS8415a, ADS7846, DataFlash) with LKML
    mentions of other drivers in development.
  - No userspace API.  There are several implementations to compare.
    Implement them like any other driver, and bind them with sysfs.
The changes from last version posted to LKML (on 11-Nov-2005) are minor,
and include:
  - One bugfix (removes a FIXME), with the visible effect of making device
    names be "spiB.C" where B is the bus number and C is the chipselect.
  - The "caller provides DMA mappings" mechanism now has kerneldoc, for
    DMA drivers that want to be fancy.
  - Hey, the framework init can be subsys_init.  Even though board init
    logic fires earlier, at arch_init ... since the framework init is
    for driver support, and the board init support uses static init.
  - Various additional spec/doc clarifications based on discussions
    with other folk.  It adds a brief "thank you" at the end, for folk
    who've helped nudge this framework into existence.
As I've said before, I think that "protocol tweaking" is the main support
that this driver framework will need to evolve.
From: Mark Underwood <basicmark@yahoo.com>
  Update the SPI framework to remove a potential priority inversion case by
  reverting to kmalloc if the pre-allocated DMA-safe buffer isn't available.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
											
										 
											2006-01-08 13:34:19 -08:00
										 |  |  | /**
 | 
					
						
							|  |  |  |  * spi_sync - blocking/synchronous SPI data transfers | 
					
						
							|  |  |  |  * @spi: device with which data will be exchanged | 
					
						
							|  |  |  |  * @message: describes the data transfers | 
					
						
							| 
									
										
										
										
											2007-05-08 00:32:21 -07:00
										 |  |  |  * Context: can sleep | 
					
						
							| 
									
										
											  
											
												[PATCH] spi: simple SPI framework
This is the core of a small SPI framework, implementing the model of a
queue of messages which complete asynchronously (with thin synchronous
wrappers on top).
  - It's still less than 2KB of ".text" (ARM).  If there's got to be a
    mid-layer for something so simple, that's the right size budget.  :)
  - The guts use board-specific SPI device tables to build the driver
    model tree.  (Hardware probing is rarely an option.)
  - This version of Kconfig includes no drivers.  At this writing there
    are two known master controller drivers (PXA/SSP, OMAP MicroWire)
    and three protocol drivers (CS8415a, ADS7846, DataFlash) with LKML
    mentions of other drivers in development.
  - No userspace API.  There are several implementations to compare.
    Implement them like any other driver, and bind them with sysfs.
The changes from last version posted to LKML (on 11-Nov-2005) are minor,
and include:
  - One bugfix (removes a FIXME), with the visible effect of making device
    names be "spiB.C" where B is the bus number and C is the chipselect.
  - The "caller provides DMA mappings" mechanism now has kerneldoc, for
    DMA drivers that want to be fancy.
  - Hey, the framework init can be subsys_init.  Even though board init
    logic fires earlier, at arch_init ... since the framework init is
    for driver support, and the board init support uses static init.
  - Various additional spec/doc clarifications based on discussions
    with other folk.  It adds a brief "thank you" at the end, for folk
    who've helped nudge this framework into existence.
As I've said before, I think that "protocol tweaking" is the main support
that this driver framework will need to evolve.
From: Mark Underwood <basicmark@yahoo.com>
  Update the SPI framework to remove a potential priority inversion case by
  reverting to kmalloc if the pre-allocated DMA-safe buffer isn't available.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
											
										 
											2006-01-08 13:34:19 -08:00
										 |  |  |  * | 
					
						
							|  |  |  |  * This call may only be used from a context that may sleep.  The sleep | 
					
						
							|  |  |  |  * is non-interruptible, and has no timeout.  Low-overhead controller | 
					
						
							|  |  |  |  * drivers may DMA directly into and out of the message buffers. | 
					
						
							|  |  |  |  * | 
					
						
							|  |  |  |  * Note that the SPI device's chip select is active during the message, | 
					
						
							|  |  |  |  * and then is normally disabled between messages.  Drivers for some | 
					
						
							|  |  |  |  * frequently-used devices may want to minimize costs of selecting a chip, | 
					
						
							|  |  |  |  * by leaving it selected in anticipation that the next message will go | 
					
						
							|  |  |  |  * to the same chip.  (That may increase power usage.) | 
					
						
							|  |  |  |  * | 
					
						
							| 
									
										
										
										
											2006-01-08 13:34:25 -08:00
										 |  |  |  * Also, the caller is guaranteeing that the memory associated with the | 
					
						
							|  |  |  |  * message will not be freed before this call returns. | 
					
						
							|  |  |  |  * | 
					
						
							| 
									
										
										
										
											2007-12-04 23:45:10 -08:00
										 |  |  |  * It returns zero on success, else a negative error code. | 
					
						
							| 
									
										
											  
											
												[PATCH] spi: simple SPI framework
This is the core of a small SPI framework, implementing the model of a
queue of messages which complete asynchronously (with thin synchronous
wrappers on top).
  - It's still less than 2KB of ".text" (ARM).  If there's got to be a
    mid-layer for something so simple, that's the right size budget.  :)
  - The guts use board-specific SPI device tables to build the driver
    model tree.  (Hardware probing is rarely an option.)
  - This version of Kconfig includes no drivers.  At this writing there
    are two known master controller drivers (PXA/SSP, OMAP MicroWire)
    and three protocol drivers (CS8415a, ADS7846, DataFlash) with LKML
    mentions of other drivers in development.
  - No userspace API.  There are several implementations to compare.
    Implement them like any other driver, and bind them with sysfs.
The changes from last version posted to LKML (on 11-Nov-2005) are minor,
and include:
  - One bugfix (removes a FIXME), with the visible effect of making device
    names be "spiB.C" where B is the bus number and C is the chipselect.
  - The "caller provides DMA mappings" mechanism now has kerneldoc, for
    DMA drivers that want to be fancy.
  - Hey, the framework init can be subsys_init.  Even though board init
    logic fires earlier, at arch_init ... since the framework init is
    for driver support, and the board init support uses static init.
  - Various additional spec/doc clarifications based on discussions
    with other folk.  It adds a brief "thank you" at the end, for folk
    who've helped nudge this framework into existence.
As I've said before, I think that "protocol tweaking" is the main support
that this driver framework will need to evolve.
From: Mark Underwood <basicmark@yahoo.com>
  Update the SPI framework to remove a potential priority inversion case by
  reverting to kmalloc if the pre-allocated DMA-safe buffer isn't available.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
											
										 
											2006-01-08 13:34:19 -08:00
										 |  |  |  */ | 
					
						
							|  |  |  | int spi_sync(struct spi_device *spi, struct spi_message *message) | 
					
						
							|  |  |  | { | 
					
						
							| 
									
										
										
										
											2006-07-03 00:25:26 -07:00
										 |  |  | 	DECLARE_COMPLETION_ONSTACK(done); | 
					
						
							| 
									
										
											  
											
												[PATCH] spi: simple SPI framework
This is the core of a small SPI framework, implementing the model of a
queue of messages which complete asynchronously (with thin synchronous
wrappers on top).
  - It's still less than 2KB of ".text" (ARM).  If there's got to be a
    mid-layer for something so simple, that's the right size budget.  :)
  - The guts use board-specific SPI device tables to build the driver
    model tree.  (Hardware probing is rarely an option.)
  - This version of Kconfig includes no drivers.  At this writing there
    are two known master controller drivers (PXA/SSP, OMAP MicroWire)
    and three protocol drivers (CS8415a, ADS7846, DataFlash) with LKML
    mentions of other drivers in development.
  - No userspace API.  There are several implementations to compare.
    Implement them like any other driver, and bind them with sysfs.
The changes from last version posted to LKML (on 11-Nov-2005) are minor,
and include:
  - One bugfix (removes a FIXME), with the visible effect of making device
    names be "spiB.C" where B is the bus number and C is the chipselect.
  - The "caller provides DMA mappings" mechanism now has kerneldoc, for
    DMA drivers that want to be fancy.
  - Hey, the framework init can be subsys_init.  Even though board init
    logic fires earlier, at arch_init ... since the framework init is
    for driver support, and the board init support uses static init.
  - Various additional spec/doc clarifications based on discussions
    with other folk.  It adds a brief "thank you" at the end, for folk
    who've helped nudge this framework into existence.
As I've said before, I think that "protocol tweaking" is the main support
that this driver framework will need to evolve.
From: Mark Underwood <basicmark@yahoo.com>
  Update the SPI framework to remove a potential priority inversion case by
  reverting to kmalloc if the pre-allocated DMA-safe buffer isn't available.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
											
										 
											2006-01-08 13:34:19 -08:00
										 |  |  | 	int status; | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											2006-01-11 11:23:49 -08:00
										 |  |  | 	message->complete = spi_complete; | 
					
						
							| 
									
										
											  
											
												[PATCH] spi: simple SPI framework
This is the core of a small SPI framework, implementing the model of a
queue of messages which complete asynchronously (with thin synchronous
wrappers on top).
  - It's still less than 2KB of ".text" (ARM).  If there's got to be a
    mid-layer for something so simple, that's the right size budget.  :)
  - The guts use board-specific SPI device tables to build the driver
    model tree.  (Hardware probing is rarely an option.)
  - This version of Kconfig includes no drivers.  At this writing there
    are two known master controller drivers (PXA/SSP, OMAP MicroWire)
    and three protocol drivers (CS8415a, ADS7846, DataFlash) with LKML
    mentions of other drivers in development.
  - No userspace API.  There are several implementations to compare.
    Implement them like any other driver, and bind them with sysfs.
The changes from last version posted to LKML (on 11-Nov-2005) are minor,
and include:
  - One bugfix (removes a FIXME), with the visible effect of making device
    names be "spiB.C" where B is the bus number and C is the chipselect.
  - The "caller provides DMA mappings" mechanism now has kerneldoc, for
    DMA drivers that want to be fancy.
  - Hey, the framework init can be subsys_init.  Even though board init
    logic fires earlier, at arch_init ... since the framework init is
    for driver support, and the board init support uses static init.
  - Various additional spec/doc clarifications based on discussions
    with other folk.  It adds a brief "thank you" at the end, for folk
    who've helped nudge this framework into existence.
As I've said before, I think that "protocol tweaking" is the main support
that this driver framework will need to evolve.
From: Mark Underwood <basicmark@yahoo.com>
  Update the SPI framework to remove a potential priority inversion case by
  reverting to kmalloc if the pre-allocated DMA-safe buffer isn't available.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
											
										 
											2006-01-08 13:34:19 -08:00
										 |  |  | 	message->context = &done; | 
					
						
							|  |  |  | 	status = spi_async(spi, message); | 
					
						
							| 
									
										
										
										
											2007-12-04 23:45:10 -08:00
										 |  |  | 	if (status == 0) { | 
					
						
							| 
									
										
											  
											
												[PATCH] spi: simple SPI framework
This is the core of a small SPI framework, implementing the model of a
queue of messages which complete asynchronously (with thin synchronous
wrappers on top).
  - It's still less than 2KB of ".text" (ARM).  If there's got to be a
    mid-layer for something so simple, that's the right size budget.  :)
  - The guts use board-specific SPI device tables to build the driver
    model tree.  (Hardware probing is rarely an option.)
  - This version of Kconfig includes no drivers.  At this writing there
    are two known master controller drivers (PXA/SSP, OMAP MicroWire)
    and three protocol drivers (CS8415a, ADS7846, DataFlash) with LKML
    mentions of other drivers in development.
  - No userspace API.  There are several implementations to compare.
    Implement them like any other driver, and bind them with sysfs.
The changes from last version posted to LKML (on 11-Nov-2005) are minor,
and include:
  - One bugfix (removes a FIXME), with the visible effect of making device
    names be "spiB.C" where B is the bus number and C is the chipselect.
  - The "caller provides DMA mappings" mechanism now has kerneldoc, for
    DMA drivers that want to be fancy.
  - Hey, the framework init can be subsys_init.  Even though board init
    logic fires earlier, at arch_init ... since the framework init is
    for driver support, and the board init support uses static init.
  - Various additional spec/doc clarifications based on discussions
    with other folk.  It adds a brief "thank you" at the end, for folk
    who've helped nudge this framework into existence.
As I've said before, I think that "protocol tweaking" is the main support
that this driver framework will need to evolve.
From: Mark Underwood <basicmark@yahoo.com>
  Update the SPI framework to remove a potential priority inversion case by
  reverting to kmalloc if the pre-allocated DMA-safe buffer isn't available.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
											
										 
											2006-01-08 13:34:19 -08:00
										 |  |  | 		wait_for_completion(&done); | 
					
						
							| 
									
										
										
										
											2007-12-04 23:45:10 -08:00
										 |  |  | 		status = message->status; | 
					
						
							|  |  |  | 	} | 
					
						
							| 
									
										
											  
											
												[PATCH] spi: simple SPI framework
This is the core of a small SPI framework, implementing the model of a
queue of messages which complete asynchronously (with thin synchronous
wrappers on top).
  - It's still less than 2KB of ".text" (ARM).  If there's got to be a
    mid-layer for something so simple, that's the right size budget.  :)
  - The guts use board-specific SPI device tables to build the driver
    model tree.  (Hardware probing is rarely an option.)
  - This version of Kconfig includes no drivers.  At this writing there
    are two known master controller drivers (PXA/SSP, OMAP MicroWire)
    and three protocol drivers (CS8415a, ADS7846, DataFlash) with LKML
    mentions of other drivers in development.
  - No userspace API.  There are several implementations to compare.
    Implement them like any other driver, and bind them with sysfs.
The changes from last version posted to LKML (on 11-Nov-2005) are minor,
and include:
  - One bugfix (removes a FIXME), with the visible effect of making device
    names be "spiB.C" where B is the bus number and C is the chipselect.
  - The "caller provides DMA mappings" mechanism now has kerneldoc, for
    DMA drivers that want to be fancy.
  - Hey, the framework init can be subsys_init.  Even though board init
    logic fires earlier, at arch_init ... since the framework init is
    for driver support, and the board init support uses static init.
  - Various additional spec/doc clarifications based on discussions
    with other folk.  It adds a brief "thank you" at the end, for folk
    who've helped nudge this framework into existence.
As I've said before, I think that "protocol tweaking" is the main support
that this driver framework will need to evolve.
From: Mark Underwood <basicmark@yahoo.com>
  Update the SPI framework to remove a potential priority inversion case by
  reverting to kmalloc if the pre-allocated DMA-safe buffer isn't available.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
											
										 
											2006-01-08 13:34:19 -08:00
										 |  |  | 	message->context = NULL; | 
					
						
							|  |  |  | 	return status; | 
					
						
							|  |  |  | } | 
					
						
							|  |  |  | EXPORT_SYMBOL_GPL(spi_sync); | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											2006-04-02 10:37:40 -08:00
										 |  |  | /* portable code must never pass more than 32 bytes */ | 
					
						
							|  |  |  | #define	SPI_BUFSIZ	max(32,SMP_CACHE_BYTES)
 | 
					
						
							| 
									
										
											  
											
												[PATCH] spi: simple SPI framework
This is the core of a small SPI framework, implementing the model of a
queue of messages which complete asynchronously (with thin synchronous
wrappers on top).
  - It's still less than 2KB of ".text" (ARM).  If there's got to be a
    mid-layer for something so simple, that's the right size budget.  :)
  - The guts use board-specific SPI device tables to build the driver
    model tree.  (Hardware probing is rarely an option.)
  - This version of Kconfig includes no drivers.  At this writing there
    are two known master controller drivers (PXA/SSP, OMAP MicroWire)
    and three protocol drivers (CS8415a, ADS7846, DataFlash) with LKML
    mentions of other drivers in development.
  - No userspace API.  There are several implementations to compare.
    Implement them like any other driver, and bind them with sysfs.
The changes from last version posted to LKML (on 11-Nov-2005) are minor,
and include:
  - One bugfix (removes a FIXME), with the visible effect of making device
    names be "spiB.C" where B is the bus number and C is the chipselect.
  - The "caller provides DMA mappings" mechanism now has kerneldoc, for
    DMA drivers that want to be fancy.
  - Hey, the framework init can be subsys_init.  Even though board init
    logic fires earlier, at arch_init ... since the framework init is
    for driver support, and the board init support uses static init.
  - Various additional spec/doc clarifications based on discussions
    with other folk.  It adds a brief "thank you" at the end, for folk
    who've helped nudge this framework into existence.
As I've said before, I think that "protocol tweaking" is the main support
that this driver framework will need to evolve.
From: Mark Underwood <basicmark@yahoo.com>
  Update the SPI framework to remove a potential priority inversion case by
  reverting to kmalloc if the pre-allocated DMA-safe buffer isn't available.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
											
										 
											2006-01-08 13:34:19 -08:00
										 |  |  | 
 | 
					
						
							|  |  |  | static u8	*buf; | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | /**
 | 
					
						
							|  |  |  |  * spi_write_then_read - SPI synchronous write followed by read | 
					
						
							|  |  |  |  * @spi: device with which data will be exchanged | 
					
						
							|  |  |  |  * @txbuf: data to be written (need not be dma-safe) | 
					
						
							|  |  |  |  * @n_tx: size of txbuf, in bytes | 
					
						
							| 
									
										
										
										
											2009-06-17 16:26:06 -07:00
										 |  |  |  * @rxbuf: buffer into which data will be read (need not be dma-safe) | 
					
						
							|  |  |  |  * @n_rx: size of rxbuf, in bytes | 
					
						
							| 
									
										
										
										
											2007-05-08 00:32:21 -07:00
										 |  |  |  * Context: can sleep | 
					
						
							| 
									
										
											  
											
												[PATCH] spi: simple SPI framework
This is the core of a small SPI framework, implementing the model of a
queue of messages which complete asynchronously (with thin synchronous
wrappers on top).
  - It's still less than 2KB of ".text" (ARM).  If there's got to be a
    mid-layer for something so simple, that's the right size budget.  :)
  - The guts use board-specific SPI device tables to build the driver
    model tree.  (Hardware probing is rarely an option.)
  - This version of Kconfig includes no drivers.  At this writing there
    are two known master controller drivers (PXA/SSP, OMAP MicroWire)
    and three protocol drivers (CS8415a, ADS7846, DataFlash) with LKML
    mentions of other drivers in development.
  - No userspace API.  There are several implementations to compare.
    Implement them like any other driver, and bind them with sysfs.
The changes from last version posted to LKML (on 11-Nov-2005) are minor,
and include:
  - One bugfix (removes a FIXME), with the visible effect of making device
    names be "spiB.C" where B is the bus number and C is the chipselect.
  - The "caller provides DMA mappings" mechanism now has kerneldoc, for
    DMA drivers that want to be fancy.
  - Hey, the framework init can be subsys_init.  Even though board init
    logic fires earlier, at arch_init ... since the framework init is
    for driver support, and the board init support uses static init.
  - Various additional spec/doc clarifications based on discussions
    with other folk.  It adds a brief "thank you" at the end, for folk
    who've helped nudge this framework into existence.
As I've said before, I think that "protocol tweaking" is the main support
that this driver framework will need to evolve.
From: Mark Underwood <basicmark@yahoo.com>
  Update the SPI framework to remove a potential priority inversion case by
  reverting to kmalloc if the pre-allocated DMA-safe buffer isn't available.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
											
										 
											2006-01-08 13:34:19 -08:00
										 |  |  |  * | 
					
						
							|  |  |  |  * This performs a half duplex MicroWire style transaction with the | 
					
						
							|  |  |  |  * device, sending txbuf and then reading rxbuf.  The return value | 
					
						
							|  |  |  |  * is zero for success, else a negative errno status code. | 
					
						
							| 
									
										
										
										
											2006-01-08 13:34:23 -08:00
										 |  |  |  * This call may only be used from a context that may sleep. | 
					
						
							| 
									
										
											  
											
												[PATCH] spi: simple SPI framework
This is the core of a small SPI framework, implementing the model of a
queue of messages which complete asynchronously (with thin synchronous
wrappers on top).
  - It's still less than 2KB of ".text" (ARM).  If there's got to be a
    mid-layer for something so simple, that's the right size budget.  :)
  - The guts use board-specific SPI device tables to build the driver
    model tree.  (Hardware probing is rarely an option.)
  - This version of Kconfig includes no drivers.  At this writing there
    are two known master controller drivers (PXA/SSP, OMAP MicroWire)
    and three protocol drivers (CS8415a, ADS7846, DataFlash) with LKML
    mentions of other drivers in development.
  - No userspace API.  There are several implementations to compare.
    Implement them like any other driver, and bind them with sysfs.
The changes from last version posted to LKML (on 11-Nov-2005) are minor,
and include:
  - One bugfix (removes a FIXME), with the visible effect of making device
    names be "spiB.C" where B is the bus number and C is the chipselect.
  - The "caller provides DMA mappings" mechanism now has kerneldoc, for
    DMA drivers that want to be fancy.
  - Hey, the framework init can be subsys_init.  Even though board init
    logic fires earlier, at arch_init ... since the framework init is
    for driver support, and the board init support uses static init.
  - Various additional spec/doc clarifications based on discussions
    with other folk.  It adds a brief "thank you" at the end, for folk
    who've helped nudge this framework into existence.
As I've said before, I think that "protocol tweaking" is the main support
that this driver framework will need to evolve.
From: Mark Underwood <basicmark@yahoo.com>
  Update the SPI framework to remove a potential priority inversion case by
  reverting to kmalloc if the pre-allocated DMA-safe buffer isn't available.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
											
										 
											2006-01-08 13:34:19 -08:00
										 |  |  |  * | 
					
						
							| 
									
										
										
										
											2006-01-08 13:34:25 -08:00
										 |  |  |  * Parameters to this routine are always copied using a small buffer; | 
					
						
							| 
									
										
										
										
											2007-05-08 00:32:21 -07:00
										 |  |  |  * portable code should never use this for more than 32 bytes. | 
					
						
							|  |  |  |  * Performance-sensitive or bulk transfer code should instead use | 
					
						
							| 
									
										
										
										
											2006-01-08 13:34:25 -08:00
										 |  |  |  * spi_{async,sync}() calls with dma-safe buffers. | 
					
						
							| 
									
										
											  
											
												[PATCH] spi: simple SPI framework
This is the core of a small SPI framework, implementing the model of a
queue of messages which complete asynchronously (with thin synchronous
wrappers on top).
  - It's still less than 2KB of ".text" (ARM).  If there's got to be a
    mid-layer for something so simple, that's the right size budget.  :)
  - The guts use board-specific SPI device tables to build the driver
    model tree.  (Hardware probing is rarely an option.)
  - This version of Kconfig includes no drivers.  At this writing there
    are two known master controller drivers (PXA/SSP, OMAP MicroWire)
    and three protocol drivers (CS8415a, ADS7846, DataFlash) with LKML
    mentions of other drivers in development.
  - No userspace API.  There are several implementations to compare.
    Implement them like any other driver, and bind them with sysfs.
The changes from last version posted to LKML (on 11-Nov-2005) are minor,
and include:
  - One bugfix (removes a FIXME), with the visible effect of making device
    names be "spiB.C" where B is the bus number and C is the chipselect.
  - The "caller provides DMA mappings" mechanism now has kerneldoc, for
    DMA drivers that want to be fancy.
  - Hey, the framework init can be subsys_init.  Even though board init
    logic fires earlier, at arch_init ... since the framework init is
    for driver support, and the board init support uses static init.
  - Various additional spec/doc clarifications based on discussions
    with other folk.  It adds a brief "thank you" at the end, for folk
    who've helped nudge this framework into existence.
As I've said before, I think that "protocol tweaking" is the main support
that this driver framework will need to evolve.
From: Mark Underwood <basicmark@yahoo.com>
  Update the SPI framework to remove a potential priority inversion case by
  reverting to kmalloc if the pre-allocated DMA-safe buffer isn't available.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
											
										 
											2006-01-08 13:34:19 -08:00
										 |  |  |  */ | 
					
						
							|  |  |  | int spi_write_then_read(struct spi_device *spi, | 
					
						
							|  |  |  | 		const u8 *txbuf, unsigned n_tx, | 
					
						
							|  |  |  | 		u8 *rxbuf, unsigned n_rx) | 
					
						
							|  |  |  | { | 
					
						
							| 
									
										
										
										
											2007-12-04 23:45:09 -08:00
										 |  |  | 	static DEFINE_MUTEX(lock); | 
					
						
							| 
									
										
											  
											
												[PATCH] spi: simple SPI framework
This is the core of a small SPI framework, implementing the model of a
queue of messages which complete asynchronously (with thin synchronous
wrappers on top).
  - It's still less than 2KB of ".text" (ARM).  If there's got to be a
    mid-layer for something so simple, that's the right size budget.  :)
  - The guts use board-specific SPI device tables to build the driver
    model tree.  (Hardware probing is rarely an option.)
  - This version of Kconfig includes no drivers.  At this writing there
    are two known master controller drivers (PXA/SSP, OMAP MicroWire)
    and three protocol drivers (CS8415a, ADS7846, DataFlash) with LKML
    mentions of other drivers in development.
  - No userspace API.  There are several implementations to compare.
    Implement them like any other driver, and bind them with sysfs.
The changes from last version posted to LKML (on 11-Nov-2005) are minor,
and include:
  - One bugfix (removes a FIXME), with the visible effect of making device
    names be "spiB.C" where B is the bus number and C is the chipselect.
  - The "caller provides DMA mappings" mechanism now has kerneldoc, for
    DMA drivers that want to be fancy.
  - Hey, the framework init can be subsys_init.  Even though board init
    logic fires earlier, at arch_init ... since the framework init is
    for driver support, and the board init support uses static init.
  - Various additional spec/doc clarifications based on discussions
    with other folk.  It adds a brief "thank you" at the end, for folk
    who've helped nudge this framework into existence.
As I've said before, I think that "protocol tweaking" is the main support
that this driver framework will need to evolve.
From: Mark Underwood <basicmark@yahoo.com>
  Update the SPI framework to remove a potential priority inversion case by
  reverting to kmalloc if the pre-allocated DMA-safe buffer isn't available.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
											
										 
											2006-01-08 13:34:19 -08:00
										 |  |  | 
 | 
					
						
							|  |  |  | 	int			status; | 
					
						
							|  |  |  | 	struct spi_message	message; | 
					
						
							| 
									
										
										
										
											2009-04-13 14:39:57 -07:00
										 |  |  | 	struct spi_transfer	x[2]; | 
					
						
							| 
									
										
											  
											
												[PATCH] spi: simple SPI framework
This is the core of a small SPI framework, implementing the model of a
queue of messages which complete asynchronously (with thin synchronous
wrappers on top).
  - It's still less than 2KB of ".text" (ARM).  If there's got to be a
    mid-layer for something so simple, that's the right size budget.  :)
  - The guts use board-specific SPI device tables to build the driver
    model tree.  (Hardware probing is rarely an option.)
  - This version of Kconfig includes no drivers.  At this writing there
    are two known master controller drivers (PXA/SSP, OMAP MicroWire)
    and three protocol drivers (CS8415a, ADS7846, DataFlash) with LKML
    mentions of other drivers in development.
  - No userspace API.  There are several implementations to compare.
    Implement them like any other driver, and bind them with sysfs.
The changes from last version posted to LKML (on 11-Nov-2005) are minor,
and include:
  - One bugfix (removes a FIXME), with the visible effect of making device
    names be "spiB.C" where B is the bus number and C is the chipselect.
  - The "caller provides DMA mappings" mechanism now has kerneldoc, for
    DMA drivers that want to be fancy.
  - Hey, the framework init can be subsys_init.  Even though board init
    logic fires earlier, at arch_init ... since the framework init is
    for driver support, and the board init support uses static init.
  - Various additional spec/doc clarifications based on discussions
    with other folk.  It adds a brief "thank you" at the end, for folk
    who've helped nudge this framework into existence.
As I've said before, I think that "protocol tweaking" is the main support
that this driver framework will need to evolve.
From: Mark Underwood <basicmark@yahoo.com>
  Update the SPI framework to remove a potential priority inversion case by
  reverting to kmalloc if the pre-allocated DMA-safe buffer isn't available.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
											
										 
											2006-01-08 13:34:19 -08:00
										 |  |  | 	u8			*local_buf; | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | 	/* Use preallocated DMA-safe buffer.  We can't avoid copying here,
 | 
					
						
							|  |  |  | 	 * (as a pure convenience thing), but we can keep heap costs | 
					
						
							|  |  |  | 	 * out of the hot path ... | 
					
						
							|  |  |  | 	 */ | 
					
						
							|  |  |  | 	if ((n_tx + n_rx) > SPI_BUFSIZ) | 
					
						
							|  |  |  | 		return -EINVAL; | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											2006-01-08 13:34:28 -08:00
										 |  |  | 	spi_message_init(&message); | 
					
						
							| 
									
										
										
										
											2009-04-13 14:39:57 -07:00
										 |  |  | 	memset(x, 0, sizeof x); | 
					
						
							|  |  |  | 	if (n_tx) { | 
					
						
							|  |  |  | 		x[0].len = n_tx; | 
					
						
							|  |  |  | 		spi_message_add_tail(&x[0], &message); | 
					
						
							|  |  |  | 	} | 
					
						
							|  |  |  | 	if (n_rx) { | 
					
						
							|  |  |  | 		x[1].len = n_rx; | 
					
						
							|  |  |  | 		spi_message_add_tail(&x[1], &message); | 
					
						
							|  |  |  | 	} | 
					
						
							| 
									
										
										
										
											2006-01-08 13:34:28 -08:00
										 |  |  | 
 | 
					
						
							| 
									
										
											  
											
												[PATCH] spi: simple SPI framework
This is the core of a small SPI framework, implementing the model of a
queue of messages which complete asynchronously (with thin synchronous
wrappers on top).
  - It's still less than 2KB of ".text" (ARM).  If there's got to be a
    mid-layer for something so simple, that's the right size budget.  :)
  - The guts use board-specific SPI device tables to build the driver
    model tree.  (Hardware probing is rarely an option.)
  - This version of Kconfig includes no drivers.  At this writing there
    are two known master controller drivers (PXA/SSP, OMAP MicroWire)
    and three protocol drivers (CS8415a, ADS7846, DataFlash) with LKML
    mentions of other drivers in development.
  - No userspace API.  There are several implementations to compare.
    Implement them like any other driver, and bind them with sysfs.
The changes from last version posted to LKML (on 11-Nov-2005) are minor,
and include:
  - One bugfix (removes a FIXME), with the visible effect of making device
    names be "spiB.C" where B is the bus number and C is the chipselect.
  - The "caller provides DMA mappings" mechanism now has kerneldoc, for
    DMA drivers that want to be fancy.
  - Hey, the framework init can be subsys_init.  Even though board init
    logic fires earlier, at arch_init ... since the framework init is
    for driver support, and the board init support uses static init.
  - Various additional spec/doc clarifications based on discussions
    with other folk.  It adds a brief "thank you" at the end, for folk
    who've helped nudge this framework into existence.
As I've said before, I think that "protocol tweaking" is the main support
that this driver framework will need to evolve.
From: Mark Underwood <basicmark@yahoo.com>
  Update the SPI framework to remove a potential priority inversion case by
  reverting to kmalloc if the pre-allocated DMA-safe buffer isn't available.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
											
										 
											2006-01-08 13:34:19 -08:00
										 |  |  | 	/* ... unless someone else is using the pre-allocated buffer */ | 
					
						
							| 
									
										
										
										
											2007-12-04 23:45:09 -08:00
										 |  |  | 	if (!mutex_trylock(&lock)) { | 
					
						
							| 
									
										
											  
											
												[PATCH] spi: simple SPI framework
This is the core of a small SPI framework, implementing the model of a
queue of messages which complete asynchronously (with thin synchronous
wrappers on top).
  - It's still less than 2KB of ".text" (ARM).  If there's got to be a
    mid-layer for something so simple, that's the right size budget.  :)
  - The guts use board-specific SPI device tables to build the driver
    model tree.  (Hardware probing is rarely an option.)
  - This version of Kconfig includes no drivers.  At this writing there
    are two known master controller drivers (PXA/SSP, OMAP MicroWire)
    and three protocol drivers (CS8415a, ADS7846, DataFlash) with LKML
    mentions of other drivers in development.
  - No userspace API.  There are several implementations to compare.
    Implement them like any other driver, and bind them with sysfs.
The changes from last version posted to LKML (on 11-Nov-2005) are minor,
and include:
  - One bugfix (removes a FIXME), with the visible effect of making device
    names be "spiB.C" where B is the bus number and C is the chipselect.
  - The "caller provides DMA mappings" mechanism now has kerneldoc, for
    DMA drivers that want to be fancy.
  - Hey, the framework init can be subsys_init.  Even though board init
    logic fires earlier, at arch_init ... since the framework init is
    for driver support, and the board init support uses static init.
  - Various additional spec/doc clarifications based on discussions
    with other folk.  It adds a brief "thank you" at the end, for folk
    who've helped nudge this framework into existence.
As I've said before, I think that "protocol tweaking" is the main support
that this driver framework will need to evolve.
From: Mark Underwood <basicmark@yahoo.com>
  Update the SPI framework to remove a potential priority inversion case by
  reverting to kmalloc if the pre-allocated DMA-safe buffer isn't available.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
											
										 
											2006-01-08 13:34:19 -08:00
										 |  |  | 		local_buf = kmalloc(SPI_BUFSIZ, GFP_KERNEL); | 
					
						
							|  |  |  | 		if (!local_buf) | 
					
						
							|  |  |  | 			return -ENOMEM; | 
					
						
							|  |  |  | 	} else | 
					
						
							|  |  |  | 		local_buf = buf; | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | 	memcpy(local_buf, txbuf, n_tx); | 
					
						
							| 
									
										
										
										
											2009-04-13 14:39:57 -07:00
										 |  |  | 	x[0].tx_buf = local_buf; | 
					
						
							|  |  |  | 	x[1].rx_buf = local_buf + n_tx; | 
					
						
							| 
									
										
											  
											
												[PATCH] spi: simple SPI framework
This is the core of a small SPI framework, implementing the model of a
queue of messages which complete asynchronously (with thin synchronous
wrappers on top).
  - It's still less than 2KB of ".text" (ARM).  If there's got to be a
    mid-layer for something so simple, that's the right size budget.  :)
  - The guts use board-specific SPI device tables to build the driver
    model tree.  (Hardware probing is rarely an option.)
  - This version of Kconfig includes no drivers.  At this writing there
    are two known master controller drivers (PXA/SSP, OMAP MicroWire)
    and three protocol drivers (CS8415a, ADS7846, DataFlash) with LKML
    mentions of other drivers in development.
  - No userspace API.  There are several implementations to compare.
    Implement them like any other driver, and bind them with sysfs.
The changes from last version posted to LKML (on 11-Nov-2005) are minor,
and include:
  - One bugfix (removes a FIXME), with the visible effect of making device
    names be "spiB.C" where B is the bus number and C is the chipselect.
  - The "caller provides DMA mappings" mechanism now has kerneldoc, for
    DMA drivers that want to be fancy.
  - Hey, the framework init can be subsys_init.  Even though board init
    logic fires earlier, at arch_init ... since the framework init is
    for driver support, and the board init support uses static init.
  - Various additional spec/doc clarifications based on discussions
    with other folk.  It adds a brief "thank you" at the end, for folk
    who've helped nudge this framework into existence.
As I've said before, I think that "protocol tweaking" is the main support
that this driver framework will need to evolve.
From: Mark Underwood <basicmark@yahoo.com>
  Update the SPI framework to remove a potential priority inversion case by
  reverting to kmalloc if the pre-allocated DMA-safe buffer isn't available.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
											
										 
											2006-01-08 13:34:19 -08:00
										 |  |  | 
 | 
					
						
							|  |  |  | 	/* do the i/o */ | 
					
						
							|  |  |  | 	status = spi_sync(spi, &message); | 
					
						
							| 
									
										
										
										
											2007-12-04 23:45:10 -08:00
										 |  |  | 	if (status == 0) | 
					
						
							| 
									
										
										
										
											2009-04-13 14:39:57 -07:00
										 |  |  | 		memcpy(rxbuf, x[1].rx_buf, n_rx); | 
					
						
							| 
									
										
											  
											
												[PATCH] spi: simple SPI framework
This is the core of a small SPI framework, implementing the model of a
queue of messages which complete asynchronously (with thin synchronous
wrappers on top).
  - It's still less than 2KB of ".text" (ARM).  If there's got to be a
    mid-layer for something so simple, that's the right size budget.  :)
  - The guts use board-specific SPI device tables to build the driver
    model tree.  (Hardware probing is rarely an option.)
  - This version of Kconfig includes no drivers.  At this writing there
    are two known master controller drivers (PXA/SSP, OMAP MicroWire)
    and three protocol drivers (CS8415a, ADS7846, DataFlash) with LKML
    mentions of other drivers in development.
  - No userspace API.  There are several implementations to compare.
    Implement them like any other driver, and bind them with sysfs.
The changes from last version posted to LKML (on 11-Nov-2005) are minor,
and include:
  - One bugfix (removes a FIXME), with the visible effect of making device
    names be "spiB.C" where B is the bus number and C is the chipselect.
  - The "caller provides DMA mappings" mechanism now has kerneldoc, for
    DMA drivers that want to be fancy.
  - Hey, the framework init can be subsys_init.  Even though board init
    logic fires earlier, at arch_init ... since the framework init is
    for driver support, and the board init support uses static init.
  - Various additional spec/doc clarifications based on discussions
    with other folk.  It adds a brief "thank you" at the end, for folk
    who've helped nudge this framework into existence.
As I've said before, I think that "protocol tweaking" is the main support
that this driver framework will need to evolve.
From: Mark Underwood <basicmark@yahoo.com>
  Update the SPI framework to remove a potential priority inversion case by
  reverting to kmalloc if the pre-allocated DMA-safe buffer isn't available.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
											
										 
											2006-01-08 13:34:19 -08:00
										 |  |  | 
 | 
					
						
							| 
									
										
										
										
											2009-04-13 14:39:57 -07:00
										 |  |  | 	if (x[0].tx_buf == buf) | 
					
						
							| 
									
										
										
										
											2007-12-04 23:45:09 -08:00
										 |  |  | 		mutex_unlock(&lock); | 
					
						
							| 
									
										
											  
											
												[PATCH] spi: simple SPI framework
This is the core of a small SPI framework, implementing the model of a
queue of messages which complete asynchronously (with thin synchronous
wrappers on top).
  - It's still less than 2KB of ".text" (ARM).  If there's got to be a
    mid-layer for something so simple, that's the right size budget.  :)
  - The guts use board-specific SPI device tables to build the driver
    model tree.  (Hardware probing is rarely an option.)
  - This version of Kconfig includes no drivers.  At this writing there
    are two known master controller drivers (PXA/SSP, OMAP MicroWire)
    and three protocol drivers (CS8415a, ADS7846, DataFlash) with LKML
    mentions of other drivers in development.
  - No userspace API.  There are several implementations to compare.
    Implement them like any other driver, and bind them with sysfs.
The changes from last version posted to LKML (on 11-Nov-2005) are minor,
and include:
  - One bugfix (removes a FIXME), with the visible effect of making device
    names be "spiB.C" where B is the bus number and C is the chipselect.
  - The "caller provides DMA mappings" mechanism now has kerneldoc, for
    DMA drivers that want to be fancy.
  - Hey, the framework init can be subsys_init.  Even though board init
    logic fires earlier, at arch_init ... since the framework init is
    for driver support, and the board init support uses static init.
  - Various additional spec/doc clarifications based on discussions
    with other folk.  It adds a brief "thank you" at the end, for folk
    who've helped nudge this framework into existence.
As I've said before, I think that "protocol tweaking" is the main support
that this driver framework will need to evolve.
From: Mark Underwood <basicmark@yahoo.com>
  Update the SPI framework to remove a potential priority inversion case by
  reverting to kmalloc if the pre-allocated DMA-safe buffer isn't available.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
											
										 
											2006-01-08 13:34:19 -08:00
										 |  |  | 	else | 
					
						
							|  |  |  | 		kfree(local_buf); | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | 	return status; | 
					
						
							|  |  |  | } | 
					
						
							|  |  |  | EXPORT_SYMBOL_GPL(spi_write_then_read); | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | /*-------------------------------------------------------------------------*/ | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | static int __init spi_init(void) | 
					
						
							|  |  |  | { | 
					
						
							| 
									
										
										
										
											2006-01-08 13:34:23 -08:00
										 |  |  | 	int	status; | 
					
						
							|  |  |  | 
 | 
					
						
							| 
									
										
										
										
											2006-12-06 20:33:17 -08:00
										 |  |  | 	buf = kmalloc(SPI_BUFSIZ, GFP_KERNEL); | 
					
						
							| 
									
										
										
										
											2006-01-08 13:34:23 -08:00
										 |  |  | 	if (!buf) { | 
					
						
							|  |  |  | 		status = -ENOMEM; | 
					
						
							|  |  |  | 		goto err0; | 
					
						
							|  |  |  | 	} | 
					
						
							|  |  |  | 
 | 
					
						
							|  |  |  | 	status = bus_register(&spi_bus_type); | 
					
						
							|  |  |  | 	if (status < 0) | 
					
						
							|  |  |  | 		goto err1; | 
					
						
							| 
									
										
											  
											
												[PATCH] spi: simple SPI framework
This is the core of a small SPI framework, implementing the model of a
queue of messages which complete asynchronously (with thin synchronous
wrappers on top).
  - It's still less than 2KB of ".text" (ARM).  If there's got to be a
    mid-layer for something so simple, that's the right size budget.  :)
  - The guts use board-specific SPI device tables to build the driver
    model tree.  (Hardware probing is rarely an option.)
  - This version of Kconfig includes no drivers.  At this writing there
    are two known master controller drivers (PXA/SSP, OMAP MicroWire)
    and three protocol drivers (CS8415a, ADS7846, DataFlash) with LKML
    mentions of other drivers in development.
  - No userspace API.  There are several implementations to compare.
    Implement them like any other driver, and bind them with sysfs.
The changes from last version posted to LKML (on 11-Nov-2005) are minor,
and include:
  - One bugfix (removes a FIXME), with the visible effect of making device
    names be "spiB.C" where B is the bus number and C is the chipselect.
  - The "caller provides DMA mappings" mechanism now has kerneldoc, for
    DMA drivers that want to be fancy.
  - Hey, the framework init can be subsys_init.  Even though board init
    logic fires earlier, at arch_init ... since the framework init is
    for driver support, and the board init support uses static init.
  - Various additional spec/doc clarifications based on discussions
    with other folk.  It adds a brief "thank you" at the end, for folk
    who've helped nudge this framework into existence.
As I've said before, I think that "protocol tweaking" is the main support
that this driver framework will need to evolve.
From: Mark Underwood <basicmark@yahoo.com>
  Update the SPI framework to remove a potential priority inversion case by
  reverting to kmalloc if the pre-allocated DMA-safe buffer isn't available.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
											
										 
											2006-01-08 13:34:19 -08:00
										 |  |  | 
 | 
					
						
							| 
									
										
										
										
											2006-01-08 13:34:23 -08:00
										 |  |  | 	status = class_register(&spi_master_class); | 
					
						
							|  |  |  | 	if (status < 0) | 
					
						
							|  |  |  | 		goto err2; | 
					
						
							| 
									
										
											  
											
												[PATCH] spi: simple SPI framework
This is the core of a small SPI framework, implementing the model of a
queue of messages which complete asynchronously (with thin synchronous
wrappers on top).
  - It's still less than 2KB of ".text" (ARM).  If there's got to be a
    mid-layer for something so simple, that's the right size budget.  :)
  - The guts use board-specific SPI device tables to build the driver
    model tree.  (Hardware probing is rarely an option.)
  - This version of Kconfig includes no drivers.  At this writing there
    are two known master controller drivers (PXA/SSP, OMAP MicroWire)
    and three protocol drivers (CS8415a, ADS7846, DataFlash) with LKML
    mentions of other drivers in development.
  - No userspace API.  There are several implementations to compare.
    Implement them like any other driver, and bind them with sysfs.
The changes from last version posted to LKML (on 11-Nov-2005) are minor,
and include:
  - One bugfix (removes a FIXME), with the visible effect of making device
    names be "spiB.C" where B is the bus number and C is the chipselect.
  - The "caller provides DMA mappings" mechanism now has kerneldoc, for
    DMA drivers that want to be fancy.
  - Hey, the framework init can be subsys_init.  Even though board init
    logic fires earlier, at arch_init ... since the framework init is
    for driver support, and the board init support uses static init.
  - Various additional spec/doc clarifications based on discussions
    with other folk.  It adds a brief "thank you" at the end, for folk
    who've helped nudge this framework into existence.
As I've said before, I think that "protocol tweaking" is the main support
that this driver framework will need to evolve.
From: Mark Underwood <basicmark@yahoo.com>
  Update the SPI framework to remove a potential priority inversion case by
  reverting to kmalloc if the pre-allocated DMA-safe buffer isn't available.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
											
										 
											2006-01-08 13:34:19 -08:00
										 |  |  | 	return 0; | 
					
						
							| 
									
										
										
										
											2006-01-08 13:34:23 -08:00
										 |  |  | 
 | 
					
						
							|  |  |  | err2: | 
					
						
							|  |  |  | 	bus_unregister(&spi_bus_type); | 
					
						
							|  |  |  | err1: | 
					
						
							|  |  |  | 	kfree(buf); | 
					
						
							|  |  |  | 	buf = NULL; | 
					
						
							|  |  |  | err0: | 
					
						
							|  |  |  | 	return status; | 
					
						
							| 
									
										
											  
											
												[PATCH] spi: simple SPI framework
This is the core of a small SPI framework, implementing the model of a
queue of messages which complete asynchronously (with thin synchronous
wrappers on top).
  - It's still less than 2KB of ".text" (ARM).  If there's got to be a
    mid-layer for something so simple, that's the right size budget.  :)
  - The guts use board-specific SPI device tables to build the driver
    model tree.  (Hardware probing is rarely an option.)
  - This version of Kconfig includes no drivers.  At this writing there
    are two known master controller drivers (PXA/SSP, OMAP MicroWire)
    and three protocol drivers (CS8415a, ADS7846, DataFlash) with LKML
    mentions of other drivers in development.
  - No userspace API.  There are several implementations to compare.
    Implement them like any other driver, and bind them with sysfs.
The changes from last version posted to LKML (on 11-Nov-2005) are minor,
and include:
  - One bugfix (removes a FIXME), with the visible effect of making device
    names be "spiB.C" where B is the bus number and C is the chipselect.
  - The "caller provides DMA mappings" mechanism now has kerneldoc, for
    DMA drivers that want to be fancy.
  - Hey, the framework init can be subsys_init.  Even though board init
    logic fires earlier, at arch_init ... since the framework init is
    for driver support, and the board init support uses static init.
  - Various additional spec/doc clarifications based on discussions
    with other folk.  It adds a brief "thank you" at the end, for folk
    who've helped nudge this framework into existence.
As I've said before, I think that "protocol tweaking" is the main support
that this driver framework will need to evolve.
From: Mark Underwood <basicmark@yahoo.com>
  Update the SPI framework to remove a potential priority inversion case by
  reverting to kmalloc if the pre-allocated DMA-safe buffer isn't available.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
											
										 
											2006-01-08 13:34:19 -08:00
										 |  |  | } | 
					
						
							| 
									
										
										
										
											2006-01-08 13:34:23 -08:00
										 |  |  | 
 | 
					
						
							| 
									
										
											  
											
												[PATCH] spi: simple SPI framework
This is the core of a small SPI framework, implementing the model of a
queue of messages which complete asynchronously (with thin synchronous
wrappers on top).
  - It's still less than 2KB of ".text" (ARM).  If there's got to be a
    mid-layer for something so simple, that's the right size budget.  :)
  - The guts use board-specific SPI device tables to build the driver
    model tree.  (Hardware probing is rarely an option.)
  - This version of Kconfig includes no drivers.  At this writing there
    are two known master controller drivers (PXA/SSP, OMAP MicroWire)
    and three protocol drivers (CS8415a, ADS7846, DataFlash) with LKML
    mentions of other drivers in development.
  - No userspace API.  There are several implementations to compare.
    Implement them like any other driver, and bind them with sysfs.
The changes from last version posted to LKML (on 11-Nov-2005) are minor,
and include:
  - One bugfix (removes a FIXME), with the visible effect of making device
    names be "spiB.C" where B is the bus number and C is the chipselect.
  - The "caller provides DMA mappings" mechanism now has kerneldoc, for
    DMA drivers that want to be fancy.
  - Hey, the framework init can be subsys_init.  Even though board init
    logic fires earlier, at arch_init ... since the framework init is
    for driver support, and the board init support uses static init.
  - Various additional spec/doc clarifications based on discussions
    with other folk.  It adds a brief "thank you" at the end, for folk
    who've helped nudge this framework into existence.
As I've said before, I think that "protocol tweaking" is the main support
that this driver framework will need to evolve.
From: Mark Underwood <basicmark@yahoo.com>
  Update the SPI framework to remove a potential priority inversion case by
  reverting to kmalloc if the pre-allocated DMA-safe buffer isn't available.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
											
										 
											2006-01-08 13:34:19 -08:00
										 |  |  | /* board_info is normally registered in arch_initcall(),
 | 
					
						
							|  |  |  |  * but even essential drivers wait till later | 
					
						
							| 
									
										
										
										
											2006-01-08 13:34:23 -08:00
										 |  |  |  * | 
					
						
							|  |  |  |  * REVISIT only boardinfo really needs static linking. the rest (device and | 
					
						
							|  |  |  |  * driver registration) _could_ be dynamically linked (modular) ... costs | 
					
						
							|  |  |  |  * include needing to have boardinfo data structures be much more public. | 
					
						
							| 
									
										
											  
											
												[PATCH] spi: simple SPI framework
This is the core of a small SPI framework, implementing the model of a
queue of messages which complete asynchronously (with thin synchronous
wrappers on top).
  - It's still less than 2KB of ".text" (ARM).  If there's got to be a
    mid-layer for something so simple, that's the right size budget.  :)
  - The guts use board-specific SPI device tables to build the driver
    model tree.  (Hardware probing is rarely an option.)
  - This version of Kconfig includes no drivers.  At this writing there
    are two known master controller drivers (PXA/SSP, OMAP MicroWire)
    and three protocol drivers (CS8415a, ADS7846, DataFlash) with LKML
    mentions of other drivers in development.
  - No userspace API.  There are several implementations to compare.
    Implement them like any other driver, and bind them with sysfs.
The changes from last version posted to LKML (on 11-Nov-2005) are minor,
and include:
  - One bugfix (removes a FIXME), with the visible effect of making device
    names be "spiB.C" where B is the bus number and C is the chipselect.
  - The "caller provides DMA mappings" mechanism now has kerneldoc, for
    DMA drivers that want to be fancy.
  - Hey, the framework init can be subsys_init.  Even though board init
    logic fires earlier, at arch_init ... since the framework init is
    for driver support, and the board init support uses static init.
  - Various additional spec/doc clarifications based on discussions
    with other folk.  It adds a brief "thank you" at the end, for folk
    who've helped nudge this framework into existence.
As I've said before, I think that "protocol tweaking" is the main support
that this driver framework will need to evolve.
From: Mark Underwood <basicmark@yahoo.com>
  Update the SPI framework to remove a potential priority inversion case by
  reverting to kmalloc if the pre-allocated DMA-safe buffer isn't available.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
											
										 
											2006-01-08 13:34:19 -08:00
										 |  |  |  */ | 
					
						
							| 
									
										
										
										
											2008-10-15 22:02:46 -07:00
										 |  |  | postcore_initcall(spi_init); | 
					
						
							| 
									
										
											  
											
												[PATCH] spi: simple SPI framework
This is the core of a small SPI framework, implementing the model of a
queue of messages which complete asynchronously (with thin synchronous
wrappers on top).
  - It's still less than 2KB of ".text" (ARM).  If there's got to be a
    mid-layer for something so simple, that's the right size budget.  :)
  - The guts use board-specific SPI device tables to build the driver
    model tree.  (Hardware probing is rarely an option.)
  - This version of Kconfig includes no drivers.  At this writing there
    are two known master controller drivers (PXA/SSP, OMAP MicroWire)
    and three protocol drivers (CS8415a, ADS7846, DataFlash) with LKML
    mentions of other drivers in development.
  - No userspace API.  There are several implementations to compare.
    Implement them like any other driver, and bind them with sysfs.
The changes from last version posted to LKML (on 11-Nov-2005) are minor,
and include:
  - One bugfix (removes a FIXME), with the visible effect of making device
    names be "spiB.C" where B is the bus number and C is the chipselect.
  - The "caller provides DMA mappings" mechanism now has kerneldoc, for
    DMA drivers that want to be fancy.
  - Hey, the framework init can be subsys_init.  Even though board init
    logic fires earlier, at arch_init ... since the framework init is
    for driver support, and the board init support uses static init.
  - Various additional spec/doc clarifications based on discussions
    with other folk.  It adds a brief "thank you" at the end, for folk
    who've helped nudge this framework into existence.
As I've said before, I think that "protocol tweaking" is the main support
that this driver framework will need to evolve.
From: Mark Underwood <basicmark@yahoo.com>
  Update the SPI framework to remove a potential priority inversion case by
  reverting to kmalloc if the pre-allocated DMA-safe buffer isn't available.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
											
										 
											2006-01-08 13:34:19 -08:00
										 |  |  | 
 |