Registering smibhid display drivers happens unintuitively

[sjefferson99]

At present, the display modules needs display to register their drivers in the driver module before they can be access in the display load configured drivers method. This is currently achieved by importing the specific display module and the registration occurs on init. This is not intuitive as your linter tells you about an unused import which totally breaks the display if removed.

Might make more sense to import the specific display module and call the driver registration method. This will clarify what is happening and also appease the linter.