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  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]
Date:   Tue, 12 Jan 2021 12:41:36 +0100
From:   "H. Nikolaus Schaller" <hns@...delico.com>
To:     Sam Ravnborg <sam@...nborg.org>,
        Thierry Reding <thierry.reding@...il.com>
Cc:     Paul Boddie <paul@...die.org.uk>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        ML dri-devel <dri-devel@...ts.freedesktop.org>,
        Discussions about the Letux Kernel 
        <letux-kernel@...nphoenux.org>
Subject: What ist the standard way to define connector type and bus format with device tree?

Hi,
according to bindings/display/panel/panel-common.yaml
and by using "panel-simple" as compatible string we
can define almost all properties of a DSI panel by a
device tree entry.

Except the connector and bus format which can only be
set by adding the same information to the panel-simple tables.

This leads to big problems because DRM can't match the
display with any lcd controller. The least issue is a
warning:

[    0.313431] panel-simple claa070vc01: Specify missing connector_type

Are we missing some documentation or code that reads
some "connector-type" and "bus-format" property?

BR and thanks,
Nikolaus

Powered by blists - more mailing lists