Lines Matching refs:uevent

154 …les must be created before mounting. This is usually done based on the **uevent** messages reporte…
163 …2. Create a socket for receiving **uevent** messages reported by the kernel and read `default_boot…
164 …e fstab information and socket handle to get the kernel prepared for reporting **uevent** messages.
168 1. Use **ueventd** to trigger the kernel to report a **uevent** message.
169 …2. Check whether partitionName in the **uevent** message matches with device information in the `f…
175 … nodes based on the primary and secondary device numbers passed in the **uevent** message, and the…
218 2. Create a socket and trigger the kernel to report a **uevent** message.
225 INIT_LOGE("Failed to create uevent socket");
242 4. Process the **uevent** message of the `required` partition device.
244 if (uevent->partitionName == NULL) {
245 INIT_LOGI("Match with %s for %s", devices[i], uevent->syspath);
250 INIT_INFO_CHECK(strstr(uevent->syspath, deviceName) != NULL, continue,
251 "uevent->syspath %s not match deviceName %s", uevent->syspath, deviceName);
252 HandleBlockDeviceEvent(uevent);
254 } else if (strstr(devices[i], uevent->partitionName) != NULL) {
255 INIT_LOGI("Handle block device partitionName %s", uevent->partitionName);
256 HandleBlockDeviceEvent(uevent);
260uevent** message reported by the kernel. The value of `uevent -> partitionName` should be system f…
264 …args` will be matched with the path of the required device node in the **uevent** message, so as t…
270 … BuildDeviceSymbolLinks(links, linkNum, parent, uevent->partitionName, uevent->deviceName);
274 BuildBootDeviceSymbolLink(links, linkNum, uevent->partitionName);
282 …rent`: a string that stores the device path obtained from `uevent -> syspath` in the **uevent** me…
295 …Therefore, when processing the **uevent** message of the device, the init process compares the dev…
300 … creates the device node and soft link based on the information in the **uevent** message. Up to n…