What is Stop() in UEFI Driver Model?
Quick note explaining Stop() in UEFI Driver Model for BIOS/UEFI and embedded firmware readers.
What is Stop() in UEFI Driver Model?
Stop() is the Driver Binding function that disconnects a driver from a controller and releases resources.
Why it matters
- Explains how UEFI drivers are structured and connected.
- Helps debug driver binding, controller connection, and resource cleanup.
- Useful when reading Driver Binding Protocol code.
Practical example
Example: if Start() fails halfway, the driver should close protocols and free resources it already allocated before returning the error.
Quick checklist
- Does Supported() match the correct device?
- Does Start() clean up on failure?
- Does Stop() release all resources and close protocols?
Quick takeaway
Stop() in UEFI Driver Model is a small concept, but it often becomes important when reading logs or debugging real firmware.
Related notes
- What is Supported() in UEFI Driver Model?
- What is Start() in UEFI Driver Model?
- What is UEFI Device Driver?
- What is UEFI Service Driver?
- What is UEFI Runtime Driver?
Public references
Found this useful?
Save it or share it with someone learning firmware, BIOS/UEFI, and embedded systems.
Nội dung liên quan
Một số bài viết, ghi chú hoặc project có liên quan đến nội dung bạn vừa đọc.
What is EFI_BUFFER_TOO_SMALL?
Quick note explaining EFI_BUFFER_TOO_SMALL for BIOS/UEFI and embedded firmware readers.
What is EFI_STATUS?
Quick note explaining EFI_STATUS for BIOS/UEFI and embedded firmware readers.
What is Supported() in UEFI Driver Model?
Quick note explaining Supported() in UEFI Driver Model for BIOS/UEFI and embedded firmware readers.
Biến note thành bài viết hoàn chỉnh
Notes là nơi ghi nhanh khái niệm.