Skip to main content
The QSH-exposed APIs are called QSH client APIs for applications. The client applications interact with the QSH framework available on the low-power processor. The following figure shows the detailed breakdown and usage of the QSH client APIs:
Figure : QSH client API workflow

Figure: QSH client API workflow

The following list describes the QSH client APIs:
  • getSession(): To interact with the QSH, the sensor application client must create an interface session by invoking the getSession() API. Successful creation of the interface session returns an ISession* object to the client.
  • open(), close(), setCallback(), and sendRequest(): The interface that getSession() API creates operates on a once_per_session basis. This interface allows the client application to use the QSH client APIs, such as open(), close(), setCallback(), and sendRequest(), until the session is explicitly deleted using the close() and delete() APIs. After the interface session establishes, the client application or the client code can open a sensor session by calling the open() API. Similar to getSession(), the open() API is also invoked on a once_per_session basis. The setCallback() and sendRequest() APIs are invoked once for a specified SUID.
Next steps