diff --git a/data/conf.d/00-default.cfg b/data/conf.d/00-default.cfg
index 495cec09..abc6dd35 100644
--- a/data/conf.d/00-default.cfg
+++ b/data/conf.d/00-default.cfg
@@ -47,6 +47,7 @@ sonames=libbd_part.so.3
 
 [smart]
 sonames=libbd_smart.so.3;libbd_smartmontools.so.3
+# sonames=libbd_smartmontools.so.3;libbd_smart.so.3
 
 [swap]
 sonames=libbd_swap.so.3
diff --git a/src/plugins/smart/smart-common.c b/src/plugins/smart/smart-common.c
index a43415ef..9c054c46 100644
--- a/src/plugins/smart/smart-common.c
+++ b/src/plugins/smart/smart-common.c
@@ -130,16 +130,30 @@
  *
  * ## Device type detection, multipath #
  *
- * There's a big difference in how a drive is accessed. While libatasmart performs
- * essentially no device type detection and sends a I/O request right away
- * (with usual error handling), `smartctl` implements a logic to determine which
- * protocol to use, supporting various passthrough mechanisms and interface bridges.
- * Such detection is not always reliable though, having known issues with `dm-multipath`
- * for example. For this case most plugin functions provide the `'extra'` argument
- * allowing consumers to provide specific arguments such as `'--device=' for device
- * type override`. This is only supported by the smartmontools plugin and ignored
- * by the libatasmart plugin.
- *
+ * There's a big difference in how a drive is accessed. While `libatasmart` performs
+ * only very basic device type detection based on parent subsystem as retrieved from
+ * the udev database, `smartctl` implements logic to determine which protocol to use,
+ * supporting variety of passthrough mechanisms and interface bridges. Such detection
+ * is not always reliable though, having known issues with `dm-multipath` for example.
+ *
+ * For this case most plugin functions consume the `extra` argument allowing
+ * callers to specify arguments such as `--device=` for device type override. This
+ * is only supported by the smartmontools plugin and ignored by the libatasmart
+ * plugin.
+ *
+ * As a well kept secret libatasmart has historically supported device type override
+ * via the `ID_ATA_SMART_ACCESS` udev property. There's no public C API for this and
+ * libblockdev generally tends to avoid any udev interaction, leaving the burden
+ * to callers.
+ *
+ * Valid values for this property include `auto`, `linux-ide`, `sat16`, `sat12`,
+ * `sunplus`, `jmicron`.
+ *
+ * A common example to override QEMU ATA device type, which often requires legacy
+ * IDE protocol:
+ * |[
+ * KERNEL=="sd*", ENV{ID_VENDOR}=="ATA", ENV{ID_MODEL}=="QEMU_HARDDISK", ENV{ID_ATA}=="1", ENV{ID_ATA_SMART_ACCESS}="linux-ide"
+ * ]|
  */
 
 /**