From aa2ae3f26aad496d21b528819bc06c84968cc154 Mon Sep 17 00:00:00 2001 From: Gregory Nutt Date: Tue, 26 Jan 2016 16:25:50 -0600 Subject: [PATCH] For Kinetis MCUs, rename up_spiinitialize to kinetis_spibus_initialize --- arch/arm/src/kinetis/kinetis.h | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/arch/arm/src/kinetis/kinetis.h b/arch/arm/src/kinetis/kinetis.h index 1cd6cd47fb..f84dd226b8 100644 --- a/arch/arm/src/kinetis/kinetis.h +++ b/arch/arm/src/kinetis/kinetis.h @@ -590,7 +590,7 @@ void kinetis_clrpend(int irq); * 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 Kinetis logic. To use + * including kinetis_spibus_initialize()) are provided by common Kinetis logic. To use * this common SPI logic on your board: * * 1. Provide logic in kinetis_boardinitialize() to configure SPI chip select @@ -602,9 +602,9 @@ void kinetis_clrpend(int irq); * kinetis_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 kinetis_spibus_initialize() in your low level application * initialization logic - * 4. The handle returned by up_spiinitialize() may then be used to bind the + * 4. The handle returned by kinetis_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).