Device

Detailed Description

Manages NvMediaDevice objects, which are the root of the Nvmedia object system.

A caller can use an NvMediaDevice object to create objects of all other types. See the sections describing the other object types for details on object creation.

Typedefs
typedef void	NvMediaDevice
	An opaque handle representing an NvMediaDevice object. More...

Functions
NvMediaDevice *	NvMediaDeviceCreate (void) NVM_DEPRECATED_MSG("Removed in future release")
	Creates an instance of the NvMediaDevice structure. More...
void	NvMediaDeviceDestroy (NvMediaDevice *device) NVM_DEPRECATED_MSG("Removed in future release")
	Destroys an NvMediaDevice instance. More...

Typedef Documentation

NvMediaDevice

typedef void NvMediaDevice

An opaque handle representing an NvMediaDevice object.

Definition at line 228 of file nvmedia_core.h.

Function Documentation

NvMediaDeviceCreate()

NvMediaDevice* NvMediaDeviceCreate

(

void

)

Creates an instance of the NvMediaDevice structure.

Memory will be allocated for a NvMediaDevice structure and private SOC specific NvMedia information will be saved in the created NvMediaDevice.

Return values

NvMediaDevice	Valid non-NULL pointer to the new device if successful
NULL	incase of failure

Usage considerations

• Allowed context for the API call
  • Interrupt handler: No
  • Signal handler: No
  • Thread-safe: Yes, with the following conditions:
    • Users can create different contexts on different threads.
    • However, once created each context should not be used in different threads at the same time.
  • Re-entrant: No
  • Async/Sync: Sync
• Required privileges: None
• API group
  • Init: Yes
  • Runtime: No
  • De-Init: No

NvMediaDeviceDestroy()

void NvMediaDeviceDestroy

(

NvMediaDevice *

device

)

Destroys an NvMediaDevice instance.

Memory allocated for NvMediaDevice using NvMediaDeviceCreate will be freed and the instance of NvMediaDevice structure will be destroyed.

Parameters

[in]

device

A valid non-NULL pointer to the device to be destroyed.

Usage considerations

• Allowed context for the API call
  • Interrupt handler: No
  • Signal handler: No
  • Thread-safe: Yes, with the following conditions:
    • Users can destroy different contexts on different threads.
  • Re-entrant: No
  • Async/Sync: Sync
• Required privileges: None
• API group
  • Init: No
  • Runtime: No
  • De-Init: Yes