udev: Use a new way of udev-triggered program run
Our previous form, PROGRAM+=foo, causes a warning in the log, and the
spidev device does not get created:
systemd-udevd[141]: /usr/lib/udev/rules.d/40-spi-lumentum-ocm.rules:2 PROGRAM key takes '==' or '!=' operator, assuming '==', but please fix it.
This sucks, obviously, but I'm in no mood of chasing when exactly
systemd upstream broke this feature.
The upside of this behavior change is that adjusting that
driver_override attribute via ATTR now works.
Change-Id: I52fa805dca8be060b627a5bbf70ddbdadec4cd3f
diff --git a/board/czechlight/clearfog/overlay/usr/lib/udev/rules.d/40-spi-lumentum-ocm.rules b/board/czechlight/clearfog/overlay/usr/lib/udev/rules.d/40-spi-lumentum-ocm.rules
index 206c375..0fadbae 100644
--- a/board/czechlight/clearfog/overlay/usr/lib/udev/rules.d/40-spi-lumentum-ocm.rules
+++ b/board/czechlight/clearfog/overlay/usr/lib/udev/rules.d/40-spi-lumentum-ocm.rules
@@ -1,2 +1 @@
-# cannot use ATTR{driver_override}+="spidev" because it apparently only runs after the PROGRAM
-ACTION=="add|change", SUBSYSTEM=="spi", ENV{MODALIAS}=="spi:lumentum-ocm", PROGRAM+="/bin/sh -c 'echo spidev > %S%p/driver_override && echo %k > %S%p/subsystem/drivers/spidev/bind'"
+ACTION=="add|change", SUBSYSTEM=="spi", ENV{MODALIAS}=="spi:lumentum-ocm", ATTR{driver_override}="spidev", RUN+="/bin/sh -c 'echo %k > %S%p/subsystem/drivers/spidev/bind'"