For KL MCUs, rename up_spiinitialize to kl_spibus_initialize

This commit is contained in:
Gregory Nutt 2016-01-26 16:19:50 -06:00
parent 57909612d8
commit 77cb9f1729
11 changed files with 32 additions and 32 deletions

View File

@ -103,14 +103,14 @@
****************************************************************************************************/
/****************************************************************************************************
* Name: kl_spiinitialize
* Name: kl_spidev_initialize
*
* Description:
* Called to configure SPI chip select GPIO pins for the Freedom KL25Z board.
*
****************************************************************************************************/
void weak_function kl_spiinitialize(void);
void weak_function kl_spidev_initialize(void);
/****************************************************************************************************
* Name: kl_usbinitialize

View File

@ -272,7 +272,7 @@ int adxl345_archinitialize(int minor)
/* Get an instance of the I2C interface */
dev = up_spiinitialize(CONFIG_ADXL345_SPIDEV);
dev = kl_spibus_initialize(CONFIG_ADXL345_SPIDEV);
if (!dev)
{
sndbg("Failed to initialize SPI bus %d\n", CONFIG_ADXL345_SPIDEV);

View File

@ -73,13 +73,13 @@
void kl_boardinitialize(void)
{
/* Configure SPI chip selects if 1) SPI is not disabled, and 2) the weak function
* kl_spiinitialize() has been brought into the link.
* kl_spidev_initialize() has been brought into the link.
*/
#if defined(CONFIG_KL_SPI0) || defined(CONFIG_KL_SPI1)
if (kl_spiinitialize)
if (kl_spidev_initialize)
{
kl_spiinitialize();
kl_spidev_initialize();
}
#endif

View File

@ -78,14 +78,14 @@
****************************************************************************/
/****************************************************************************
* Name: kl_spiinitialize
* Name: kl_spidev_initialize
*
* Description:
* Called to configure SPI chip select GPIO pins for the FRDM-KL25Z board.
*
****************************************************************************/
void weak_function kl_spiinitialize(void)
void weak_function kl_spidev_initialize(void)
{
/* Configure SPI0 chip selects */
@ -114,7 +114,7 @@ void weak_function kl_spiinitialize(void)
* These external functions must be provided by board-specific logic. They
* are implementations of the select, status, and cmddata methods of the SPI
* interface defined by struct spi_ops_s (see include/nuttx/spi/spi.h). All
* other methods including up_spiinitialize()) are provided by common
* other methods including kl_spibus_initialize()) are provided by common
* Kinetis logic. To use this common SPI logic on your board:
*
* 1. Provide logic in kl_boardinitialize() to configure SPI chip select
@ -127,9 +127,9 @@ void weak_function kl_spiinitialize(void)
* kl_spi[n]cmddata() functions in your board-specific logic. These
* functions will perform cmd/data selection operations using GPIOs in
* the way your board is configured.
* 3. Add a call to up_spiinitialize() in your low level application
* 3. Add a call to kl_spibus_initialize() in your low level application
* initialization logic
* 4. The handle returned by up_spiinitialize() may then be used to bind
* 4. The handle returned by kl_spibus_initialize() may then be used to bind
* the SPI driver to higher level logic (e.g., calling
* mmcsd_spislotinitialize(), for example, will bind the SPI driver to
* the SPI MMC/SD driver).

View File

@ -301,7 +301,7 @@ int wireless_archinitialize(size_t max_rx_size)
/* Get an instance of the SPI interface */
spi = up_spiinitialize(CONFIG_CC3000_SPIDEV);
spi = kl_spibus_initialize(CONFIG_CC3000_SPIDEV);
if (!spi)
{
idbg("Failed to initialize SPI bus %d\n", CONFIG_CC3000_SPIDEV);

View File

@ -102,14 +102,14 @@
****************************************************************************************************/
/****************************************************************************************************
* Name: kl_spiinitialize
* Name: kl_spidev_initialize
*
* Description:
* Called to configure SPI chip select GPIO pins for the Freedom KL26Z board.
*
****************************************************************************************************/
void weak_function kl_spiinitialize(void);
void weak_function kl_spidev_initialize(void);
/****************************************************************************************************
* Name: kl_usbinitialize

View File

@ -72,13 +72,13 @@
void kl_boardinitialize(void)
{
/* Configure SPI chip selects if 1) SPI is not disabled, and 2) the weak function
* kl_spiinitialize() has been brought into the link.
* kl_spidev_initialize() has been brought into the link.
*/
#if defined(CONFIG_KL_SPI0) || defined(CONFIG_KL_SPI1)
if (kl_spiinitialize)
if (kl_spidev_initialize)
{
kl_spiinitialize();
kl_spidev_initialize();
}
#endif

View File

@ -78,14 +78,14 @@
****************************************************************************/
/****************************************************************************
* Name: kl_spiinitialize
* Name: kl_spidev_initialize
*
* Description:
* Called to configure SPI chip select GPIO pins for the FRDM-KL26Z board.
*
****************************************************************************/
void weak_function kl_spiinitialize(void)
void weak_function kl_spidev_initialize(void)
{
/* Configure SPI0 chip selects */
@ -105,7 +105,7 @@ void weak_function kl_spiinitialize(void)
* These external functions must be provided by board-specific logic. They
* are implementations of the select, status, and cmddata methods of the SPI
* interface defined by struct spi_ops_s (see include/nuttx/spi/spi.h). All
* other methods including up_spiinitialize()) are provided by common
* other methods including kl_spibus_initialize()) are provided by common
* Kinetis logic. To use this common SPI logic on your board:
*
* 1. Provide logic in kl_boardinitialize() to configure SPI chip select
@ -118,9 +118,9 @@ void weak_function kl_spiinitialize(void)
* kl_spi[n]cmddata() functions in your board-specific logic. These
* functions will perform cmd/data selection operations using GPIOs in
* the way your board is configured.
* 3. Add a call to up_spiinitialize() in your low level application
* 3. Add a call to kl_spibus_initialize() in your low level application
* initialization logic
* 4. The handle returned by up_spiinitialize() may then be used to bind
* 4. The handle returned by kl_spibus_initialize() may then be used to bind
* the SPI driver to higher level logic (e.g., calling
* mmcsd_spislotinitialize(), for example, will bind the SPI driver to
* the SPI MMC/SD driver).

View File

@ -84,13 +84,13 @@ void kl_boardinitialize(void)
#endif
/* Configure SPI chip selects if 1) SPI is not disabled, and 2) the weak function
* kl_spiinitialize() has been brought into the link.
* kl_spidev_initialize() has been brought into the link.
*/
#if defined(CONFIG_KL_SPI0) || defined(CONFIG_KL_SPI1)
if (kl_spiinitialize)
if (kl_spidev_initialize)
{
kl_spiinitialize();
kl_spidev_initialize();
}
#endif

View File

@ -78,14 +78,14 @@
****************************************************************************/
/****************************************************************************
* Name: kl_spiinitialize
* Name: kl_spidev_initialize
*
* Description:
* Called to configure SPI chip select GPIO pins for the FRDM-KL25Z board.
*
****************************************************************************/
void weak_function kl_spiinitialize(void)
void weak_function kl_spidev_initialize(void)
{
/* Configure SPI0 chip selects */
@ -105,7 +105,7 @@ void weak_function kl_spiinitialize(void)
* These external functions must be provided by board-specific logic. They
* are implementations of the select, status, and cmddata methods of the SPI
* interface defined by struct spi_ops_s (see include/nuttx/spi/spi.h). All
* other methods including up_spiinitialize()) are provided by common
* other methods including kl_spibus_initialize()) are provided by common
* Kinetis logic. To use this common SPI logic on your board:
*
* 1. Provide logic in kl_boardinitialize() to configure SPI chip select
@ -118,9 +118,9 @@ void weak_function kl_spiinitialize(void)
* kl_spi[n]cmddata() functions in your board-specific logic. These
* functions will perform cmd/data selection operations using GPIOs in
* the way your board is configured.
* 3. Add a call to up_spiinitialize() in your low level application
* 3. Add a call to kl_spibus_initialize() in your low level application
* initialization logic
* 4. The handle returned by up_spiinitialize() may then be used to bind
* 4. The handle returned by kl_spibus_initialize() may then be used to bind
* the SPI driver to higher level logic (e.g., calling
* mmcsd_spislotinitialize(), for example, will bind the SPI driver to
* the SPI MMC/SD driver).

View File

@ -70,14 +70,14 @@
****************************************************************************/
/****************************************************************************
* Name: kl_spiinitialize
* Name: kl_spidev_initialize
*
* Description:
* Called to configure SPI chip select GPIO pins for the Freedom KL25Z board.
*
****************************************************************************/
void weak_function kl_spiinitialize(void);
void weak_function kl_spidev_initialize(void);
/****************************************************************************
* Name: kl_led_initialize