/* Update sr_strerror()/sr_strerror_name() (error.c) upon changes! */
};
+/** Ternary return type for DMM/LCR/etc packet parser validity checks. */
+enum sr_valid_code {
+ SR_PACKET_INVALID = -1, /**< Certainly invalid. */
+ SR_PACKET_VALID = 0, /**< Certainly valid. */
+ SR_PACKET_NEED_RX = +1, /**< Need more RX data. */
+};
+
#define SR_MAX_CHANNELNAME_LEN 32
/* Handy little macros */
SR_T_DOUBLE_RANGE,
SR_T_INT32,
SR_T_MQ,
+ SR_T_UINT32,
/* Update sr_variant_type_get() (hwdriver.c) upon changes! */
};
/** The device can measure power. */
SR_CONF_POWERMETER,
+ /**
+ * The device can switch between multiple sources, e.g. a relay actuator
+ * or multiplexer.
+ */
+ SR_CONF_MULTIPLEXER,
+
/* Update sr_key_info_config[] (hwdriver.c) upon changes! */
/*--- Driver scan options -------------------------------------------*/
*/
SR_CONF_FORCE_DETECT,
+ /**
+ * Override builtin probe names from user specs.
+ *
+ * Users may want to override the names which are assigned to
+ * probes during scan (these usually match the vendor's labels
+ * on the device). This avoids the interactive tedium of
+ * changing channel names after device creation and before
+ * protocol decoder attachment. Think of IEEE488 recorders or
+ * parallel computer bus loggers. The scan option eliminates
+ * the issue of looking up previously assigned names before
+ * renaming a channel (see sigrok-cli -C), which depends on
+ * the device as well as the application, and is undesirable.
+ * The scan option is limited to those drivers which implement
+ * support for it, but works identically across those drivers.
+ *
+ * The value is a string, either a comma separated list of
+ * probe names, or an alias for a typical set of names.
+ */
+ SR_CONF_PROBE_NAMES,
+
/* Update sr_key_info_config[] (hwdriver.c) upon changes! */
/*--- Device (or channel group) configuration -----------------------*/