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.

Change-Id: If6972cef5b7381b93dc83feb1ced874a0d1877c8
Signed-off-by: William A. Kennington III <wak@google.com>
1 file changed
tree: e4e572430b224c66a194056b861f67a08f850196
  1. aspeed-layer/
  2. classes/
  3. conf/
  4. nuvoton-layer/
  5. raspberrypi/
  6. recipes-connectivity/
  7. recipes-core/
  8. recipes-devtools/
  9. recipes-extended/
  10. recipes-graphics/
  11. recipes-phosphor/
  12. recipes-protocols/
  13. recipes-support/
  14. recipes-textproc/
  15. recipes-x86/
  16. COPYING.apache-2.0
  17. COPYING.MIT
  18. LICENSE
  19. MAINTAINERS
  20. README.md
  21. recipes.txt
README.md

OpenBMC

meta-phosphor is the OpenBMC layer. This layer should be included for all OpenBMC systems. The OpenBMC layer contains content which is shared between all OpenBMC systems.