28262d704c
r348164 added code to iicbus_request_bus/iicbus_release_bus to automatically call device_busy()/device_unbusy() as part of aquiring exclusive use of the bus (so modules can't be unloaded while the bus is exclusively owned and/or IO is in progress). That broke the ability to do i2c IO from a slave device probe method, because the slave isn't attached yet, so calling device_busy() triggers a sanity-check panic for trying to busy a non-attached device. Now we check whether the device status is < DS_ATTACHING, and if so we busy the iicbus rather than the slave device. I think this leaves a small window where a module could be unloaded while probing is in progress. But I think that's true of all devices, and probably should be fixed by introducing a DS_PROBING state for devices, and handling that at various points in the newbus code. |
||
|---|---|---|
| .. | ||
| twsi | ||
| ad7417.c | ||
| ad7418.c | ||
| adm1030.c | ||
| adt746x.c | ||
| ds13rtc.c | ||
| ds1307.c | ||
| ds1307reg.h | ||
| ds1631.c | ||
| ds1672.c | ||
| ds1775.c | ||
| ds3231.c | ||
| ds3231reg.h | ||
| icee.c | ||
| if_ic.c | ||
| iic_recover_bus.c | ||
| iic_recover_bus.h | ||
| iic.c | ||
| iic.h | ||
| iicbb_if.m | ||
| iicbb.c | ||
| iicbus_if.m | ||
| iicbus.c | ||
| iicbus.h | ||
| iicoc.c | ||
| iicoc.h | ||
| iiconf.c | ||
| iiconf.h | ||
| iicsmb.c | ||
| isl12xx.c | ||
| lm75.c | ||
| max6690.c | ||
| nxprtc.c | ||
| ofw_iicbus.c | ||
| rtc8583.c | ||
| s35390a.c | ||
| sy8106a.c | ||
| syr827.c | ||