Skip to content

Latest commit

 

History

History
82 lines (57 loc) · 3.82 KB

nf-portcls-iportwavepci-notify.md

File metadata and controls

82 lines (57 loc) · 3.82 KB
UID title description old-location tech.root ms.date keywords ms.keywords req.header req.include-header req.target-type req.target-min-winverclnt req.target-min-winversvr req.kmdf-ver req.umdf-ver req.ddi-compliance req.unicode-ansi req.idl req.max-support req.namespace req.assembly req.type-library req.lib req.dll req.irql targetos req.typenames f1_keywords topic_type api_type api_location api_name
NF:portcls.IPortWavePci.Notify
IPortWavePci::Notify (portcls.h)
The Notify method notifies the port driver that an interrupt indicating the progress of the DMA pointer has occurred.
audio\iportwavepci_notify.htm
audio
05/08/2018
IPortWavePci::Notify
IPortWavePci interface [Audio Devices],Notify method, IPortWavePci.Notify, IPortWavePci::Notify, Notify, Notify method [Audio Devices], Notify method [Audio Devices],IPortWavePci interface, audio.iportwavepci_notify, audmp-routines_5b988b85-05d1-4a66-b04d-fdd21dcf0310.xml, portcls/IPortWavePci::Notify
portcls.h
Portcls.h
Universal
Any level
Windows
IPortWavePci::Notify
portcls/IPortWavePci::Notify
APIRef
kbSyntax
COM
portcls.h
IPortWavePci::Notify

IPortWavePci::Notify

-description

The Notify method notifies the port driver that an interrupt indicating the progress of the DMA pointer has occurred.

-parameters

-param ServiceGroup [in]

A pointer to the miniport driver's IServiceGroup object.

-remarks

Some miniport drivers call this method from an ISR in response to a hardware interrupt after having cleared the interrupt source. Other drivers call this method from a timer DPC that is scheduled to run at regular intervals. As a general rule, only drivers that manage a single render stream from KMixer should rely on hardware interrupts. Drivers that support DirectSound hardware acceleration should turn off hardware interrupts and use timer DPCs instead. For more information, see IPortWavePciStream::GetMapping.

Although the miniport driver is free to choose its own technique for determining when to call this method, this method should be called frequently enough to allow the port driver to fire pending position and clock events at regular intervals. Timing for this method is not as critical as it is for the IPortWaveCyclic::Notify method, however.

When an adapter driver installs an ISR, it submits a ServiceContext parameter along with the ISR's entry point (for details, see Providing ISR Context Information). When the interrupt occurs, the operating system calls the ISR and passes ServiceContext as a call parameter to the ISR. Although the meaning of the ServiceContext parameter is known only to the driver developer, it is typically a pointer to the miniport object. The ISR uses this pointer to access information about the miniport object.

The ServiceGroup parameter follows the reference-counting conventions for COM objects.

-see-also

IPortWaveCyclic::Notify

IPortWavePci

IPortWavePciStream::GetMapping

IServiceGroup