tree 2b833a4dabaccdd0b54b4206de448817c774ea3f
parent 989ac308dedd12c913da60ba168f3c7a4ef0cbbb
author William A. Kennington III <wak@google.com> 1571853990 -0700
committer Brad Bishop <bradleyb@fuzziesquirrel.com> 1574389825 -0500

phosphor-hwmon: Udev rules should never block

If we create a dependency in the hwmon service that makes it take extra
time to start, this will block up all of udev and prevent other devices
from being discovered as we wait on the specific hwmon instance to
start. This can result in deadlocks.

Typical convention in udev is to block as little as possible to avoid
these type of scenarios. udev can't handle failures so it's pointless to
wait anyway. The service start will still be queued up as expected.

Tested:
    Ran on a machine configured to use hwmon. Configured sensors can
    still be read and the daemons start as expected.

(From meta-phosphor rev: 1a21d0092ab2f07f5530f8b1167cbe5af12b9516)

Change-Id: I358566ce124a2bcd44306df3d579beca65133e83
Signed-off-by: William A. Kennington III <wak@google.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>