{"id":3889,"date":"2020-11-26T06:08:55","date_gmt":"2020-11-26T06:08:55","guid":{"rendered":"http:\/\/fastbitlab.com\/?p=3889"},"modified":"2023-09-05T14:45:07","modified_gmt":"2023-09-05T09:15:07","slug":"driver-api-requirements-and-user-configurable-items","status":"publish","type":"post","link":"https:\/\/fastbitlab.com\/blog\/driver-api-requirements-and-user-configurable-items\/","title":{"rendered":"STM32 I2C Lecture 7: I2C driver API requirements"},"content":{"rendered":"
\n
\n
\n
\n

 <\/p>\n<\/div>\n

\n

I2C driver API requirements<\/span><\/h1>\n
\n
\n
\n
\n<\/div>\n<\/div>\n<\/div>\n

 <\/p>\n

In this article, let\u2019s discuss the driver API requirements and user-configurable items for I2C peripherals.<\/span><\/p>\n

<\/div>\n
\"I2C
  Figure 1. Driver API requirements for I2C peripherals.<\/span><\/figcaption><\/figure>\n

 <\/p>\n

I2C driver APIs<\/b>:<\/b><\/span><\/p>\n

I2C drivers should have I2C initialization APIs and separate APIs for I2C Master TX and I2C Master RX; because the master has to initiate the start condition, address phase, etc. <\/span><\/p>\n

Since the slave is not going to do all these things, there are separate APIs for I2C Slave TX and I2C Slave RX. <\/span>There is a separate API for master and slave to transmit and receive data. That\u2019s why I2C Master TX, I2C Master RX, I2C Slave TX, and I2C Slave RX are created as shown in Figure 1.<\/span><\/p>\n

There are some interrupt handling APIs such as I2C error interrupt handling and I2C event interrupt handling that has to be supported. <\/span><\/p>\n

Apart from this, you have to keep the peripheral control, the peripheral clock control, peripheral enable\/ disable, and lots of other peripheral control APIs.<\/span><\/p>\n

 <\/p>\n

\"I2C
 Figure 2. Configurable items for user application.<\/span><\/figcaption><\/figure>\n

 <\/p>\n

Configurable items for user application:<\/b><\/span><\/p>\n

The configurable items for the user application are as shown in Figure 2.<\/span><\/p>\n