In the case there is also a display with a frame-buffer device, the probe
order of the auxdisplay fb and the main fb is not predictable, possibly
leading to the situation where the holtek auxdisplay becomes /dev/fb0.
This is problematic because there is currently no way to automatically
rename these devices, and too much user-space software that assumes fb0
to be the main display.
In such a situation, adding "holtek,refuse-primary-fb" to the DT, the
auxdisplay driver returns -EPROBE_DEFER to wait for the primary fb device
to get probed first.

David Jander (2):
  drivers: auxdisplay: ht16k33.c: Add option to refuse claiming primary
    fb
  dt-bindings: auxdisplay: holtek,ht16k33.yaml: Add
    holtek,refuse-primary-fb

 .../devicetree/bindings/auxdisplay/holtek,ht16k33.yaml    | 3 +++
 drivers/auxdisplay/ht16k33.c                              | 8 ++++++++
 2 files changed, 11 insertions(+)

-- 
2.32.0