In the Hardware Driver Foundation \(HDF\), the Serial Peripheral Interface \(SPI\) uses the independent service mode for API adaptation. In this mode, each device independently publishes a device service to handle external access requests. After receiving an access request from an API, the device manager extracts the parameters in the request to call the internal method of the target device. In the independent service mode, the service management capabilities of the HDFDeviceManager can be directly used. However, you need to configure a device node for each device, which increases the memory usage.
Serial Peripheral Interface (SPI) is a serial bus specification used for high-speed, full-duplex, and synchronous communication. In the Hardware Driver Foundation (HDF), the SPI module uses the independent service mode for API adaptation. In this mode, each device independently publishes a service to process external access requests. When receiving an access request, the HDF DeviceManager extracts parameters from the request to call the internal APIs of the target device. In the independent service mode, the HDF DeviceManager provides service management capabilities. However, you need to configure a node for each device, which increases memory usage.
**Figure 1** Independent service mode<aname="fig666465313303"></a>
| Transfer | **cntlr**: structure pointer to the SPI controller at the core layer.<br>**msg**: structure pointer to the SPI message.<br>**count**: number of messages. The value is of the uint32_t type.| HDF_STATUS| Transfers messages.|
</th>
| SetCfg | **cntlr**: structure pointer to the SPI controller at the core layer.<br>**cfg**: structure pointer to the SPI attributes.| HDF_STATUS| Sets SPI controller attributes.|
| GetCfg | **cntlr**: structure pointer to the SPI controller at the core layer.<br>**cfg**: structure pointer to the SPI attributes.| HDF_STATUS| Obtains SPI controller attributes.|
</th>
| Open | **cntlr**: structure pointer to the SPI controller at the core layer.| HDF_STATUS| Opens an SPI device.|
<tdclass="cellrowborder"valign="top"width="25%"headers="mcps1.2.5.1.2 "><pid="p0671913132514"><aname="p0671913132514"></a><aname="p0671913132514"></a><strongid="b19675134258"><aname="b19675134258"></a><aname="b19675134258"></a>cntlr</strong>: structure pointer to the SPI controller at the core layer.</p>
<pid="p192109186258"><aname="p192109186258"></a><aname="p192109186258"></a><strongid="b1921051810258"><aname="b1921051810258"></a><aname="b1921051810258"></a>msg</strong>: structure pointer to the SPI message.</p>
<pid="p6168736173213"><aname="p6168736173213"></a><aname="p6168736173213"></a><strongid="b92627310191"><aname="b92627310191"></a><aname="b92627310191"></a>count</strong>: number of messages. The value is of the uint32_t type.</p>
<tdclass="cellrowborder"valign="top"width="25%"headers="mcps1.2.5.1.2 "><pid="p242632402513"><aname="p242632402513"></a><aname="p242632402513"></a><strongid="b742642452513"><aname="b742642452513"></a><aname="b742642452513"></a>cntlr</strong>: structure pointer to the SPI controller at the core layer.</p>
<pid="p11168163643217"><aname="p11168163643217"></a><aname="p11168163643217"></a><strongid="b1283910558207"><aname="b1283910558207"></a><aname="b1283910558207"></a>cfg</strong>: structure pointer to the SPI attributes.</p>
<tdclass="cellrowborder"valign="top"width="25%"headers="mcps1.2.5.1.2 "><pid="p9698153182520"><aname="p9698153182520"></a><aname="p9698153182520"></a><strongid="b19698131162510"><aname="b19698131162510"></a><aname="b19698131162510"></a>cntlr</strong>: structure pointer to the SPI controller at the core layer.</p>
<pid="p3168936133218"><aname="p3168936133218"></a><aname="p3168936133218"></a><strongid="b11555148182113"><aname="b11555148182113"></a><aname="b11555148182113"></a>cfg</strong>: structure pointer to the SPI attributes.</p>
<tdclass="cellrowborder"valign="top"width="25%"headers="mcps1.2.5.1.2 "><pid="p181697365327"><aname="p181697365327"></a><aname="p181697365327"></a><strongid="b1876822162218"><aname="b1876822162218"></a><aname="b1876822162218"></a>cntlr</strong>: structure pointer to the SPI controller at the core layer. </p>
<tdclass="cellrowborder"valign="top"width="25.019999999999996%"headers="mcps1.2.5.1.4 "><pid="p1116963693218"><aname="p1116963693218"></a><aname="p1116963693218"></a>Enables the SPI.</p>
<tdclass="cellrowborder"valign="top"width="25%"headers="mcps1.2.5.1.2 "><pid="p31691936193210"><aname="p31691936193210"></a><aname="p31691936193210"></a><strongid="b16798152112239"><aname="b16798152112239"></a><aname="b16798152112239"></a>cntlr</strong>: structure pointer to the SPI controller at the core layer. </p>
<tdclass="cellrowborder"valign="top"width="25.019999999999996%"headers="mcps1.2.5.1.4 "><pid="p1169636103220"><aname="p1169636103220"></a><aname="p1169636103220"></a>Disables the SPI.</p>
</td>
</tr>
</tbody>
</table>
## How to Develop<a name="section799667984152909"></a>
The SPI module adaptation involves the following steps:
The SPI module adaptation involves the following steps:
1. Instantiate the driver entry.
1. Instantiate the driver entry.
- Instantiate the **HdfDriverEntry** structure.
- Instantiate the **HdfDriverEntry** structure.
- Call **HDF\_INIT** to register the **HdfDriverEntry** instance with the HDF.
- Call **HDF_INIT** to register the **HdfDriverEntry** instance with the HDF.
2. Configure attribute files.
2. Configure attribute files.
- Add the **deviceNode** information to the **device\_info.hcs** file.
- Add the **deviceNode** information to the **device_info.hcs** file.
-\(Optional\) Add the **spi\_config.hcs** file.
- (Optional) Add the **spi_config.hcs** file.
3. Instantiate the SPI controller object.
3. Instantiate the SPI controller object.
- Initialize **SpiCntlr**.
- Initialize **SpiCntlr**.
- Instantiate **SpiCntlrMethod** in the **SpiCntlr** object.
- Instantiate **SpiCntlrMethod** in the **SpiCntlr** object.
For details, see [Available APIs](#section752964871810).
> For details about the functions in **SpiCntlrMethod**, see [Available APIs](#available-apis).
4.\(Optional\) Debug the driver.
4. Debug the driver.<br>
For new drivers, verify the basic functions, such as the SPI control status and response to interrupts.
(Optional) For new drivers, verify the basic functions, such as the SPI status control and response to interrupts.
## Development Example<a name="section956157227152909"></a>
## Development Example
The following uses **spi\_hi35xx.c** as an example to present the contents that need to be provided by the vendor to implement device functions.
The following uses **spi_hi35xx.c** as an example to present the information required for implementing device functions.
1. Instantiate the driver entry. The driver entry must be a global variable of the **HdfDriverEntry** type \(defined in **hdf\_device\_desc.h**\), and the value of **moduleName** must be the same as that in **device\_info.hcs**. In the HDF, the start address of each **HdfDriverEntry** object of all loaded drivers is collected to form a segment address space similar to an array for the upper layer to invoke.
1. Instantiate the driver entry.<br/>The driver entry must be a global variable of the **HdfDriverEntry** type (defined in **hdf_device_desc.h**), and the value of **moduleName** must be the same as that in **device_info.hcs**. In the HDF framework, the start address of each **HdfDriverEntry** object of all loaded drivers is collected to form a segment address space similar to an array for the upper layer to invoke.
Generally, the HDF calls the **Bind** function and then the **Init** function to load a driver. If **Init** fails to be called, the HDF calls **Release** to release driver resources and exit.
Generally, HDF calls the **Bind** function and then the **Init** function to load a driver. If **Init** fails to be called, HDF calls **Release** to release driver resources and exit.
SPI driver entry example:
- SPI driver entry reference
```
```
struct HdfDriverEntry g_hdfSpiDevice = {
struct HdfDriverEntry g_hdfSpiDevice = {
.moduleVersion = 1,
.moduleVersion = 1,
.moduleName = "HDF_PLATFORM_SPI",// (Mandatory) The value must be the same as that of moduleName in the .hcs file.
.moduleName = "HDF_PLATFORM_SPI",// (Mandatory) The value must be the same as that of moduleName in the .hcs file.
.Bind = HdfSpiDeviceBind, // See the Bind function.
.Bind = HdfSpiDeviceBind, // See the Bind function.
.Init = HdfSpiDeviceInit, // See the Init function.
.Init = HdfSpiDeviceInit, // See the Init function.
.Release = HdfSpiDeviceRelease, //See the Release function.
.Release = HdfSpiDeviceRelease, //See the Release function.
};
};
// Call HDF_INIT to register the driver entry with the HDF.
// Call HDF_INIT to register the driver entry with the HDF.
HDF_INIT(g_hdfSpiDevice);
HDF_INIT(g_hdfSpiDevice);
```
```
2. Add the **deviceNode** information to the **device_info.hcs** file and configure the device attributes in the **spi_config.hcs** file.
2. Add the **deviceNode** information to the **device\_info.hcs** file and configure the device attributes in the **spi\_config.hcs** file. The **deviceNode** information is related to registration of the driver entry. The device attribute values are closely related to the default values or value ranges of the **SpiCntlr** members at the core layer.
The **deviceNode** information is related to registration of the driver entry. The device attribute values are closely related to the default values or value ranges of the **SpiCntlr** members at the core layer.
In this example, there is only one SPI controller. If there are multiple SPI controllers, you need to add the **deviceNode** information to the **device\_info** file and add the corresponding device attributes to the **spi\_config** file.
In this example, there is only one SPI controller. If there are multiple SPI controllers, you need to add the **deviceNode** information to the **device_info** file and add the corresponding device attributes to the **spi_config** file for each controller.
- **device\_info.hcs** configuration reference
-**device_info.hcs** configuration example
```
root {
device_info {
```
match_attr = "hdf_manager";
root {
platform :: host {
device_info {
hostName = "platform_host";
match_attr = "hdf_manager";
priority = 50;
platform :: host {
device_spi :: device {// Configure an HDF device node for each SPI controller.
hostName = "platform_host";
device0 :: deviceNode {
priority = 50;
policy = 1;
device_spi :: device { // Configure an HDF device node for each SPI controller.
priority = 60;
device0 :: deviceNode {
permission = 0644;
policy = 1;
moduleName = "HDF_PLATFORM_SPI";
priority = 60;
serviceName = "HDF_PLATFORM_SPI_0";
permission = 0644;
deviceMatchAttr = "hisilicon_hi35xx_spi_0";
moduleName = "HDF_PLATFORM_SPI";
}
serviceName = "HDF_PLATFORM_SPI_0";
device1 :: deviceNode {
deviceMatchAttr = "hisilicon_hi35xx_spi_0";
policy = 1;
}
priority = 60;
device1 :: deviceNode {
permission = 0644;
policy = 1;
moduleName = "HDF_PLATFORM_SPI"; // (Mandatory) Driver name, which must be the same as that of moduleName in the driver entry structure.
priority = 60;
serviceName = "HDF_PLATFORM_SPI_1"; // (Mandatory) Unique name of the service published by the driver
permission = 0644;
deviceMatchAttr = "hisilicon_hi35xx_spi_1";// The value must be the same as that of match_attr in the .hcs file.
moduleName = "HDF_PLATFORM_SPI"; // (Mandatory) Driver name, which must be the same as that of moduleName in the driver entry structure.
}
serviceName = "HDF_PLATFORM_SPI_1"; // (Mandatory) Unique name of the service published by the driver.
...
deviceMatchAttr = "hisilicon_hi35xx_spi_1";// The value must be the same as that of match_attr in the .hcs file.
}
}
}
...
}
}
}
}
```
}
}
- **spi\_config.hcs** configuration reference
```
```
-**spi_config.hcs** configuration example
root {
platform {
spi_config {// Configure private data for each SPI controller.
```
template spi_controller {// Template configuration. In the template, you can configure the common parameters shared by service nodes.
root {
serviceName = "";
platform {
match_attr = "";
spi_config {// Configure private data for each SPI controller.
transferMode = 0; // Data transfer mode, which can be interrupt transfer (0), flow control transfer (1), or DMA transfer (2).
template spi_controller { // Template configuration. In the template, you can configure the common parameters shared by device nodes.
busNum = 0; // Bus number
serviceName = "";
clkRate = 100000000;
match_attr = "";
bitsPerWord = 8; // Bit width of the data transferred
transferMode = 0; // Data transfer mode. The value **0** indicates interrupt transfer, **1** indicates flow control transfer, and **2** indicates DMA transfer.
mode = 19; // SPI data input/output mode
busNum = 0; // Bus number.
maxSpeedHz = 0; // Maximum clock frequency
clkRate = 100000000;
minSpeedHz = 0; // Minimum clock frequency
bitsPerWord = 8 // Number of bits per word.
speed = 2000000; // Current message transfer speed
mode = 19; // SPI data input/output mode.
fifoSize = 256; // FIFO size
maxSpeedHz = 0; // Maximum clock frequency.
numCs = 1; // Chip select (CS) number
minSpeedHz = 0; // Minimum clock frequency.
regBase = 0x120c0000; // Used for address mapping.
speed = 2000000; // Current message transfer speed.
regBase = 0x120c1000; // (Mandatory) Used for address mapping.
//(Optional) Add nodes to the device_info.hcs file as required.
irqNum = 101; // (Mandatory) IRQ number.
}
}
}
...
}
//(Optional) Add nodes to the device_info.hcs file as required.
```
}
}
3. Initialize the **SpiCntlr** object at the core layer, including initializing the vendor custom structure \(transferring parameters and data\), instantiating **SpiCntlrMethod**\(used to call underlying functions of the driver\) in **SpiCntlr**, and implementing the **HdfDriverEntry** member functions \(**Bind**, **Init**, and **Release**\).
}
- Custom structure reference
```
To the driver, the custom structure carries parameters and data. The values in the **spi\_config.hcs** file are read by HDF, and the structure members are initialized through **DeviceResourceIface**. Some important values, such as the device number and bus number, are also passed to the object at the core layer.
3. Initialize the **SpiCntlr** object at the core layer, including defining a custom structure (to pass parameters and data) and implementing the **HdfDriverEntry** member functions (**Bind**, **Init**, and **Release**) to instantiate **SpiCntlrMethod** in **SpiCntlr** (so that the underlying driver functions can be called).
- Defining a custom structure
```
struct Pl022 {// Corresponds to parameters in .hcs.
To the driver, the custom structure holds parameters and data. The **DeviceResourceIface** method provided by the HDF reads the values in the **spi_config.hcs** file to initialize the members in the custom structure and passes important parameters, such as the device number and bus number, to the **SpiCntlr** object at the core layer.
struct SpiCntlr *cntlr;
struct DListHead deviceList;
struct OsalSem sem;
```
volatile unsigned char *phyBase;
struct Pl022 {// Corresponds to parameters in .hcs.
volatile unsigned char *regBase;
struct SpiCntlr *cntlr;
uint32_t irqNum;
struct DListHead deviceList;
uint32_t busNum;
struct OsalSem sem;
uint32_t numCs;
volatile unsigned char *phyBase;
uint32_t curCs;
volatile unsigned char *regBase;
uint32_t speed;
uint32_t irqNum;
uint32_t fifoSize;
uint32_t busNum;
uint32_t clkRate;
uint32_t numCs;
uint32_t maxSpeedHz;
uint32_t curCs;
uint32_t minSpeedHz;
uint32_t speed;
uint32_t regCrg;
uint32_t fifoSize;
uint32_t clkEnBit;
uint32_t clkRate;
uint32_t clkRstBit;
uint32_t maxSpeedHz;
uint32_t regMiscCtrl;
uint32_t minSpeedHz;
uint32_t miscCtrlCsShift;
uint32_t regCrg;
uint32_t miscCtrlCs;
uint32_t clkEnBit;
uint16_t mode;
uint32_t clkRstBit;
uint8_t bitsPerWord;
uint32_t regMiscCtrl;
uint8_t transferMode;
uint32_t miscCtrlCsShift;
};
uint32_t miscCtrlCs;
uint16_t mode;
// SpiCntlr is the core layer controller structure. Its members are assigned with values by using the Init function.
uint8_t bitsPerWord;
struct SpiCntlr {
uint8_t transferMode;
struct IDeviceIoService service;
};
struct HdfDeviceObject *device;
uint32_t busNum;
// SpiCntlr is the core layer controller structure. The Init function assigns values to the members of SpiCntlr.
uint32_t numCs;
struct SpiCntlr {
uint32_t curCs;
struct IDeviceIoService service;
struct OsalMutex lock;
struct HdfDeviceObject *device;
struct SpiCntlrMethod *method;
uint32_t busNum;
struct DListHead list;
uint32_t numCs;
void *priv;
uint32_t curCs;
};
struct OsalMutex lock;
```
struct SpiCntlrMethod *method;
struct DListHead list;
- Instantiate the callback function structure **SpiCntlrMethod** in **SpiCntlr**. Other members are initialized by using the **Init** function.
void *priv;
};
```
```
// Example in spi_hi35xx.c: instantiate the hook.
struct SpiCntlrMethod g_method = {
- Instantiating **SpiCntlrMethod** in **SpiCntlr** (other members are initialized by **Init**)
.Transfer = Pl022Transfer,
.SetCfg = Pl022SetCfg,
.GetCfg = Pl022GetCfg,
```
.Open = Pl022Open,
// Example in spi_hi35xx.c: instantiate the hooks.
.Close = Pl022Close,
struct SpiCntlrMethod g_method = {
};
.Transfer = Pl022Transfer,
```
.SetCfg = Pl022SetCfg,
.GetCfg = Pl022GetCfg,
- Bind function
.Open = Pl022Open,
.Close = Pl022Close,
Input parameters:
};
```
**HdfDeviceObject**, an interface parameter exposed by the driver, contains the .hcs configuration file information.
-**Bind** function
Return values:
Input parameter:
HDF\_STATUS
**HdfDeviceObject**, an interface parameter exposed by the driver, contains the .hcs information.
Function description:
Return value:
Associates the **SpiCntlr** object with **HdfDeviceObject**.
cntlr->device = device; // Prerequisites for conversion between HdfDeviceObject and SpiCntlr.
```
device->service = &(cntlr->service); // Prerequisites for conversion between HdfDeviceObject and SpiCntlr.
(void)OsalMutexInit(&cntlr->lock); // Initialize the lock.
- Init function
DListHeadInit(&cntlr->list); // Add the corresponding nodes.
cntlr->priv = NULL;
Input parameters:
return cntlr;
}
**HdfDeviceObject**, an interface parameter exposed by the driver, contains the .hcs configuration file information.
```
Return values:
-**Init** function
HDF\_STATUS \(The following table lists some status. For details about other status, see **HDF\_STATUS** in the **/drivers/framework/include/utils/hdf\_base.h** file.\)
Input parameter:
**Table 2** Input parameters and return values of the init function
**HdfDeviceObject**, an interface parameter exposed by the driver, contains the .hcs information.
cntlr = SpiCntlrFromDevice(device); // Use service to forcibly convert HdfDeviceObject to SpiCntlr. For details about the value assignment, see the Bind function.
ret = SpiGetBaseCfgFromHcs(pl022, device->property); // Initialize busNum, numCs, speed, fifoSize, clkRate, mode, bitsPerWord, and transferMode.
{
...
int32_t ret;
ret = SpiGetRegCfgFromHcs(pl022, device->property); // Initialize regBase, phyBase, irqNum, regCrg, clkEnBit, clkRstBit, regMiscCtrl, miscCtrlCs, and miscCtrlCsShift.
struct SpiCntlr *cntlr = NULL;
...
...
// Calculate the frequencies corresponding to the maximum and minimum speeds.
cntlr = SpiCntlrFromDevice(device);// Forcibly convert HdfDeviceObject to SpiCntlr by using service. For details about the value assignment, see the Bind function.
DListHeadInit(&pl022->deviceList);// Initialize the DList linked list.
pl022->cntlr = cntlr; // Enable conversion between Pl022 and SpiCntlr.
No value is returned.
cntlr->priv = pl022; // Enable conversion between Pl022 and SpiCntlr.
cntlr->busNum = pl022->busNum; // Assign a value to busNum in SpiCntlr.
Function description:
cntlr->method = &g_method; // Connect to the SpiCntlrMethod instance.
...
Releases the memory and deletes the controller. This function assigns values to the **Release** function in the driver entry structure. If the HDF fails to call the **Init** function to initialize the driver, the **Release** function can be called to release driver resources. All forced conversion operations for obtaining the corresponding object can be successful only when the **Init** function has the value assignment operations.
ret = Pl022CreatAndInitDevice(pl022);
if (ret != 0) {
Pl022Release(pl022); // Release the Pl022 object if the initialization fails.
cntlr = SpiCntlrFromDevice(device); // Use service to forcibly convert HdfDeviceObject to SpiCntlr. For details about the value assignment, see the Bind function.
Pl022Remove((struct Pl022 *)cntlr->priv);// A forced conversion from SpiCntlr to Pl022 is involved.
}
**HdfDeviceObject**, an interface parameter exposed by the driver, contains the .hcs configuration file information.
SpiCntlrDestroy(cntlr); // Release the Pl022 object.
}
Return values:
```
–
Function description:
Releases the memory and deletes the controller. This function assigns a value to the **Release** API in the driver entry structure. When the HDF fails to call the **Init** function to initialize the driver, the **Release** function can be called to release driver resources. All forced conversion operations for obtaining the corresponding object can be successful only when the **Init** function has the corresponding value assignment operations.
cntlr = SpiCntlrFromDevice(device);// Forcibly convert HdfDeviceObject to SpiCntlr by using service. For details about the value assignment, see the Bind function.
