forked from microsoft/WSL2-Linux-Kernel
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge branch 'drm-next' of git://people.freedesktop.org/~airlied/linux
Pull drm updates from Dave Airlie: "This is the main drm pull request for v4.2. I've one other new driver from freescale on my radar, it's been posted and reviewed, I'd just like to get someone to give it a last look, so maybe I'll send it or maybe I'll leave it. There is no major nouveau changes in here, Ben was working on something big, and we agreed it was a bit late, there wasn't anything else he considered urgent to merge. There might be another msm pull for some bits that are waiting on arm-soc, I'll see how we time it. This touches some "of" stuff, acks are in place except for the fixes to the build in various configs,t hat I just applied. Summary: New drivers: - virtio-gpu: KMS only pieces of driver for virtio-gpu in qemu. This is just the first part of this driver, enough to run unaccelerated userspace on. As qemu merges more we'll start adding the 3D features for the virgl 3d work. - amdgpu: a new driver from AMD to driver their newer GPUs. (VI+) It contains a new cleaner userspace API, and is a clean break from radeon moving forward, that AMD are going to concentrate on. It also contains a set of register headers auto generated from AMD internal database. core: - atomic modesetting API completed, enabled by default now. - Add support for mode_id blob to atomic ioctl to complete interface. - bunch of Displayport MST fixes - lots of misc fixes. panel: - new simple panels - fix some long-standing build issues with bridge drivers radeon: - VCE1 support - add a GPU reset counter for userspace - lots of fixes. amdkfd: - H/W debugger support module - static user-mode queues - support killing all the waves when a process terminates - use standard DECLARE_BITMAP i915: - Add Broxton support - S3, rotation support for Skylake - RPS booting tuning - CPT modeset sequence fixes - ns2501 dither support - enable cmd parser on haswell - cdclk handling fixes - gen8 dynamic pte allocation - lots of atomic conversion work exynos: - Add atomic modesetting support - Add iommu support - Consolidate drm driver initialization - and MIC, DECON and MIPI-DSI support for exynos5433 omapdrm: - atomic modesetting support (fixes lots of things in rewrite) tegra: - DP aux transaction fixes - iommu support fix msm: - adreno a306 support - various dsi bits - various 64-bit fixes - NV12MT support rcar-du: - atomic and misc fixes sti: - fix HDMI timing complaince tilcdc: - use drm component API to access tda998x driver - fix module unloading qxl: - stability fixes" * 'drm-next' of git://people.freedesktop.org/~airlied/linux: (872 commits) drm/nouveau: Pause between setting gpu to D3hot and cutting the power drm/dp/mst: close deadlock in connector destruction. drm: Always enable atomic API drm/vgem: Set unique to "vgem" of: fix a build error to of_graph_get_endpoint_by_regs function drm/dp/mst: take lock around looking up the branch device on hpd irq drm/dp/mst: make sure mst_primary mstb is valid in work function of: add EXPORT_SYMBOL for of_graph_get_endpoint_by_regs ARM: dts: rename the clock of MIPI DSI 'pll_clk' to 'sclk_mipi' drm/atomic: Don't set crtc_state->enable manually drm/exynos: dsi: do not set TE GPIO direction by input drm/exynos: dsi: add support for MIC driver as a bridge drm/exynos: dsi: add support for Exynos5433 drm/exynos: dsi: make use of array for clock access drm/exynos: dsi: make use of driver data for static values drm/exynos: dsi: add macros for register access drm/exynos: dsi: rename pll_clk to sclk_clk drm/exynos: mic: add MIC driver of: add helper for getting endpoint node of specific identifiers drm/exynos: add Exynos5433 decon driver ...
- Loading branch information
Showing
569 changed files
with
453,841 additions
and
9,861 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,120 @@ | ||
Qualcomm Technologies Inc. adreno/snapdragon DSI output | ||
|
||
DSI Controller: | ||
Required properties: | ||
- compatible: | ||
* "qcom,mdss-dsi-ctrl" | ||
- reg: Physical base address and length of the registers of controller | ||
- reg-names: The names of register regions. The following regions are required: | ||
* "dsi_ctrl" | ||
- qcom,dsi-host-index: The ID of DSI controller hardware instance. This should | ||
be 0 or 1, since we have 2 DSI controllers at most for now. | ||
- interrupts: The interrupt signal from the DSI block. | ||
- power-domains: Should be <&mmcc MDSS_GDSC>. | ||
- clocks: device clocks | ||
See Documentation/devicetree/bindings/clocks/clock-bindings.txt for details. | ||
- clock-names: the following clocks are required: | ||
* "bus_clk" | ||
* "byte_clk" | ||
* "core_clk" | ||
* "core_mmss_clk" | ||
* "iface_clk" | ||
* "mdp_core_clk" | ||
* "pixel_clk" | ||
- vdd-supply: phandle to vdd regulator device node | ||
- vddio-supply: phandle to vdd-io regulator device node | ||
- vdda-supply: phandle to vdda regulator device node | ||
- qcom,dsi-phy: phandle to DSI PHY device node | ||
|
||
Optional properties: | ||
- panel@0: Node of panel connected to this DSI controller. | ||
See files in Documentation/devicetree/bindings/panel/ for each supported | ||
panel. | ||
- qcom,dual-panel-mode: Boolean value indicating if the DSI controller is | ||
driving a panel which needs 2 DSI links. | ||
- qcom,master-panel: Boolean value indicating if the DSI controller is driving | ||
the master link of the 2-DSI panel. | ||
- qcom,sync-dual-panel: Boolean value indicating if the DSI controller is | ||
driving a 2-DSI panel whose 2 links need receive command simultaneously. | ||
- interrupt-parent: phandle to the MDP block if the interrupt signal is routed | ||
through MDP block | ||
|
||
DSI PHY: | ||
Required properties: | ||
- compatible: Could be the following | ||
* "qcom,dsi-phy-28nm-hpm" | ||
* "qcom,dsi-phy-28nm-lp" | ||
- reg: Physical base address and length of the registers of PLL, PHY and PHY | ||
regulator | ||
- reg-names: The names of register regions. The following regions are required: | ||
* "dsi_pll" | ||
* "dsi_phy" | ||
* "dsi_phy_regulator" | ||
- qcom,dsi-phy-index: The ID of DSI PHY hardware instance. This should | ||
be 0 or 1, since we have 2 DSI PHYs at most for now. | ||
- power-domains: Should be <&mmcc MDSS_GDSC>. | ||
- clocks: device clocks | ||
See Documentation/devicetree/bindings/clocks/clock-bindings.txt for details. | ||
- clock-names: the following clocks are required: | ||
* "iface_clk" | ||
- vddio-supply: phandle to vdd-io regulator device node | ||
|
||
Example: | ||
mdss_dsi0: qcom,mdss_dsi@fd922800 { | ||
compatible = "qcom,mdss-dsi-ctrl"; | ||
qcom,dsi-host-index = <0>; | ||
interrupt-parent = <&mdss_mdp>; | ||
interrupts = <4 0>; | ||
reg-names = "dsi_ctrl"; | ||
reg = <0xfd922800 0x200>; | ||
power-domains = <&mmcc MDSS_GDSC>; | ||
clock-names = | ||
"bus_clk", | ||
"byte_clk", | ||
"core_clk", | ||
"core_mmss_clk", | ||
"iface_clk", | ||
"mdp_core_clk", | ||
"pixel_clk"; | ||
clocks = | ||
<&mmcc MDSS_AXI_CLK>, | ||
<&mmcc MDSS_BYTE0_CLK>, | ||
<&mmcc MDSS_ESC0_CLK>, | ||
<&mmcc MMSS_MISC_AHB_CLK>, | ||
<&mmcc MDSS_AHB_CLK>, | ||
<&mmcc MDSS_MDP_CLK>, | ||
<&mmcc MDSS_PCLK0_CLK>; | ||
vdda-supply = <&pma8084_l2>; | ||
vdd-supply = <&pma8084_l22>; | ||
vddio-supply = <&pma8084_l12>; | ||
|
||
qcom,dsi-phy = <&mdss_dsi_phy0>; | ||
|
||
qcom,dual-panel-mode; | ||
qcom,master-panel; | ||
qcom,sync-dual-panel; | ||
|
||
panel: panel@0 { | ||
compatible = "sharp,lq101r1sx01"; | ||
reg = <0>; | ||
link2 = <&secondary>; | ||
|
||
power-supply = <...>; | ||
backlight = <...>; | ||
}; | ||
}; | ||
|
||
mdss_dsi_phy0: qcom,mdss_dsi_phy@fd922a00 { | ||
compatible = "qcom,dsi-phy-28nm-hpm"; | ||
qcom,dsi-phy-index = <0>; | ||
reg-names = | ||
"dsi_pll", | ||
"dsi_phy", | ||
"dsi_phy_regulator"; | ||
reg = <0xfd922a00 0xd4>, | ||
<0xfd922b00 0x2b0>, | ||
<0xfd922d80 0x7b>; | ||
clock-names = "iface_clk"; | ||
clocks = <&mmcc MDSS_AHB_CLK>; | ||
vddio-supply = <&pma8084_l12>; | ||
}; |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,60 @@ | ||
Qualcomm Technologies Inc. adreno/snapdragon eDP output | ||
|
||
Required properties: | ||
- compatible: | ||
* "qcom,mdss-edp" | ||
- reg: Physical base address and length of the registers of controller and PLL | ||
- reg-names: The names of register regions. The following regions are required: | ||
* "edp" | ||
* "pll_base" | ||
- interrupts: The interrupt signal from the eDP block. | ||
- power-domains: Should be <&mmcc MDSS_GDSC>. | ||
- clocks: device clocks | ||
See Documentation/devicetree/bindings/clocks/clock-bindings.txt for details. | ||
- clock-names: the following clocks are required: | ||
* "core_clk" | ||
* "iface_clk" | ||
* "mdp_core_clk" | ||
* "pixel_clk" | ||
* "link_clk" | ||
- #clock-cells: The value should be 1. | ||
- vdda-supply: phandle to vdda regulator device node | ||
- lvl-vdd-supply: phandle to regulator device node which is used to supply power | ||
to HPD receiving chip | ||
- panel-en-gpios: GPIO pin to supply power to panel. | ||
- panel-hpd-gpios: GPIO pin used for eDP hpd. | ||
|
||
|
||
Optional properties: | ||
- interrupt-parent: phandle to the MDP block if the interrupt signal is routed | ||
through MDP block | ||
|
||
Example: | ||
mdss_edp: qcom,mdss_edp@fd923400 { | ||
compatible = "qcom,mdss-edp"; | ||
reg-names = | ||
"edp", | ||
"pll_base"; | ||
reg = <0xfd923400 0x700>, | ||
<0xfd923a00 0xd4>; | ||
interrupt-parent = <&mdss_mdp>; | ||
interrupts = <12 0>; | ||
power-domains = <&mmcc MDSS_GDSC>; | ||
clock-names = | ||
"core_clk", | ||
"pixel_clk", | ||
"iface_clk", | ||
"link_clk", | ||
"mdp_core_clk"; | ||
clocks = | ||
<&mmcc MDSS_EDPAUX_CLK>, | ||
<&mmcc MDSS_EDPPIXEL_CLK>, | ||
<&mmcc MDSS_AHB_CLK>, | ||
<&mmcc MDSS_EDPLINK_CLK>, | ||
<&mmcc MDSS_MDP_CLK>; | ||
#clock-cells = <1>; | ||
vdda-supply = <&pma8084_l12>; | ||
lvl-vdd-supply = <&lvl_vreg>; | ||
panel-en-gpios = <&tlmm 137 0>; | ||
panel-hpd-gpios = <&tlmm 103 0>; | ||
}; |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
7 changes: 7 additions & 0 deletions
7
Documentation/devicetree/bindings/panel/hannstar,hsd100pxn1.txt
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,7 @@ | ||
HannStar Display Corp. HSD100PXN1 10.1" XGA LVDS panel | ||
|
||
Required properties: | ||
- compatible: should be "hannstar,hsd100pxn1" | ||
|
||
This binding is compatible with the simple-panel binding, which is specified | ||
in simple-panel.txt in this directory. |
Oops, something went wrong.