SVR5

mdi_hw_resumed(D3mdi)

mdi_hw_resumed -- notify dlpi module that hardware is resumed

Synopsis

   #include <sys/types.h>
   #include <sys/stream.h>
   #include <sys/mdi.h>
   #include <sys/confmgr.h>
   #include <sys/ddi.h>
   
   int mdi_hw_resumed(queue_t *q, rm_key_t rmkey)

Description

mdi_hw_resumed( ) notifies the dlpi module that the hardware has been resumed.

Arguments

q: pointer to the upstream queue to the dlpi module.
rmkey: affected resource manager key.

Return values

mdi_hw_resumed( ) returns 0 on success, or an appropriate error number from those listed on the errnos(D5) manual page.

Usage

This function is used in the CFG_RESUME subfunction to the config(D2mdi) entry point for hotplug-aware MDI drivers.

Context and synchronization

Blockable or interrupt context.

Driver-defined basic locks, read/write locks, and sleep locks may not be held across calls to this function.

The caller cannot have the stream frozen (see freezestr(D3str)) when calling this function.

Hardware applicability

All

Version applicability

mdi: 2, 2.1

Differences between versions

This function is not supported in MDI on SCO OpenServer systems.

References

config(D2mdi), mdi_hw_suspended(D3mdi)

``Hotplug devices'' in HDK Technical Reference

Examples

   int
   e3Dconfig(cfg_func_t func, void *idata, rm_key_t rmkey)
   {
      int ret;
      e3Ddev_t *dev=idata;
   
      switch(func) {
         case CFG_RESUME:
         /* Always call mdi_hw_resumed to tell the stack to resume
          * frames, as we don't know if user a) never issued the
          * BIND_REQ before the suspend or b) issued the BIND_REQ
          * successfully, got the suspend, then closed the device
          * while we were suspended.
          */
         if ((ret=mdi_hw_resumed(dev->ex_up_queue, rmkey)) != 0) {
            return(ret);
         }
      }
   }