linux-kernel - [PATCH 0/2] drivers: auxdisplay: ht16k33.c: Add option to refuse claiming primary fb

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <20220330073440.3986724-1-david@protonic.nl>
Date:   Wed, 30 Mar 2022 09:34:38 +0200
From:   David Jander <david@...tonic.nl>
To:     Robin van der Gracht <robin@...tonic.nl>,
        Miguel Ojeda <ojeda@...nel.org>
Cc:     Rob Herring <robh+dt@...nel.org>, linux-kernel@...r.kernel.org,
        devicetree@...r.kernel.org, David Jander <david@...tonic.nl>
Subject: [PATCH 0/2] drivers: auxdisplay: ht16k33.c: Add option to refuse claiming primary fb

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