* What ist the standard way to define connector type and bus format with device tree? @ 2021-01-12 11:41 H. Nikolaus Schaller [not found] ` <F038EBE2-132E-4390-85E3-74AE9FB512A2@goldelico.com> 0 siblings, 1 reply; 2+ messages in thread From: H. Nikolaus Schaller @ 2021-01-12 11:41 UTC (permalink / raw) To: Sam Ravnborg, Thierry Reding Cc: Paul Boddie, Linux Kernel Mailing List, ML dri-devel, Discussions about the Letux Kernel 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 ^ permalink raw reply [flat|nested] 2+ messages in thread
[parent not found: <F038EBE2-132E-4390-85E3-74AE9FB512A2@goldelico.com>]
* Q: What ist the standard way to define connector type and bus format with device tree? [not found] ` <F038EBE2-132E-4390-85E3-74AE9FB512A2@goldelico.com> @ 2021-02-28 21:10 ` H. Nikolaus Schaller 0 siblings, 0 replies; 2+ messages in thread From: H. Nikolaus Schaller @ 2021-02-28 21:10 UTC (permalink / raw) To: Sam Ravnborg, Thierry Reding, Laurent Pinchart Cc: Paul Boddie, Linux Kernel Mailing List, ML dri-devel, Discussions about the Letux Kernel No expert available? Let me refine the question: By using the descriptions of panel-common.yaml and panel-timing.yaml it is possible to define a simple-panel by pure DTS means. This timing setup is done by code through: git blame drivers/gpu/drm/panel/panel-simple.c | grep of_get_display_timing 4a1d0dbc8332231 (Sam Ravnborg 2020-02-16 19:15:13 +0100 431) ret = of_get_display_timing(np, "panel-timing", timing); 4a1d0dbc8332231 (Sam Ravnborg 2020-02-16 19:15:13 +0100 566) if (!of_get_display_timing(dev->of_node, "panel-timing", &dt)) But it seems to lack a mechanism to define the connector type and bus format which is needed to make a panel finally work. Are we missing something or is the code/property missing? If it is the first, please let us know so that we can use it. If code is missing, please let us know so that we can suggest a patch. BR and thanks, Nikolaus > Am 31.01.2021 um 11:54 schrieb H. Nikolaus Schaller <hns@goldelico.com>: > > ping? > >> Am 12.01.2021 um 12:41 schrieb H. Nikolaus Schaller <hns@goldelico.com>: >> >> 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 type and bus format which can only be >> set by adding the information to the panel-simple tables. >> >> This leads to big problems because DRM can't match the >> display with any lcd controller. A smaller 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 > ^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2021-02-28 21:14 UTC | newest] Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2021-01-12 11:41 What ist the standard way to define connector type and bus format with device tree? H. Nikolaus Schaller [not found] ` <F038EBE2-132E-4390-85E3-74AE9FB512A2@goldelico.com> 2021-02-28 21:10 ` Q: " H. Nikolaus Schaller
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).