Changes between Version 20 and Version 21 of DeviceDrivers

Timestamp:

2011-11-14T21:51:46Z (12 years ago)

Author:

Jiri Svoboda

Comment:

ddf_fun_… call stubs

DeviceDrivers

@@ -37 +37 @@
 
 There is no formal distinction between a bus (nexus) driver and a leaf (device) driver. All drivers consume device nodes and produce function nodes. There are two type of functions (function nodes), ''inner functions'' and ''exposed functions''. Inner functions are functions internal to the device graph and DDF will attempt to attach child devices/drivers under these functions. Exposed functions are meant to be consumed by clients external to the DDF (such as applications or non-DDF servers) and the DDF will expose them as services via the Location Service.
+
+==== Device and Function Life Cycle ====
+
+'''TODO'''
 
 == DDF Driver Structure ==
@@ -144 +148 @@
 return ENOTSUP.
 
-== Device and Function Life Cycle ==
+=== Calls for Managing Functions ===
+
+DDF provides the driver with a set of calls to manage functions:
 
  * ddf_fun_create()
@@ -155 +161 @@
  * ddf_fun_offline()
 
+==== ddf_fun_create ====
+
+{{{
+ddf_fun_t *ddf_fun_create(ddf_dev_t *dev, fun_type_t ftype, const char *name)
+}}}
+
+==== ddf_fun_destroy ====
+
+{{{
+ddf_fun_t *ddf_fun_destroy(ddf_fun_t *fun)
+}}}
+
+==== ddf_fun_add_match_id ====
+
+{{{
+int ddf_fun_add_match_id(ddf_fun_t *fun, const char *match_id_str, int match_score)
+}}}
+
+==== ddf_fun_add_to_category ====
+
+{{{
+int ddf_fun_add_to_category(ddf_fun_t *fun, const char *cat_name)
+}}}
+
+==== ddf_fun_bind ====
+
+{{{
+int ddf_fun_bind(ddf_fun_t *fun)
+}}}
+
+==== ddf_fun_unbind ====
+
+{{{
+int ddf_fun_unbind(ddf_fun_t *fun)
+}}}
+
+==== ddf_fun_online ====
+
+{{{
+int ddf_fun_online(ddf_fun_t *fun)
+}}}
+
+==== ddf_fun_offline ====
+
+{{{
+int ddf_fun_offline(ddf_fun_t *fun)
+}}}
+
 == Soft State Management ==