Notifications
Clear all
Embedded Linux, BSPs, and Platform Software
1
Posts
1
Users
0
Reactions
0
Views
Topic starter
27/06/2026 10:10 pm
When a Linux peripheral does not probe correctly, I normally check the board description in a strict order: power, clocks, reset, pinctrl, interrupts, then driver binding.
Many long debug sessions collapse quickly once you verify that the hardware description matches the schematic instead of the vendor example board.
- Confirm regulator names and voltage values
- Confirm clock parents and rates
- Confirm reset polarity and ownership
- Check pinctrl state selection at runtime
- Inspect kernel logs around probe and deferred probe