linux-kernel - [PATCH 0/3] drm/msm: Use device graph to parse connected panels

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]

Date:	Mon, 22 Jun 2015 20:24:18 +0530
From:	Archit Taneja <architt@...eaurora.org>
To:	dri-devel@...ts.freedesktop.org, linux-arm-msm@...r.kernel.org
Cc:	robdclark@...il.com, hali@...eaurora.org,
	linux-kernel@...r.kernel.org,
	Archit Taneja <architt@...eaurora.org>
Subject: [PATCH 0/3] drm/msm: Use device graph to parse connected panels

drm/msm currently relies on phandles/child nodes to get data about
connected panels to LVDS and DSI. This method has known limitations.

Use device graphs in DT to represent the connections between the encoder
outputs and the panels. Use of_graph helpers in the driver to get the
panel device node.

The usage of device graphs should also simplify management in dual dsi
mode. I haven't tried this out yet, though.

Archit Taneja (3):
  drm/msm: dsi host: add missing of_node_put()
  drm/msm: dsi host: Use device graph parsing to parse connected panel
  drm/msm: mdp4 lvds: get panel node via of graph parsing

 Documentation/devicetree/bindings/drm/msm/dsi.txt | 15 ++++++
 drivers/gpu/drm/msm/dsi/dsi_host.c                | 62 ++++++++++++++++++-----
 drivers/gpu/drm/msm/mdp/mdp4/mdp4_kms.c           | 32 ++++++++----
 drivers/gpu/drm/msm/msm_drv.h                     |  1 +
 4 files changed, 87 insertions(+), 23 deletions(-)

-- 
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
hosted by The Linux Foundation

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
Please read the FAQ at  http://www.tux.org/lkml/