IOCTL_NFCSE_SET_CARD_EMULATION_MODE - NtDoc

Native API online documentation, based on the System Informer (formerly Process Hacker) phnt headers
// nfcsedev.h

// CTL_CODE(0x0022, 0x203, METHOD_BUFFERED, FILE_ANY_ACCESS)
#define IOCTL_NFCSE_SET_CARD_EMULATION_MODE 0x0022080C
View the official Windows Driver Kit DDI reference

NtDoc

No description available.

Windows Driver Kit DDI reference (ni-nfcsedev-ioctl_nfcse_set_card_emulation_mode)

IOCTL_NFCSE_SET_CARD_EMULATION_MODE IOCTL

Description

The IOCTL_NFCSE_SET_CARD_EMULATION_MODE control code sets whether the specified secure element is exposed in card emulation mode. When a secure element is “exposed” as card emulation, it means when the device is brought to an external reader that secure element can be accessed by the reader. The IOCTL is issued on a file handle opened with a relative filename ‘SEManage’. The driver MUST grant exclusive access to the client to manage card emulation mode, that is, subsequent calls to open a file handle using relative filename ‘SEManage’ will fail with STATUS_ACCESS_DENIED until the client with exclusive access closes its file handle.

Parameters

Major code

Input buffer

SECURE_ELEMENT_SET_CARD_EMULATION_MODE_INFO structure.

Input buffer length

Output buffer

None

Output buffer length

Input/output buffer

Input/output buffer length

Status block

Irp->IoStatus.Status is set to STATUS_SUCCESS if the request is successful. Possible error codes are:

Return Code Description
STATUS_INVALID_PARAMETER If the secure element GUID is invalid or output buffer is non-zero.
STATUS_INVALID_DEVICE_STATE If the IOCTL is sent on a handle other than with the relative name 'SEManage'.

Remarks

The following are requirements that the driver must adhere to.