Fork us on GitHub Follow us on Facebook Follow us on Twitter

Changes between Version 17 and Version 18 of DeviceDrivers


Ignore:
Timestamp:
2011-11-14T21:25:17Z (8 years ago)
Author:
Jiri Svoboda
Comment:

fun_online, fun_offline

Legend:

Unmodified
Added
Removed
Modified
  • DeviceDrivers

    v17 v18  
    6767 * #include <ddf/driver.h>
    6868 * driver_t
    69  * driver_ops_t
    70    * dev_add
    71    * dev_remove
    72    * dev_gone
    73    * fun_online
    74    * fun_offline
     69 * driver_ops_t -- driver entry points
     70   * dev_add -- ask driver to take ownership of device
     71   * dev_remove -- ask driver to give up device
     72   * dev_gone -- device connectivity lost
     73   * fun_online -- ask driver to online function
     74   * fun_offline -- ask driver to offline function
    7575 * ddf_dev_ops_t
    7676
     
    119119software state associated with the device. If this entry point is not implemented, it should
    120120be either set to NULL or it should always return ENOTSUP.
     121
     122==== fun_online ====
     123{{{
     124int (*fun_online)(ddf_fun_t *fun)
     125}}}
     126This entry point is called by DDF to ask the driver to online a function. The driver must
     127online the function ''fun''. It may also online other functions, if necessary (in case the
     128function states are interlocked somehow). For many drivers this function will simply call
     129{{{ddf_fun_online(fun)}}}.
     130
     131If this entry point is not implemented, it should be either set to NULL or it should always
     132return ENOTSUP.
     133
     134==== fun_offline ====
     135{{{
     136int (*fun_offline)(ddf_fun_t *fun)
     137}}}
     138This entry point is called by DDF to ask the driver to offline a function. The driver must
     139offline the function ''fun''. It may also offline other functions, if necessary (in case the
     140function states are interlocked somehow). For many drivers this function will simply call
     141{{{ddf_fun_offline(fun)}}}.
     142
     143If this entry point is not implemented, it should be either set to NULL or it should always
     144return ENOTSUP.
    121145
    122146== Device and Function Life Cycle ==